Remediation for strict read-only fields preventing client side updates<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Starting with the Australia release, additional controls were introduced to enforce read-only behavior more consistently. Two primary options are now available: strict_read_only – Prevents any client-side modification of read-only fields.client_script_modifiable – Allows modification of read-only fields only on a form via client-side scripts. Impact After Upgrade After upgrading, some customer-created client scripts that previously modified ServiceNow-created read-only fields may no longer be able to update those fields due to the stricter enforcement. The following tables containing client scripts may be impacted: Client Scripts (sys_client_script)UI Actions (sys_ui_action)Declarative Actions (sys_declarative_action_assignment)UI Policies (sys_ui_policy) Diagnosing the Issue If a client script is no longer updating a read-only field as expected: Navigate to the field’s sys_dictionary record.Review the value of the read_only_option field.If the value is strict_read_only, this setting is preventing the client-side update. Options You can address this issue using one of the following approaches: Manually update the dictionary record. Change the field’s read_only_option value to client_script_modifiable.Run a background script to identify and update affected fields. These scripts identify strict read-only fields that are being updated via the g_form API. The read only option on the dictionary or dictionary override record is then modified from a value of Strict read only to Client Script Modifiable. Identify Affected Fields (No Changes Applied) To identify affected fields without modifying any records, run the following background script: var strictReadOnlyOption = new StrictReadOnlyOption(true); strictReadOnlyOption.setClientScriptModifiableWhereAffected(); Updating Read-only Options for Affected Fields To automatically update affected fields to client_script_modifiable, run the following background script by navigating to System Definitions -> Scripts - Background. var strictReadOnlyOption = new StrictReadOnlyOption(); strictReadOnlyOption.setClientScriptModifiableWhereAffected();