--- sourceDocument: yokohama Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/delta-xanadu-yokohama Release : - yokohama ft:locale : - en-US ft:publication_title : - yokohama Combined Product Files ft:clusterId : - delta3yx bundleId : - delta3yx --- # Combined Change Management release notes for upgrades from Xanadu to Yokohama # Combined Change Management release notes for upgrades from Xanadu to Yokohama {#ariaid-title1} Release version: Yokohama Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Xanadu to Yokohama This consolidated guide provides essential information for ServiceNow customers upgrading Change Management from the Xanadu release to Yokohama. It highlights new features, important upgrade considerations, deprecated functionality, and security enhancements introduced in Yokohama to help you prepare and optimize your Change Management processes. Show full answer Show less ## Key Features * **snservicedeskagent User Role:** A new role designed for tier 1 service desk agents to streamline information gathering and resolution delivery. It bundles key roles for incident, problem, change, and request management, along with tracked file reading. When the ITSM Gen AI plugin is installed, it also includes knowledge and assist panel user roles. This role supports Service Operations Workspace version 6.1 and later, enhancing operational efficiency for service desk agents. * **Change Model Type Field:** Adds a new "Model" option to the change model Type field, allowing easier identification of changes controlled by a change model. "Model" is set as the default if no Type is specified on a change request. * **No Default Risk Value:** The Risk field on change requests no longer has a default value. It remains "-- None --" until explicitly evaluated, ensuring more accurate risk assessments before change progression. * **Mandatory Field Transition Condition:** Enforces completion of required fields before advancing change request states as defined by the Change Model. This helps change managers maintain data integrity and compliance throughout the change lifecycle. * **Deny-Unless Access Control Lists (ACLs):** Introduces enhanced security by restricting unauthorized access to changerequest and changetask tables for unauthenticated users. This feature requires installation of the ITSM Enhanced Security Features plugin and is recommended to be tested in sub-production environments before production deployment. ## Deprecations and Changes * **Workflows Replaced by Flows:** Change Management workflows have been removed for new customers and replaced by flows, which are customizable and extendable via ServiceNow Workflow Studio and Flow Designer. Existing customers using workflows will remain unaffected. ## Upgrade and Activation Notes * Change Management is an AI Platform feature that is active by default in Yokohama. * There are no additional browser, localization, accessibility, or other requirements introduced in this upgrade. ## Practical Impact for ServiceNow Customers * Upgrade preparation includes reviewing pre- and post-upgrade tasks, especially related to security ACLs and testing in sub-production instances. * The new snservicedeskagent role empowers tier 1 agents to work more efficiently with integrated AI capabilities when applicable. * Mandatory field enforcement and risk assessment changes improve data quality and compliance during change execution. * Security enhancements provide stronger protection for Change Management data from unauthorized access. * Transition from workflows to flows offers greater flexibility and customization for change processes moving forward. Consolidated page of all release notes for Change Management from Xanadu to Yokohama. ## 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 Xanadu to Yokohama. 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 Yokohama Before you upgrade to Yokohama, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-changemanagement-summary__entry__2} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## New features Between your current release family and Yokohama, new features were introduced for Change Management. {#dfrn3-changemanagement-summary__entry__8} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | 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. | [ ] ## Changes Between your current release family and Yokohama, some changes were made to existing Change Management features. {#dfrn3-changemanagement-summary__entry__14} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Removed Between your current release family and Yokohama, some Change Management features or functionality were removed. {#dfrn3-changemanagement-summary__entry__20} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Deprecations Between your current release family and Yokohama, some Change Management features or functionality were deprecated. {#dfrn3-changemanagement-summary__entry__26} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | 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). | [ ] ## Activation information Review information on how to activate Change Management. {#dfrn3-changemanagement-summary__entry__32} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | Activation information : Change Management is a ServiceNow AI Platform feature that is active 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 | |-|-| | Xanadu | No updates for this release. | | Yokohama | 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 | |-|-| | Xanadu | No updates for this release. | | Yokohama | 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 | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Change Management we have noted them here. {#dfrn3-changemanagement-summary__entry__56} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | 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 | |-|-| | Xanadu | No updates for this release. | | 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. | [ ]