ServiceNow Australia Release: New Read-Only Dictionary Attributes Explained

In the ServiceNow Australia (March 2026) release, the "Read-only" checkbox is officially evolving. For years, developers have dealt with "leaky" read-only fields that could be bypassed by Client Scripts or server-side APIs. That ends now.

In this deep dive, we compare the Zurich version's legacy behavior against the new Australia granular security model. We’ll show you why your existing scripts might suddenly fail and how to use the new Read-only option to truly lock down your data.

What You’ll Learn:

✅ The Zurich "Suggestion": How we used to bypass read-only fields with simple scripts.
✅ The 4 New Levels: Understanding Instance Configured, Display Read Only, Client Script Modifiable, and Strict Read Only.
✅ The API Trap: Why GlideRecord still works on some fields while GlideRecordSecure respects the new "Strict" attribute.
✅ Global Control: How the glide.read_only.legacy_read_only_behavior property dictates your upgrade path.
Video Chapters:

0:00 Intro: Why Read-Only was "Broken"

0:45 Zurich Demo: Bypassing the UI Lock

1:54 Australia Release: The New Dictionary UI

2:25 The 4 New Security Levels Explained

3:30 "Display Read Only" vs. Client Scripts

4:25 Critical Detail: GlideRecord vs. GlideRecordSecure

6:00 Setting Up "Strict Read Only" (The Total Lock)

7:20 System Properties & Migration Strategy

8:15 Final Summary: Which level should you choose?

Key Takeaway for Admins:

If you are upgrading to Australia, your fields default to "Instance Configured" to prevent breaking your current scripts. However, for new high-security fields, Strict Read Only is your new best friend for ensuring data integrity across both the UI and the API.

#ServiceNow #AustraliaRelease #ServiceNowDev #ServiceNowAdmin #ServiceNowSecurity #GlideRecord #DataIntegrity #ITSM #LowCode

Видео ServiceNow Australia Release: New Read-Only Dictionary Attributes Explained канала loop91 - ServiceNow