Does UI Policy override ACL?

[Community Alums]

I've a custom field on change_request form and have restricted it to be read only when state is greater than authorize. I've a write ACL to make is editable only for users with role CAB manager. When I login as CAB manager, the field is still read only. Anything I am missing here?

[Vishal Khandve]

Hi Vineeth,

Field State (Mandatory,Visible, Read only) is generally applied in the following order of preference, where one is the top preference:

1. ACL (Visible/Disabled)
2. Dictionary Entry (Mandatory/Disabled)
3. UI Policy (Mandatory/Visible/Disabled)
4. Data Policy as UI   (Mandatory/Disabled)
5. Client Script (Mandatory/Visible/Disabled)

also go through below link-

https://community.servicenow.com/community?id=community_question&sys_id=096362aadb831bc45129a851ca96...

Thanks,

Vishal

[Community Alums]

Hi Vishal,

Thanks for the reply, I've gone through the link. I've write ACL to the custom field so that particular user with role(CAB Manager) can write. But when watch that field(Field Watcher) it's showing that UI policy is making it read only which I've written when state is greater than Authorize.

As per information given in link, CAB manager should be able to edit it correct?

[ggg]

The only way I know how to do this is to have a display Business Rule that gets the roles.

I then have an onload client script that does the work of setting READONLY based upon role and other conditions I may have.

I would appreciate knowing how to do this with an ACL.

[Community Alums]

Hi ggg,

Thanks for your reply, can it be done in a simple way?