Ankur Bawiskar
Tera Patron

@Kiran_25 

so any other client script or UI policy is making it editable?

Did you debug that?

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

There's no UI policies or client scripts. There is one preexisting ACL that makes it editable 

for users with a technical owner role. I want to open it to so its also editable by users with a domain manager role. 

I have tried adding my roles to the existing ACL and I have also tried creating a brand new ACL too

 

Hi @Kiran_25 ,
You can try Creating a script condition in the existing ACL with gs.hasRole('x'), as creating a new ACL for the same field/write combination won’t work, because all matching ACLs must evaluate to true. That means if your new ACL passes but the old one restricts access, users will still be blocked. 

If you want to confirm behavior, use Access Analyzer with a  test user  you’ll see which ACLs are being enforced.


Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.

Thanks & Regards,
Muhammad Iftikhar

If my response helped, please mark it as the accepted solution so others can benefit as well.

@Kiran_25 

it means some other component is doing the job here.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

Shashank_Jain
Mega Sage

@Kiran_25 ,

1. Check UI Policies, Client Scripts, or Dictionary Overrides that may be making the field read-only.

2. Check with an admin user – see if the field is editable.

 

If this works, please mark it as helpful/accepted — it keeps me motivated and helps others find solutions.
Shashank Jain

View solution in original post