ACLs - List Edit vs. Write

[Sue Frost]

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!

[Sue Frost]

What if I approach this somewhat differently ... if Test User is supposed to be able to update via List Edit, why not let them update via the form as well?

That feels like it would simplify things.

Then I should be able to use the ACLs I have built and tweak them by role.

[paul_mcnamara · 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!

[ryadavalli]

HI Anurag,

I have a similar question. I have a list edit ACL on all the tables *.* which is preventing anyone other than admin to edit the fields on list. But we saw a peculiar thing, we are not able to modify any reference fields as well except a CI field which is reference to cmdb_ci table. We need to lock down that as well. DO yo have any suggestion for me ?

Thanks,

[Anurag Tripathi]

find the acl on this field, probably there would be some act on this field that is allowing other roles to edit this field.

[Anurag Tripathi]

find the acl on this field, probably there would be some act on this field that is allowing other roles to edit this field.