One small but useful change in the ServiceNow Australia release is the new Read-only options for dictionary fields. might be lil older but sharing it anyways.
Previously, when we marked a field as read-only, it mainly meant that users couldn't edit it from the form. But scripts and other backend processes could still change the value.
Now ServiceNow gives us more control with three read-only options:
1. Display Read Only
This is basically the familiar behavior.
The field is read-only for users, but client scripts and backend processes can still update it.
Use this when: you only want to stop users from manually changing the field.
2. Client Script Modifiable
The field is read-only for users, but client scripts can still modify it. However, server-side updates through supported APIs are blocked.
Use this when: your form logic needs to update the field, but you don't want backend/API updates.
3. Strict Read Only
This is the strongest option.
The field can't be changed by users, client scripts, or supported server-side APIs.
Use this when: the value really needs to stay locked down.
What about "Instance Configured"?
You might also see Instance Configured in the dropdown.
This is mainly for older fields and backward compatibility. Its behavior is controlled by the instance configuration, so existing fields don't suddenly change behavior after upgrading.
Why does this matter?
It's a small change, but it gives developers much better control over what "read-only" actually means.
Earlier, read-only mostly meant "the user can't edit it."
Now we can choose whether we want:
UI protection → Client-side flexibility → Full read-only protection
So, when creating or updating a field, don't just mark it read-only and move on. Think about who or what should still be allowed to change that value.
Read-only options • Australia ServiceNow AI Platform Administration • Docs | ServiceNow
That's where these new options become really useful. Bye until next time.
