--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-yokohama-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3ay bundleId : - delta3ay --- # Combined Change Management release notes for upgrades from Yokohama to Australia # Combined Change Management release notes for upgrades from Yokohama to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 9 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 Yokohama to Australia This consolidated release note provides ServiceNow customers with essential information for upgrading Change Management from Yokohama through Zurich to Australia releases. It highlights new features, important upgrade considerations, changes, deprecated functionality, and accessibility improvements across these releases, helping customers prepare and optimize their Change Management processes effectively. Show full answer Show less ## Important Upgrade Information * **Zurich Release:** Transitioned conflict detection mechanism from Progress Workers to Flow using the Change Management Worker table, controlled via the `change.conflict.useprogressworker` system property. UI macros were updated accordingly to support this change. * The **ITSM Enhanced Security Features plugin** (`com.snc.itsm.enhancedsecurity`) is automatically activated on upgrades to Zurich and Australia, enforcing stricter "deny unless authenticated" ACLs on core ITSM tables like `changerequest` and `changetask`. Customers should evaluate impacts in sub-production before enabling in production and can contact ServiceNow Support for ACL deactivation assistance if needed. ## New Features * **snservicedeskagent User Role (Yokohama):** Designed for tier 1 service desk agents, this role streamlines information gathering and resolution delivery, incorporating roles for incident, problem, change, and request management. It integrates with ITSM Gen AI for enhanced assistance and is compatible with Service Operations Workspace 6.1+. * **Change Model Enhancements:** * A new "Model" option in the change model Type field identifies controlled changes more clearly. * The Risk field on change requests no longer defaults to a value, ensuring risk is explicitly evaluated before progressing. * Mandatory fields must be completed before state transitions as defined by the Change Model, enforcing data integrity. * **Security Improvements:** Deny-unless ACLs restrict unauthorized access to core change tables, enhancing data protection when the ITSM Enhanced Security Features plugin is installed. * **Zurich Features:** * Control CAB meeting openings via system property (`snchangecab.com.snc.changemanagement.cab.usesowmeeting`). * Track conflict detection progress using flows and the Change Management Worker table with configurable maximum conflict records via `change.conflict.maxcount`. * **Australia Features:** * Introduce a granular admin role (`snchangeadmin`) for fine-tuned permission management in Change Management. * Ability to exclude specific change requests from conflict detection to reduce noise and improve accuracy. * Change templates now support mandatory and read-only field policies aligned with change models, enabling standardization and compliance. * Enhanced data model for change templates offers better categorization and role-based access without impacting existing standard changes. ## Changes and Deprecations * **Zurich:** Coral theme became the default for portals and mobile, offering a modern, brand-neutral appearance with a dark theme option. * **Workflow to Flow Transition (Yokohama):** Legacy Change Management workflows have been replaced by Flow Designer flows for new customers, while existing workflows remain supported. * **Service Operations Workspace:** ITIL users can propose standard change templates directly within the workspace. ## Accessibility and Usability Enhancements * **Zurich:** The Coral theme includes a dark mode option to reduce eye strain and enhance readability. * **Australia:** The "Create a change request" page now supports content reflow and zoom up to 400% without loss of functionality, improving accessibility for users with low vision or varying device constraints. This reflow can be disabled via system properties if desired. ## Activation and Additional Notes * Change Management is an AI Platform feature active by default across all releases mentioned. * No additional browser or localization requirements were introduced in these releases. * Customers are advised to test new security ACLs and plugin activations in sub-production environments before production deployment. ## Practical Benefits for ServiceNow Customers * Streamlined role management improves efficiency for service desk agents and administrators. * Enhanced security controls protect sensitive change data and enforce authentication. * Improved change request data quality through mandatory field validation tied to change models. * Greater flexibility and control over conflict detection and CAB meeting management. * Standardized change templates drive compliance and reduce manual errors. * Accessibility improvements enhance usability for diverse user needs and environments. Consolidated page of all release notes for Change Management from Yokohama 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 Yokohama 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 | |-|-| | Yokohama | No updates for this release. | | 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__10} | Release | Release notes | |-|-| | Yokohama | [User role for service desk agents](https://www.servicenow.com/docs/access?context=installed-with-cm-itsm-roles&family=yokohama&ft:locale=en-US) : With the sn_service_desk_agent user role, increase operational efficiency by streamlining the process of asking about, gathering, and verifying information, as well as delivering quick resolutions. This role is designed for tier 1 service desk agents and is accessible when the ITSM Roles plugin (com.snc.itsm.roles) installed. The sn_service_desk_agent role includes the following roles: * sn_incident_write * sn_problem_write * sn_change_write * sn_request_write * tracked_file_reader Additionally, with the installation of the ITSM Gen AI (com.sn.itsm.gen.ai) plugin, the knowledge_user and now_assist_panel_user roles are integrated within the sn_service_desk_agent role. The sn_service_desk_agent user role can be used starting with Service Operations Workspace version 6.1. [Change model Type field](https://www.servicenow.com/docs/access?context=t_CreateAChange&family=yokohama&ft:locale=en-US) : A new Model option has been added to the change model Type field to help users identify a change that is controlled by a change model. Model is the default if a Type has not been set for the change request of a certain change model. [No default Risk value for change requests](https://www.servicenow.com/docs/access?context=t_CreateAChange&family=yokohama&ft:locale=en-US) : There is no longer a default value for the Risk field on the Change Request table. The Risk value is set to -- None -- until the risk is evaluated for the change request. This change ensures that no risk value is pre-assigned, allowing for a more accurate assessment before advancing the change [Mandatory field transition condition](https://www.servicenow.com/docs/access?context=create-a-change-model&family=yokohama&ft:locale=en-US) : Ensure mandatory fields are completed before advancing through states for a change request, as defined by the Change Model. This feature enables change managers to mandate the completion of required fields before states can progress according to the Change Model. [Deny-unless ACLs on core tables](https://www.servicenow.com/docs/access?context=features-itsm-enhanced-security-change&family=yokohama&ft:locale=en-US) : Prevent unauthorized access to change_request and change_task tables using deny-unless ACLs. The deny-unless ACLs restrict access on these tables for a non-authenticated user to perform actions such as read, write, delete, or create. This feature is available for new or zBoot customers with the installation of the ITSM Enhanced Security Features (com.snc.itsm.enhanced_security) plugin. Existing or upgrade customers must test and evaluate in their sub production instance before installing the plugin and implementing the security change in their production instance. | | 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__18} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | 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__26} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | 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__34} | Release | Release notes | |-|-| | Yokohama | Change Management workflows have been removed and replaced by flows for new customers. Existing customers that use these workflows are unaffected. The flows are available to both new and existing customers. You can use ServiceNow® Workflow Studio to customize or extend these flows. For more information, see [Flow Designer](https://www.servicenow.com/docs/access?context=flow-designer&family=yokohama&ft:locale=en-US). | | 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__42} | Release | Release notes | |-|-| | Yokohama | Activation information : Change Management is a ServiceNow AI Platform feature that is active by default. | | 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__50} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | 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__58} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | 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__66} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | 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__74} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | 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__82} | Release | Release notes | |-|-| | Yokohama | * Increase operational efficiency of tier 1 service desk agents with the dedicated sn_service_desk_agent role. * Require specified field details to be updated before transitioning the state of a change request by converting existing optional fields to mandatory fields. * Restrict unauthorized access to Change Management tables using deny ACLs. See [Change Management](https://www.servicenow.com/docs/access?context=c_ITILChangeManagement&family=yokohama&ft:locale=en-US) for more information. | | 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. | [ ]