Consolidated page of all release notes for Change Management from Xanadu 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 Xanadu 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.
| Release |
Release notes |
Xanadu |
No updates for this release. |
Yokohama |
No updates for this release. |
Zurich |
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.
|
Australia |
No updates for this release. |
New features
Between your current release family and Australia, new features were introduced for Change Management.
| Release |
Release notes |
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.
- 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.
|
Zurich |
- Control opening of CAB meetings
- 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.
- Track conflict detection
- 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
- 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
-
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
- 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
- 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
-
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.
| Release |
Release notes |
Xanadu |
No updates for this release. |
Yokohama |
No updates for this release. |
Zurich |
|
Australia |
No updates for this release. |
Removed
Between your current release family and Australia, some Change Management features or functionality were removed.
| 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.
|
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.
| Release |
Release notes |
Xanadu |
No updates for this release. |
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Australia |
No updates for this release. |
Activation information
Review information on how to activate Change Management.
| Release |
Release notes |
Xanadu |
No updates for this release. |
Yokohama |
Change Management is a ServiceNow AI Platform feature that is active by default. |
Zurich |
Change Management is a ServiceNow AI Platform feature that is active by default.
|
Australia |
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.
| Release |
Release notes |
Xanadu |
No updates for this release. |
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.
| Release |
Release notes |
Xanadu |
No updates for this release. |
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.
| Release |
Release notes |
Xanadu |
No updates for this release. |
Yokohama |
No updates for this release. |
Zurich |
|
Australia |
- 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.
| Release |
Release notes |
Xanadu |
No updates for this release. |
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.
| 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 for more information.
|
Zurich |
See Change Management 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 for more information.
|