| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nZurich\n\n | \n\n- **Upgrade information**\n\nThe dynamic schema application framework has been revised in the Zurich release. If you implemented dynamic schema in Xanadu or Yokohama, the application is automatically migrated to a new framework as part of the upgrade to the Zurich release. For details on the migration, see the [Dynamic Schema Zurich Migration Guide \\[KB2146133\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2146133) article in the Now Support Knowledge Base.\n\n\n |
| \n\nAustralia\n\n | \n\n- **Upgrade information**\n\nThe dynamic schema application framework was revised in the Zurich release. If you implemented dynamic schema in the Xanadu or Yokohama releases, the application is automatically migrated to a new framework as part of the upgrade to releases starting with the Zurich release. For details on the migration and steps you might need to perform, see the [Dynamic Schema Zurich Migration Guide \\[KB2146133\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2146133) article in the Now Support Knowledge Base.\n\nThe Australia release introduces enhanced protections for read‑only fields across the ServiceNow AI Platform®. These changes include a new “read\\_only\\_option” field with granular control levels, including “strict\\_read\\_only” and “client\\_script\\_modifiable\". The changes occur in the back end and maintain backward‑compatible behavior. This update helps strengthen your instance security while preserving the flexibility you need. Refer to [KB2718122](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2718122) for additional technical details on how to identify affected fields and adjust their settings. For more information about granular read-only security options, see [Configuring read-only security options](https://www.servicenow.com/docs/access?context=read-only-option&family=australia&ft:locale=en-US).\n\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nZurich\n\n | \n\n- **[Access and test pre-release features](https://www.servicenow.com/docs/access?context=feature-preview-program&family=zurich&ft:locale=en-US)**\n\nThe Feature Preview Program provides a centralized location to discover, activate, and test pre-release capabilities on your instance. When a pre-release feature is added to your instance, you receive a notification and can access the Feature Preview Program to review feature details, activate features for testing, and provide feedback.\n\n\n - **[Enhance instance security for sandbox scripts with guarded script](https://www.servicenow.com/docs/access?context=guarded-script&family=zurich&ft:locale=en-US)**\n\nThe guarded script evaluator restricts the JavaScript features and APIs available to untrusted, client-generated scripts running in the script sandbox environment. Beginning with the Zurich Patch 9 release, incompatible scripts sent to the server by guest users are rejected on all instances by default. Scripts sent by authenticated users are evaluated using a phased approach to enforcement that varies by the type of instance to provide time to detect and review incompatible scripts before rejecting them. Scripts that use unsupported features are recorded in the Incompatible Guarded Scripts list, where you can rewrite them or create exemptions for scripts that can't be rewritten.\n\n\n - **[Automatically generate request definitions for scripted REST API resources](https://www.servicenow.com/docs/access?context=autogenerate-api-request-definitions&family=zurich&ft:locale=en-US)**\n\nUse sample requests made to an API resource to generate request header associations, query parameter associations, and a request schema for that resource and the related scripted REST API service.\n\n\n - **[Use schemas to define the structure and format of REST API responses and requests](https://www.servicenow.com/docs/access?context=define-scripted-rest-api-schema&family=zurich&ft:locale=en-US)**\n\nWhen you define a schema in the ServiceNow AI Platform, the schema can be used to define the structure of requests and responses within the associated REST API. The schema data for the requests and responses is then available in the exportable OpenAPI specification for the API.\n\n\n - **[Experimentation framework](https://www.servicenow.com/docs/access?context=experimentation-framework&family=zurich&ft:locale=en-US)**\n\nHelp enable innovation by trying new ServiceNow® feature variants in your instance. Only single customer instances or Gen AI Innovation Program participants have early access to new innovations via experimentation framework. You can opt out of specific experiments or turn off the framework entirely.\n\n- **[Monitor requestors' API usage rates through the Inbound API Integration Usage dashboard](https://www.servicenow.com/docs/access?context=inbound-api-integration-usage-dashboard&family=zurich&ft:locale=en-US)**\n\nInbound integrations track web service requests for OAuth registered applications and user accounts making those requests.\n\n\n - **[Hierarchical queries in condition builders](https://www.servicenow.com/docs/access?context=data-hierarchies&family=zurich&ft:locale=en-US)**\n\nSimplify and build queries with fewer conditions using existing hierarchical data in a table. You can also define new hierarchical relationships between records that are in the same table.\n\n- **[Dynamic namespaces](https://www.servicenow.com/docs/access?context=create-dynamic-namespace&family=zurich&ft:locale=en-US)**\n\nDefine categories and attributes once and reuse them using dynamic namespaces across multiple tables and dynamic attribute store fields. A dynamic namespace is automatically created when you add a dynamic attribute store field.\n\n- **[Audit Management Console and audit retention](https://www.servicenow.com/docs/access?context=audit-mgmt-console&family=zurich&ft:locale=en-US)**\n\nSimplify your audit data management and configuration by using the Audit Management Console module. It includes a new Retention option, which automates and simplifies the deletion of audit data based on your requirements.\n\n\n |
| \n\nAustralia\n\n | \n\n- **[Access and test pre-release features](https://www.servicenow.com/docs/access?context=feature-preview-program&family=australia&ft:locale=en-US)**\n\nThe Feature Preview Program provides a centralized location to discover, activate, and test pre-release capabilities on your instance. When a pre-release feature is added to your instance, you receive a notification and can access the Feature Preview Program to review feature details, activate features for testing, and provide feedback.\n\n\n - **[Enhance instance security for sandbox scripts with guarded script](https://www.servicenow.com/docs/access?context=guarded-script&family=australia&ft:locale=en-US)**\n\nThe guarded script evaluator restricts the JavaScript features and APIs available to untrusted, client-generated scripts running in the script sandbox environment. Beginning with the Australia Patch 2 release, incompatible scripts sent to the server by guest users are rejected on all instances by default. Scripts sent by authenticated users are evaluated using a phased approach to enforcement that varies by the type of instance to provide time to detect and review incompatible scripts before rejecting them. Scripts that use unsupported features are recorded in the Incompatible Guarded Scripts list, where you can rewrite them or create exemptions for scripts that can't be rewritten.\n\n\n - **[Automatically generate request definitions for scripted REST API resources](https://www.servicenow.com/docs/access?context=autogenerate-api-request-definitions&family=australia&ft:locale=en-US)**\n\nUse sample requests made to an API resource to generate request header associations, query parameter associations, and a request schema for that resource and the related scripted REST API service.\n\n\n - **[Granular read-only security options](https://www.servicenow.com/docs/access?context=read-only-option&family=australia&ft:locale=en-US)**\n\nControl the editability of read-only fields by configuring read-only options, allowing for customized behavior that balances usability and security. Read-only options provide granular control over whether read-only fields can be updated through client scripts and server-side operations. You can also test stricter read-only controls in non-production instances before implementing them in production.\n\n- **[Support for reference data types in Dynamic Schema](https://www.servicenow.com/docs/access?context=add-dynamic-attributes&family=australia&ft:locale=en-US)**\n\nCreate dynamic attributes using reference data types.\n\n- **[Work with Dynamic Schema elements in the Workspace condition builder](https://www.servicenow.com/docs/access?context=dynamic-schema&family=australia&ft:locale=en-US)**\n\nFilter Workspace lists using dynamic schema elements in the condition builder.\n\n- **[Toggle the mail icon display](https://www.servicenow.com/docs/access?context=c_DictionaryAttributes&family=australia&ft:locale=en-US)**\n\nShow or hide the mail icon in email fields by configuring the hide\\_email\\_icon dictionary attribute.\n\n- **[AI indicator in forms](https://www.servicenow.com/docs/access?context=c_FormFields&family=australia&ft:locale=en-US)**\n\nEasily identify AI involvement across the ServiceNow AI Platform® through a visual cue that identifies form fields in configurable workspace and Core UI that have been updated with AI-generated content.\n\n- **[Guest API access control](https://www.servicenow.com/docs/access?context=c_RESTAPI&family=australia&ft:locale=en-US)**\n\nManage guest access to REST and GraphQL API endpoints using path-based ACLs while maintaining separate authenticated user controls.\n\n- **[Granular admin roles](https://www.servicenow.com/docs/access?context=granular-admin-roles&family=australia&ft:locale=en-US)**\n\nGrant specific permissions to developers or users who perform minor administrative tasks without granting them unrestricted access to the full admin role by reviewing and assigning available granular admin roles.\n\n- **[Optional trailing slash configuration](https://www.servicenow.com/docs/access?context=api-rest&family=australia&ft:locale=en-US)**\n\nAlign with external specifications and industry standards by configuring REST APIs with optional trailing slash support.\n\n- **[Path-based REST ACL control](https://www.servicenow.com/docs/access?context=api-rest&family=australia&ft:locale=en-US)**\n\nControl access to REST services by creating path-based ACLs using specific HTTP method and path combinations.\n\n- **[Resource-level security configuration](https://www.servicenow.com/docs/access?context=api-rest&family=australia&ft:locale=en-US)**\n\nEnable public access or custom ACL authorization by configuring resource-level security settings.\n\n- **[Address field type with auto-suggestions](https://www.servicenow.com/docs/access?context=address-field-type&family=australia&ft:locale=en-US)**\n\nReduce manual entry errors through a new Address field type for Core UI and Workspace forms, which provides real-time address suggestions displayed as you type.\n\n- **[New dot-walk scoping security properties and table attribute](https://www.servicenow.com/docs/access?context=r_AvailableSystemProperties&family=australia&ft:locale=en-US)**\n\nStrengthen scope boundary enforcement when dot-walking across application scopes using Reference Fields through additional properties and a table attribute. For more information, see the [Dot-Walk Scoping Security Enhancement \\[KB2793170\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2793170) article in the Now Support Knowledge Base.\n\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nZurich\n\n | \n\n- **[AI indicator in forms](https://www.servicenow.com/docs/access?context=ai-indicator-in-configurable-workspace-and-core-ui&family=zurich&ft:locale=en-US)**\n\nThe AI indicator is a visual cue that identifies form fields in configurable workspace and Core UI that have been updated with AI-generated content. This feature enhances user experience by providing a consistent and clear indication of AI involvement across the platform.\n\n\n - **Coral theme**\n\nCoral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences.\n\n\n - **[ECMAScript 2021 \\(ES12\\) JavaScript mode supports additional scripting features](https://www.servicenow.com/docs/access?context=javascript-engine-feature-support&family=zurich&ft:locale=en-US)**\n\nUse additional scripting features, including Promises and Async await, in applications or scripts that use the ECMAScript 2021 \\(ES12\\) JavaScript mode.\n\n- **[Stream multipart responses with REST APIs](https://www.servicenow.com/docs/access?context=r_AvailableSystemProperties&family=zurich&ft:locale=en-US)**\n\nStream multipart responses rather than buffering responses until complete by default with REST APIs that support the multipart/mixed requests, such as the Batch API. The **glide.rest.serialize.disable\\_response\\_stream\\_buffering** system property controls this behavior and applies only to instances configured with Application Delivery Controller, version 2 \\(ADCv2\\).\n\n- **[Additional field types supported in a configurable workspace](https://www.servicenow.com/docs/access?context=r_FieldTypes&family=zurich&ft:locale=en-US)**\n\nThe following field types are now supported for use in a configurable workspace:\n\n - **datetime**\n - **email\\_script**\n - **int**\n - **integer\\_time**\n - **related\\_tags**\n - **user\\_input**\n- **[Vertical layout configuration for radio buttons in a configurable workspace](https://www.servicenow.com/docs/access?context=r_FieldTypes&family=zurich&ft:locale=en-US)**\n\nConfigurable workspaces now support a vertical layout configuration of radio buttons.\n\n- **[More dictionary attributes available for selected fields in a configurable workspace](https://www.servicenow.com/docs/access?context=r_FieldTypes&family=zurich&ft:locale=en-US)**\n\nApplicable fields used in a configurable workspace now support the following dictionary attributes:\n\n - **choice**\n - **decimal**\n - **float**\n - **html\\_editor**\n - **integer**\n - **ip\\_addr**\n - **is\\_searchable\\_choice**\n - **phone\\_number\\_e164**\n - **readonly\\_clickthrough**\n - **ref\\_ac\\_columns**\n - **translated\\_html\\_editor**\n - **types**\n- **[New plugins available for the TinyMCE HTML editor](https://www.servicenow.com/docs/access?context=configuring-the-html-plugins-for-tinymce&family=zurich&ft:locale=en-US)**\n\nThe TinyMCE HTML editor now supports two new plugins in Core UI and configurable workspaces:\n\n - The Image Editing \\(editimage\\) plugin adds a contextual editing toolbar to images in the editor.\n - The Help plugin \\(help\\) enables you to check shortcuts and keyboard navigation for accessibility.\n- **[New run types available for scheduled jobs](https://www.servicenow.com/docs/access?context=c_ScheduledJobs&family=zurich&ft:locale=en-US)**\n\nThe following run types are now available for all scheduled job types, enabling flexible scheduling:\n\n - **Day and Month in Year**\n - **Day in Week in Month in Year**\n - **Week in Month**\nThe new run types are available in the following standard scheduled job types:\n\n - **Scheduled Email of Report**\n - **Scheduled Entity Generation**\n - **Scheduled Script Execution**\nTo enable these new run types in other scheduled job child tables, you must configure your applicable form view to include the fields **Day**, **Month**, and **Year**. For more information, see [Enable run types for scheduled job child tables](https://www.servicenow.com/docs/access?context=customize-run-times-for-scheduled-jobs&family=zurich&ft:locale=en-US).\n\n- **[New advanced options available for scheduled jobs](https://www.servicenow.com/docs/access?context=c_ScheduledJobs&family=zurich&ft:locale=en-US)**\n\nThe following new advanced options are available when configuring scheduled jobs, offering greater flexibility in job planning, execution, and recurrence:\n\n - **Starting**\n - **Ending**\n - **Repeat every**\n- **[Export lists to Google Sheets](https://www.servicenow.com/docs/access?context=setup-gsheet-export&family=zurich&ft:locale=en-US)**\n\nExport your lists to Google Sheets directly from the Export menu.\n\n\n |
| \n\nAustralia\n\n | \n\n- **[Data Egress and Usage by Domain tabs added to the Inbound API Integration Usage dashboard](https://www.servicenow.com/docs/access?context=inbound-api-integration-usage-dashboard&family=australia&ft:locale=en-US)**\n\nView data volumes returned in integration responses and monitor domain-level usage.\n\n\n - **[Country setting added to Language and Region preferences](https://www.servicenow.com/docs/access?context=next-experience-language-preferences&family=australia&ft:locale=en-US)**\n\nUsers can select their country from the Next Experience language and region preferences.\n\n- **[New options for date and time format in the User record](https://www.servicenow.com/docs/access?context=user&family=australia&ft:locale=en-US)**\n\nUsers can select from new options for Date format and Time format in the User record.\n\n- **[Control whether date and time formats reflect the user locale by default](https://www.servicenow.com/docs/access?context=set-localization-props&family=australia&ft:locale=en-US)**\n\nConfigure date and time formats to reflect the user locale when no date or time format has been selected in user preferences through the **glide\\_i18n.date.default\\_to\\_locale** system property.\n\n- **[Control how to set the language for guest users](https://www.servicenow.com/docs/access?context=set-localization-props&family=australia&ft:locale=en-US)**\n\nUse a guest user's IP address to set their language through the **glide\\_i18n.ip\\_geolocation** system property.\n\n- **[Activate additional choices for countries](https://www.servicenow.com/docs/access?context=activate-country-choices&family=australia&ft:locale=en-US)**\n\nActivate additional choices for countries in the Next Experience language and region preferences or in a User record.\n\n- **[ECMAScript 2021 \\(ES12\\) JavaScript mode supports additional scripting features](https://www.servicenow.com/docs/access?context=javascript-engine-feature-support&family=australia&ft:locale=en-US)**\n\nUse additional scripting features in applications or scripts that use the ECMAScript 2021 \\(ES12\\) JavaScript mode.\n\n- **[JavaScript engine updated with changes from the Rhino engine](https://www.servicenow.com/docs/access?context=updates-javascript-engine&family=australia&ft:locale=en-US)**\n\nThe JavaScript engine on the ServiceNow AI Platform was updated to incorporate changes from the open-source Rhino JavaScript engine.\n\n- **[New Normalization Data Services system property](https://www.servicenow.com/docs/access?context=r_AvailableSystemProperties&family=australia&ft:locale=en-US)**\n\nCreate duplicate records in core\\_company extension tables by setting the **com.glide.acl\\_check\\_all\\_filter\\_on\\_new** system property to true to reference account records.\n\n- **[System properties secured by default](https://www.servicenow.com/docs/access?context=r_AvailableSystemProperties&family=australia&ft:locale=en-US)**\n\nGlide properties that can impact instance security are set to secure values by default. For more information about which system properties are affected and why, see the [Glide Property Hardening \\[KB1982254\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1982254) article in the Now Support Knowledge Base.\n\n- **[Tracking records in unauthenticated users' sessions](https://www.servicenow.com/docs/access?context=web-embeddables&family=australia&ft:locale=en-US)**\n\nTrack records created, modified, or deleted by unauthenticated users to enable session-based ACL access on public forms, portals, or workflows.\n\n- **[Manage guest user access to records](https://www.servicenow.com/docs/access?context=web-embeddables&family=australia&ft:locale=en-US)**\n\nRestrict guest user access to records they created or updated during their current session using the 'is in session' condition builder on the ACL form for Sys ID fields.\n\n- **[Session-based guest access](https://www.servicenow.com/docs/access?context=web-embeddables&family=australia&ft:locale=en-US)**\n\nManage REST GraphQL security with path-based ACLs that are enforced without needing to require authentication for access to an API.\n\n\n - **[Support duplicate company names across core\\_company extension tables](https://www.servicenow.com/docs/access?context=enhanced-nds-for-duplicate-records&family=australia&ft:locale=en-US)**\n\nAvoid normalization conflicts when creating records with the same company name in both the Company \\[core\\_company\\] table and its extension tables, such as Customer Account \\[customer\\_account\\], using the **glide.cmdb.canonical.use\\_base\\_core\\_company\\_only** property. It ensures that uniqueness enforcement applies only to base core\\_company records.\n\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nZurich\n\n | \n\nNo updates for this release.\n\n |
| \n\nAustralia\n\n | \n\nNo updates for this release.\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nZurich\n\n | \n\nStarting with the Zurich release, Application Insights is no longer deployed, enhanced, or supported. Instead, [Overview of Instance Observer](https://www.servicenow.com/docs/access?context=io-overview&family=zurich&ft:locale=en-US) offers a powerful solution for enhancing system performance. Contact your account manager to discover more. For details, see the [Deprecation Process \\[KB0867184\\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base.\n\n - The **glide.script.use.sandbox** system property has been removed. The script sandbox is enabled by default.\n- Dynamic groups have been removed. Instead, use dynamic attributes in dynamic categories to simplify administration and improve the dynamic schema user experience.\n\n |
| \n\nAustralia\n\n | \n\nStarting with the Australia release, the legacy user interfaces commonly referred to as UI11 and UI15 are deprecated. These legacy UIs no longer receive enhancements or defect fixes, and will no longer be supported. Certain system features might continue to display through legacy rendering paths \\(for example, printer‑friendly views\\) and will be addressed case by case as part of ongoing platform improvements. Use the Next Experience for a modern, accessible, unified interface. For information about activating the Next Experience UI, see [Activation considerations](https://www.servicenow.com/docs/access?context=next-experience-adoption-paths&family=australia&ft:locale=en-US).\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nZurich\n\n | \n\n- **Activation information**\n\nThe ServiceNow AI Platform core features are active by default.\n\n\n |
| \n\nAustralia\n\n | \n\n- **Activation information**\n\nThe ServiceNow AI Platform core features are active by default.\n\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nZurich\n\n | \n\nNo updates for this release.\n\n |
| \n\nAustralia\n\n | \n\nNo updates for this release.\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nZurich\n\n | \n\nNo updates for this release.\n\n |
| \n\nAustralia\n\n | \n\nNo updates for this release.\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nZurich\n\n | \n\n- **Accessibility information**\n - **Dark theme**\n\nThe new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability.\n\n\n |
| \n\nAustralia\n\n | \n\n- **Accessibility information**\n\nFormat Painter plugin for TinyMCE enables you to apply consistent font styles, sizes, and table formats within the HTML editor field. This improvement helps users with cognitive disabilities and low vision by reducing confusion and supporting clear, predictable formatting throughout documents. Keyboard navigation is supported, providing added ease of use for keyboard-only users. For more information, see [Configure the HTML toolbar](https://www.servicenow.com/docs/access?context=t_ConfigureTheTinyMCEHTMLToolbar&family=australia&ft:locale=en-US).\n\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nZurich\n\n | \n\nNo updates for this release.\n\n |
| \n\nAustralia\n\n | \n\nNo updates for this release.\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nZurich\n\n | \n\n- Simplify and build queries with fewer conditions by leveraging hierarchical relationships in a condition builder.\n- Use additional scripting features, including Promises and Async await, with the ECMAScript 2021 \\(ES12\\) JavaScript mode.\n- Define dynamic categories and dynamic attributes once and reuse them using dynamic namespaces across multiple tables and dynamic attribute store fields.\n\n See [Administer](https://www.servicenow.com/docs/access?context=intro-now-platform-landing&family=zurich&ft:locale=en-US) for more information.\n\n Use the Feature Preview Program to choose which pre-release capabilities to activate and test on your instance.\n\n |
| \n\nAustralia\n\n | \n\nControl whether read-only fields can be updated through client scripts and server-side operations by configuring read-only options.\n\n See [Administer the ServiceNow AI Platform](https://www.servicenow.com/docs/access?context=intro-now-platform-landing&family=australia&ft:locale=en-US) for more information.\n\n Use the Feature Preview Program to choose which pre-release capabilities to activate and test on your instance.\n\n |