Consolidated page of all release notes for Service Exchange from Yokohama to Zurich.
How to use this page
To help you prepare for your upgrade, we have combined the cross-family Service Exchange release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Zurich.
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 Service Exchange to Zurich
Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed.
| Release |
Release notes |
Yokohama |
- When using Service Exchange for Providers and Service Exchange for Consumers in a single instance, you must upgrade both applications simultaneously to the same version to maintain compatibility.
- The Service Exchange Global Script Include is automatically installed or updated when you install the Service Exchange application on the following platform versions:
- Washington DC Patch 9
- Xanadu Patch 4
- Yokohama
- Service Exchange 2.x.x, which was first released with the Xanadu release, does not support migration of Service Exchange (Legacy) versions. If you are using a Service Exchange (Legacy) version, before you upgrade to the Yokohama release, you must follow instructions in the Service Exchange for Providers (Legacy) - Migration Utility [KB1499823] article in the Now Support Knowledge Base to migrate your configuration data.
- If you are upgrading from Service Exchange version 1.x.x, follow the steps in Upgrade Guide - Service Exchange for Providers and Consumers application (v2.x.x release) [KB1700387] to migrate your Service Exchange applications.
- Due to the introduction of mismatched version support, new entitlements cannot be activated until both the consumers and providers upgrade to Service Exchange version 2.x.x. Older active entitlements will continue to work but new ones cannot be activated.
- If you upgrade to Service Exchange version 2.0.55 with Sales Customer Relationship Management plug-in version 1.0.4 before upgrading the platform to the Yokohama release, the new Deny ACLs will not be installed. To ensure the Deny ACLs get installed, after upgrading to Yokohama, you must click Repair to reinstall the Service Exchange application.
|
Zurich |
|
New features
Between your current release family and Zurich, new features were introduced for Service Exchange.
| Release |
Release notes |
Yokohama |
- Remote Catalog Item Client Scripts
- Provider: Perform more complex tasks and gain better control over the completeness and correctness of catalog requests from the consumer by including catalog client scripts, UI Policy scripts, and other common scripts that
consumers can choose to include for Remote Catalog items.
- Copy From Service Catalog Item to Remote Catalog Item
- Providers: Eliminate the need to re-create catalog items manually in the Service Exchange remote catalog by copying single and multiple catalog items through the UI to remote record producers that can be synchronized to the consumer instance.
- Transform Mapping Assist
- Providers: Streamline the transformation mapping process and reduce errors by generating transform mappings between provider and consumer tables automatically using the Transform Mapping Assist feature that leverages the NOW
large language model (LLM).
- Consumer Variable Sets
- Consumers: Manage requested content and flow better by adding additional variables to add customization to your remote record producers.
|
Zurich |
- Foundation data sync
- Reduce manual effort, and eliminate the need to share data externally by sharing selected foundational data types with your consumers on a scheduled cadence. This data transfer supports the service life cycle by providing
foundational data context for operational workflows. The supported tables are CMDB (CIs), CMDB Relationship, Asset, User, Group, Location, Company, and Department.
- Journal field framework
-
- Write journal entries as a named user instead of using a generic company name to enhance authenticity and accountability.
- Maintain a complete historical record across instances by synchronizing previous journal entries between provider and consumer instances.
- Ensure that all critical operational updates remain current by mapping and synchronizing any journal-type field between provider and consumer instances.
- Flow action
- Ensure that Remote Tasks and Remote Record Producers continue to function correctly as you adopt newer revisions by maintaining flow compatibility across configuration revisions using four new Flow Actions that preserve
mapped variable integrity.
- Magic links
- Convert regular links sent from a provider instance into magic links that enable consumer users to directly access the linked resource in the provider instance without having to manually log in.
|
Changes
Between your current release family and Zurich, some changes were made to existing Service Exchange features.
| Release |
Release notes |
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Removed
Between your current release family and Zurich, some Service Exchange features or functionality were removed.
| Release |
Release notes |
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Deprecations
Between your current release family and Zurich, some Service Exchange features or functionality were deprecated.
| Release |
Release notes |
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Activation information
Review information on how to activate Service Exchange.
| Release |
Release notes |
Yokohama |
Install Service Exchange by requesting it from the ServiceNow Store. |
Zurich |
Install Service Exchange by requesting it from the ServiceNow Store.
|
Additional requirements
If any additional requirements were introduced or changed for Service Exchange we have noted them here.
| Release |
Release notes |
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Browser requirements
If any specific browser requirements were introduced or changed for Service Exchange we have noted them here.
| Release |
Release notes |
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Accessibility information
Review details on accessibility information for Service Exchange, such as specific requirements or compliance levels.
| Release |
Release notes |
Yokohama |
No updates for this release. |
Zurich |
|
Localization information
If there are specific localization considerations for Service Exchange we have noted them here.
| Release |
Release notes |
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Highlight information
If there are specific highlight considerations for Service Exchange we have noted them here.
| Release |
Release notes |
Yokohama |
- Providers can now include client and UI policy scripts in remote record producers, which consumers can review and approve.
- Providers can now copy local catalog items to Service Exchange as remote record producers either in bulk or individually.
- Providers can simplify and streamline choice-based transform mapping with ServiceNow
Now Assist.
- Consumers can now add variables to remote record producers for use in consumer pre-flows.
See Service Exchange for more information.
|
Zurich |
- Streamline data replication from provider to consumer instances with foundation data sync.
- Enable seamless collaboration between provider and consumer with enhanced journal entry support.
- Enable consumer users to access linked resources in the provider instance using magic links.
See Service Exchange for more information.
|