Custom fields being read only without the checkbox being selected

[MarisaW81535484]

Hello, 

A clients environment was recently upgraded to Australia. I created a custom field on the sn_grc_reg_change_regulatory_feed table and when I added the field to layout it came on as read only even though the checkbox is not selected. I did read about the new read only options that came out as part of Australia but none of those options helped in getting the field to be editable. The image below shows the dictionary for the new field. Is there any way for me to make this field editable without creating a new access control that allows write access to this field? I have already tried creating a client script and a UI policy. If I do need to create a new ACL why would this be the case? This functionality makes no sense. 

[Vishal Jaswal]

Hello @MarisaW81535484 

To test this, create same custom field in a different table or in your PDI and I am sure you will notice the field is editable.

If yes, then you need to find out any client script (look for script contains

g_form.setReadOnly) or UI policy which makes all fields read only for this table.

[Rafael Batistot]

Hi @MarisaW81535484 

The field is read-only because server-side ACLs override Client Scripts and UI Policies.

The GRC table uses strict write ACLs (⁠sn_grc_reg_change_regulatory_feed.*⁠) to protect regulatory feed data. Since custom fields don't have an explicit write permission, ServiceNow defaults to restricting write access.

May you create a Write ACL for your field:

 Type: ⁠record⁠

 Operation: ⁠write⁠

 Name: ⁠sn_grc_reg_change_regulatory_feed.u_your_custom_field⁠

 Role: Add the required GRC role (or ⁠admin⁠).