ACLs - List Edit vs. Write

Sue Frost
Giga Guru

I have a custom application and table where the request is to prevent editing on the form while the status is 'on hold' BUT to allow specified users to make changes via list edit - providing they have the correct role.

I'm very new to ACLs and I've gotten most of this done. I adapted the existing ACLs on the table to allow write access only when the status is not closed (that was existing) or on hold (my change). On the form this works perfectly.

HOWEVER, I'm not able to get the list edit roles working. I've been able to determine that the write ACL is trumping the list edit ACL.

What I'm hoping for is suggestions for workarounds.

TIA!

1 ACCEPTED SOLUTION

Yes if you allow edit in both form/list you won't need to have a UI policy on the form.     Definitely more straightforward!


View solution in original post

10 REPLIES 10

ganeshb_
Giga Expert

Hi Sue,



this might help you-


Client script for blocking edits in list view



Thanks,


Ganesh


Anurag Tripathi
Mega Patron
Mega Patron

Hi Sue,



If there are not many fields, I would suggest that just create a List edit ACL . And on the form use UI Policy to make the fields read only on "On Hold".


-Anurag

Thanks for the quick replies. I've had a look at this and it is doing the same thing that I have done.


Perhaps a bit more detail is needed. Here are the ACL rules I have:



  1. on the table (eg. u_case.   ) - write - allow access at any time
  2. on the table - list edit - allow access for users with specified role
  3. on the record (eg u_case.*) - write - allow access for users under specified conditions.
    1. conditions include: case is open, case is not on hold, user is assignee or delegate, user has specified roles
  4. on the record - list edit - deny write access to all users
  5. on the field (eg. u_case.due_date) - write - allow access when case is open
  6. on the field - list edit - allow access at any time


My test user has the appropriate roles to allow for list edits.


When Test User opens the form, all the fields are locked - which is what I'm expecting.


When Test User does a list edit, he is unable to change the Due Date field on an On Hold case - I'm expecting that he can.



The only way to allow Test User to do a list edit on Due Date is to turn off Rule 3 above which locks the form when a case is on hold.



I believe I'm trying to do the reverse of all the examples I've found - the form is locked, but list edit is available.


I think the only thing you are missing is giving write perms to the Due Date field for the role you have given Test User.   And then use a UI policy to make that one field read only on the form.



If you do not have write perms to a field you don't get form or list edit.   If you have write perms to a field but not list edit you get form no list edit.   There isn't a way (that I know of) to give JUST list edit perms.