Combined Service Exchange release notes for upgrades from Yokohama to Zurich

zurich Combined Product Files

Release

zurich

ft:locale

en-US

ft:publication_title

zurich Combined Product Files

ft:clusterId

delta3zy

bundleId

delta3zy

Combined Service Exchange release notes for upgrades from Yokohama to Zurich

Release version: Zurich

Updated August 11, 2026

6 minutes to read

Summarize

Summarized using AI

Summary of Combined Service Exchange release notes for upgrades from Yokohama to Zurich

This consolidated guide covers important information and enhancements for ServiceNow customers upgrading Service Exchange from Yokohama to Zurich releases. It includes critical pre- and post-upgrade tasks, compatibility notes, new features, and activation instructions to help ensure a smooth transition and continuous service operation.

Show full answer Show less

Upgrade Considerations

Simultaneous Upgrade: When using Service Exchange for both Providers and Consumers on a single instance, upgrade both applications simultaneously to the same version to maintain compatibility.
Legacy Migration: Service Exchange Legacy versions are not supported for direct migration in Yokohama or Zurich. Follow the Service Bridge for Providers (Legacy) Migration Utility documentation before upgrading.
Version 1.x.x Migration: Customers upgrading from version 1.x.x must follow the Upgrade Guide for Service Bridge for Providers and Consumers (v2.x.x release) to migrate applications properly.
Entitlement Activation: New entitlements require both consumer and provider to be on Service Exchange version 2.x.x; existing entitlements remain active.
Deny ACLs Installation: If upgrading Service Exchange version 2.0.55 with Sales and Order Management plug-in 1.0.4 before platform upgrade, run a Repair on the Service Exchange application post-upgrade to install Deny ACLs correctly.
Global Script Include: Automatically installed or updated when installing Service Exchange on Washington DC Patch 9, Xanadu Patch 4, or Yokohama platforms.

New Features

Between Yokohama and Zurich releases, several enhancements improve control, automation, and usability:

Remote Catalog Item Client Scripts (Yokohama): Providers can include client scripts and UI policies in remote catalog items to enhance validation and user experience for consumers.
Copy From Service Catalog to Remote Catalog (Yokohama): Providers can copy single or multiple catalog items to remote record producers to avoid manual re-creation, streamlining synchronization.
Transform Mapping Assist (Yokohama): Automated generation of transform mappings between provider and consumer tables using ServiceNow’s large language model to reduce errors and simplify integration setup.
Consumer Variable Sets (Yokohama): Consumers can add extra variables to remote record producers, allowing greater customization of request flows.
Foundation Data Sync (Zurich): Scheduled syncing of foundational data types (including CMDB CIs, relationships, assets, users, groups, locations, companies, and departments) from providers to consumers reduces manual effort and improves operational workflows.
Journal Field Framework (Zurich): Enhances accountability by writing journal entries as named users, synchronizing journal entries across provider and consumer instances for complete historical records.
Flow Action Enhancements (Zurich): Introduces four new flow actions to maintain compatibility of Remote Tasks and Remote Record Producers across configuration revisions, preserving mapped variable integrity.
Magic Links (Zurich): Converts provider instance links into magic links that allow consumer users direct access to provider resources without manual login, improving collaboration.

Changes, Removals, and Deprecations

No updates, removals, or deprecations were noted for Service Exchange features in either Yokohama or Zurich releases.

Activation and Additional Information

Service Exchange installation requires requesting the application from the ServiceNow Store for both Yokohama and Zurich.
No new browser, accessibility, localization, or additional requirements have been introduced or changed.

Practical Implications for ServiceNow Customers

By following upgrade guidelines and leveraging new features introduced through Yokohama and Zurich releases, customers can:

Ensure seamless compatibility between Provider and Consumer instances during upgrades.
Automate and simplify catalog item synchronization and data transformation tasks.
Enhance data sharing and operational collaboration via foundation data sync and journal synchronization.
Improve user experience with client scripts, variable customization, and easy access through magic links.
Maintain operational integrity of flows and security configurations during platform updates.

Adhering to these notes and instructions will help customers maintain stable and feature-rich Service Exchange environments during and after their upgrade to Zurich.

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 Bridge 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 Bridge 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 and Order 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	Service Exchange version 2.x.x: Which was first released with the Xanadu release, doesn’t support migration of Service Exchange (Legacy) versions. Service Exchange (Legacy) version: Before you upgrade to the Zurich release, follow instructions in the Service Bridge for Providers (Legacy) - Migration Utility [KB1499823] article in the Now Support Knowledge Base to migrate your configuration data. Service Exchange version 1.x.x: When upgrading, follow the steps in the Upgrade Guide - Service Bridge for Providers and Consumers application (v2.x.x release) [KB1700387] article in the Now Support Knowledge Base to migrate your Service Exchange applications. Service Exchange version 2.x.x: Due to the introduction of mismatched version support, new entitlements can’t be activated until both the consumers and providers upgrade to Service Exchange version 2.x.x. Older active entitlements continue to work but new ones can’t be activated. When you upgrade to Service Exchange version 2.0.55 with Sales and Order Management plug-in version 1.0.4, before upgrading the platform to the Zurich release, new Deny ACLs aren't installed. To ensure the Deny ACLs get installed, after upgrading to Zurich, select Repair to reinstall the Service Exchange application. 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. When you install the Service Exchange application, the Service Exchange Global Script Include is automatically installed or updated on the following platform versions: Washington DC patch 9 Xanadu patch 4 Yokohama 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.