Combined Operational Resilience release notes for upgrades from Yokohama to Australia
Consolidated page of all release notes for Operational Resilience from Yokohama to Australia.
How to use this page
To help you prepare for your upgrade, we have combined the cross-family Operational Resilience release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Australia.
Important information for upgrading Operational Resilience to Australia
Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed.
| Release | Release notes |
|---|---|
Yokohama |
No updates for this release. |
Zurich |
After upgrading to Operational Resilience version 21.0.x, rerun the Update CSDM and other dependencies scheduled job to populate the additional metadata that was introduced in this release. |
Australia |
Beginning with Operational Resilience release 22.0.x, the following scheduled jobs are deactivated for new installations by default:
|
New features
Between your current release family and Australia, new features were introduced for Operational Resilience.
| Release | Release notes |
|---|---|
Yokohama |
|
Zurich |
|
Australia |
|
Changes
Between your current release family and Australia, some changes were made to existing Operational Resilience features.
| Release | Release notes |
|---|---|
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Australia |
|
Removed
Between your current release family and Australia, some Operational Resilience features or functionality were removed.
| 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 Operational Resilience features or functionality were deprecated.
| Release | Release notes |
|---|---|
Yokohama |
No updates for this release. |
Zurich |
The Operational Resilience application previously stored the entire dependency chain in the [sn_oper_res_profile] table, which resulted in redundant data and potential performance issues. The Update CSDM and other dependencies scheduled job script has been optimized to address this issue. Any node can now be at the top level. Data retrieval is more efficient because you can store the impacted objects in a single table. |
Australia |
No updates for this release. |
Activation information
Review information on how to activate Operational Resilience.
| Release | Release notes |
|---|---|
Yokohama |
Install Operational Resilience by requesting it from the ServiceNow Store. Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes. |
Zurich |
Install Operational Resilience by requesting it from the ServiceNow Store. |
Australia |
Install Operational Resilience by requesting it from the ServiceNow Store. |
Additional requirements
If any additional requirements were introduced or changed for Operational Resilience we have noted them here.
| 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 Operational Resilience we have noted them here.
| Release | Release notes |
|---|---|
Yokohama |
Business Continuity Management requires the following browsers:
|
Zurich |
Operational Resilience requires the following browsers:
|
Australia |
No updates for this release. |
Accessibility information
Review details on accessibility information for Operational Resilience, such as specific requirements or compliance levels.
| Release | Release notes |
|---|---|
Yokohama |
No updates for this release. |
Zurich |
|
Australia |
No updates for this release. |
Localization information
If there are specific localization considerations for Operational Resilience we have noted them here.
| 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 Operational Resilience we have noted them here.
| Release | Release notes |
|---|---|
Yokohama |
See Operational Resilience for more information. |
Zurich |
See Operational Resilience for more information. |
Australia |
See Operational Resilience for more information. |