Combined Change Management release notes for upgrades from Vancouver to Yokohama

Consolidated page of all release notes for Change Management from Vancouver 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 Vancouver 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.

Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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.

Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	User role for service desk agents 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 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 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 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 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.

Release	Release notes
Vancouver	Activate Change Management - Data Archiving Archive the change requests, change tasks, and conflict data in your instance per your data retention policy through the updated archive rule, which enables you to include the conflict table with change requests and change tasks.
Washington DC	No updates for this release.
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.

Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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.

Deprecations

Between your current release family and Yokohama, some Change Management features or functionality were deprecated.

Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Activation information

Review information on how to activate Change Management.

Release	Release notes
Vancouver	Change Management is a ServiceNow AI Platform feature that is active by default.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	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.

Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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.

Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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.

Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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.

Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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.

Release	Release notes
Vancouver	Provides an extension of the existing data retention capabilities by using the conflict table. See Change Management for more information.
Washington DC	No updates for this release.
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 for more information.