--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-zurich-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3az bundleId : - delta3az --- # Combined Change Management release notes for upgrades from Zurich to Australia # Combined Change Management release notes for upgrades from Zurich to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Combined Change Management Release Notes for Upgrades from Zurich to Australia This consolidated guide provides ServiceNow customers with essential information on upgrading Change Management from the Zurich release to the Australia release. It summarizes key new features, changes, upgrade considerations, and accessibility improvements introduced across these releases, enabling customers to plan and execute their upgrade effectively while understanding the impact on their Change Management processes. Show full answer Show less ## Important Upgrade Information * **Conflict Detection Update:** Zurich introduced a shift from Progress Workers to Flow-based conflict detection, controlled via the `change.conflict.useprogressworker` system property. A new UI formatter adjusts the conflict detection interface accordingly. * **ITSM Enhanced Security Features Plugin:** Automatically activated during upgrades to both Zurich and Australia, this plugin enforces stricter access controls with "deny unless authenticated" ACL rules on ITSM tables. Customers can revert this with ServiceNow Support assistance if necessary. ## New Features * **Zurich:** * Control opening of CAB meetings through UI properties and Service Operations Workspace integration. * Track conflict detection progress using the Change Management Worker table and Flow system instead of Progress Workers. * Set limits on maximum conflict records generated per conflict type using the `change.conflict.maxcount` system property. * **Australia:** * Introduce a granular admin role (`snchangeadmin`) that consolidates permissions for managing Change Management features, replacing broader admin and ITIL roles. * Allow exclusion of specific change requests from conflict detection to avoid false conflicts. * Enable creation and management of change templates with controlled mandatory and read-only fields, supporting standardization and compliance in change models. * Implement an enhanced data model for change templates providing better categorization and role-based access without impacting existing standard changes. ## Changes to Existing Features * **Zurich:** The Coral theme became the default for new portals, web, and mobile experiences, offering a modern look with brand-neutral illustrations and a dark theme option for improved readability. * **Australia:** No changes reported in this release. ## Activation and Requirements * Change Management is active by default as part of the ServiceNow AI Platform in both Zurich and Australia releases. * No additional Change Management-specific browser or other requirements were introduced. ## Accessibility Enhancements * **Zurich:** The Coral theme includes a dark theme option to reduce eye strain and improve user comfort on web and mobile devices. * **Australia:** The Create a change request page now supports reflow, enabling up to 400% browser zoom without loss of content or functionality. This supports users with low vision by automatically stacking page layouts vertically at high zoom levels. Reflow can be disabled via system properties if needed. ## Practical Benefits for ServiceNow Customers * Improved security posture with automated activation of enhanced security plugins during upgrade. * Greater control and customization of change processes via conflict detection settings and change templates. * Simplified administration through the new granular admin role, reducing permission complexity. * Enhanced user experience with a modern UI theme and accessibility improvements, facilitating adoption and efficiency. ## Next Steps for Customers * Review and complete pre- and post-upgrade tasks outlined to ensure smooth migration. * Evaluate the impact of security ACLs and consult ServiceNow Support if modification is required. * Familiarize administrators with the new `snchangeadmin` role and adjust permissions accordingly. * Leverage change templates to standardize and streamline change request creation. * Test the new conflict detection mechanisms and configure system properties to meet organizational needs. * Explore accessibility options such as dark theme and reflow to enhance usability for all users. Consolidated page of all release notes for Change Management from Zurich to Australia. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Change Management release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Zurich to Australia. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading Change Management to Australia Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-changemanagement-summary__entry__2} | Release | Release notes | |-|-| | Zurich | Upgrade information : As part of the update to use Flow instead of Progress Workers for conflict detection, the Conflict Checker Progress UI Formatter record references a new UI macro, change_conflict_worker_progress_gate. This macro checks the change.conflict.useprogressworker system property to determine the conflict detection mechanism and then displays the corresponding UI macro to work with either Progress Workers or the Change Management Worker table. For more information, see [Conflict detection](https://www.servicenow.com/docs/access?context=c_ConflictDetection&family=zurich&ft:locale=en-US). The ITSM Enhanced Security Features plugin (com.snc.itsm.enhanced_security) is now activated automatically when you upgrade to the Zurich release. Previously, the plugin was activated only on new instances. Activating the plugin adds "deny unless authenticated" access control list (ACL) rules to several IT Service Management tables. To revert to the pre-upgrade behavior, contact ServiceNow Support for a list of ACLs to deactivate on specific tables. As a last resort, Support can run a script that deactivates all the new ACLs. | | Australia | Upgrade information : The ITSM Enhanced Security Features plugin (com.snc.itsm.enhanced_security) is now activated automatically when you upgrade to the Australia release. Previously, the plugin was activated only on new instances. Activating the plugin adds "deny unless authenticated" access control list (ACL) rules to several IT Service Management tables. To revert to the pre-upgrade behavior, contact ServiceNow Support for a list of ACLs to deactivate on specific tables. As a last resort, Support can run a script that deactivates all the new ACLs. | [ ] ## New features Between your current release family and Australia, new features were introduced for Change Management. {#dfrn3-changemanagement-summary__entry__8} | Release | Release notes | |-|-| | Zurich | [Control opening of CAB meetings](https://www.servicenow.com/docs/access?context=attend-cab-meeting-using-cab-workbench&family=zurich&ft:locale=en-US) : Control the opening of a CAB meeting from the CAB Meeting calendar in the CAB Meeting workbench in Service Operations Workspace or in the Core UI through the sn_change_cab.com.snc.change_management.cab.use_sow_meeting system property. For more information, see [Change Management properties](https://www.servicenow.com/docs/access?context=r_ChangeManagementProperties&family=zurich&ft:locale=en-US). [Track conflict detection](https://www.servicenow.com/docs/access?context=c_ConflictDetection&family=zurich&ft:locale=en-US) : Track the progress of conflict detection using the Change - Conflict Detection flow (that runs as a system user) and the Change Management Worker table instead of Progress Workers. You can choose between the Flow and Progress Worker options by updating the change.conflict.useprogressworker system property.A new UI formatter change_conflict_worker_progress_gate.xml has been introduced to the change request form to replace the existing change_request_conflict_progress.xml . This update supports the change.conflict.useprogressworker system property when you upgrade to Zurich. The new formatter displays the same Conflict tab but selects the macro version to render the form according to the value of the new system property. [Define the maximum records for conflict detection](https://www.servicenow.com/docs/access?context=configure-conflict-properties&family=zurich&ft:locale=en-US) : Limit the maximum number of conflict records that can be generated for each conflict type when conflict detection runs through the change.conflict.max_count system property; create this system property if it is not already present. | | Australia | [Granular admin role](https://www.servicenow.com/docs/access?context=installed-with-cm-itsm-roles&family=australia&ft:locale=en-US) : Assign the single feature-specific granular sn_change_admin role to users to grant permission to configure Change Management features and system properties. This role replaces the previous general admin and ITIL roles. The sn_change_admin role includes the sn_change_writer, change_manager, and sn_change_cab.cab_manager roles. [Exclude change request records from conflict check](https://www.servicenow.com/docs/access?context=configure-conflict-properties&family=australia&ft:locale=en-US) : Exclude change requests from the conflict check process by setting the Exclude from conflict detection field to true. This setting also means that the change record is not displayed as a conflicting change when conflict checker is run on other change records. [Create change templates](https://www.servicenow.com/docs/access?context=create-change-template&family=australia&ft:locale=en-US) : Control mandatory and read-only fields for change models by configuring change templates and defining template field policies. Change templates provide baseline standardization for common changes, making changes easier to create as well as driving a higher standard of change and compliance. Similar to the concepts used for existing standard change templates, templates used for change models can be proposed, reviewed, versioned, or retired. [Enhanced data model for change templates](https://www.servicenow.com/docs/access?context=change-data-model&family=australia&ft:locale=en-US) : Use the enhanced data model that supports better categorization and role-based access for change templates for all change models automatically. This feature is optional for newly created standard changes. This data model does not impact the existing standard change catalog and migration of these standard changes is not required. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing Change Management features. {#dfrn3-changemanagement-summary__entry__14} | Release | Release notes | |-|-| | Zurich | Coral theme : Coral 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. [Propose a standard change template in Service Operations Workspace](https://www.servicenow.com/docs/access?context=propose-standard-change-sow&family=zurich&ft:locale=en-US) : As a user with the itil role, you can create a standard change template proposal in Service Operations Workspace. | | Australia | No updates for this release. | [ ] ## Removed Between your current release family and Australia, some Change Management features or functionality were removed. {#dfrn3-changemanagement-summary__entry__20} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Deprecations Between your current release family and Australia, some Change Management features or functionality were deprecated. {#dfrn3-changemanagement-summary__entry__26} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Activation information Review information on how to activate Change Management. {#dfrn3-changemanagement-summary__entry__32} | Release | Release notes | |-|-| | Zurich | Activation information : Change Management is a ServiceNow AI Platform feature that is active by default. | | Australia | Activation information : Change Management is a ServiceNow AI Platform feature that is active by default. The Change Management plugins listed are activated by default. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Change Management we have noted them here. {#dfrn3-changemanagement-summary__entry__38} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Change Management we have noted them here. {#dfrn3-changemanagement-summary__entry__44} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Change Management, such as specific requirements or compliance levels. {#dfrn3-changemanagement-summary__entry__50} | Release | Release notes | |-|-| | Zurich | Accessibility information : Dark theme : The 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. | | Australia | Accessibility information : Reflow for Create a change request page : The Create a change request page now supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. Additionally, content can be enlarged without scrolling in two dimensions at a width equivalent to 320 CSS pixels or a height equivalent to 256 CSS pixels. Page layouts are transformed into a vertical, stacked view automatically when users increase browser zoom to 400%. This enhancement helps users with low vision or who have trouble seeing web content in a browser due to monitor size, device type, poor lighting, or other situations. Reflow can be turned off with a system property for instances, experiences, and pages. | [ ] ## Localization information If there are specific localization considerations for Change Management we have noted them here. {#dfrn3-changemanagement-summary__entry__56} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Change Management we have noted them here. {#dfrn3-changemanagement-summary__entry__62} | Release | Release notes | |-|-| | Zurich | * Review and authorize change requests and review recently implemented changes in the Change Advisory Board Workbench in the Service Operations Workspace (SOW). * Track conflict detection using the Change - Conflict Detection flow and the Change Management Worker table instead of Progress Workers. * Limit the number of conflict records for each conflict type through the change.conflict.max_count system property. * Coral is the new default theme for Next Experience and Core UI, offering a more modern experience. See [Change Management](https://www.servicenow.com/docs/access?context=c_ITILChangeManagement&family=zurich&ft:locale=en-US) for more information. | | Australia | * Configure the properties in Change Management application using the sn_change_admin role. * Manage conflict detection for change request using the new Exclude from conflict detection option. * Configure change templates with a specific change model. * Use change templates to manage the change request creation process. See [Change Management](https://www.servicenow.com/docs/access?context=c_ITILChangeManagement&family=australia&ft:locale=en-US) for more information. | [ ]