--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-yokohama-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3ay bundleId : - delta3ay --- # Combined Service Exchange (formerly Service Bridge) release notes for upgrades from Yokohama to Australia # Combined Service Exchange (formerly Service Bridge) release notes for upgrades from Yokohama to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 10 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Combined Service Exchange Release Notes for Upgrades from Yokohama to Australia This consolidated release note provides essential information for ServiceNow customers upgrading Service Exchange (formerly Service Bridge) from Yokohama through to the Australia release. It highlights new features, important upgrade considerations, changes, and enhancements to help customers prepare, execute, and optimize their upgrade process effectively. Show full answer Show less ## Important Upgrade Considerations * **Upgrade Timing:** Do not upgrade your ServiceNow instance to Australia if you depend on Service Exchange until Australia Patch 1 is available due to a known RPS issue affecting functionality. * **Migration Support:** Service Exchange version 2.x.x does not support migrating legacy versions directly. Customers must use documented migration utilities and upgrade guides available in the Now Support Knowledge Base for legacy and 1.x.x versions. * **Compatibility:** Both provider and consumer applications need simultaneous upgrades to the same Service Exchange version to avoid version mismatches and health dashboard issues. * **Post-Upgrade Tasks:** Running and validating the post-upgrade scan suite is critical to identify and resolve any issues. * **Special Cases:** For instances with Sales Customer Relationship Management version 1.0.4, a repair install is required post-upgrade to enable new Deny ACLs. OAuth grant type migration from authorization code to client credentials is required for Service Exchange 2.3.x to prevent authentication errors. ## Key Features Introduced * **Yokohama Enhancements:** Added support for Remote Catalog Item Client Scripts, enabling providers to apply complex validations on consumer requests, and the ability to copy catalog items to remote catalogs. Transform Mapping Assist, powered by the Now LLM, automates transform mappings to reduce errors. Consumer Variable Sets enhance customization of remote record producers. * **Zurich Enhancements:** Foundation Data Sync allows scheduled sharing of foundational CMDB and user data to consumers, improving operational workflows. The Journal Field Framework now supports named user journal entries and synchronization of historical journal data. Flow actions preserve variable integrity during configuration revisions. Magic links enable direct access for consumers to provider resources without manual login. * **Australia Enhancements:** Centralized management via the Connections tab in the Service Exchange Center simplifies connection lifecycle management. Improved consumer onboarding features provide guided registration with progress indicators and actionable messaging. Foundation Data Sync capabilities are expanded to synchronize Knowledge Base articles and better preserve CMDB sysids and relationships. Journal Field Framework supports multi-field mapping and journalinput types. Persona management is simplified with group-based assignments and inheritance. The new ServiceNow AI Platform tiers offer advanced AI capabilities. Service Exchange Knowledge Assistant delivers contextual answers within Now Assist. Auto-onboarding automates onboarding workflows, secure connection establishment, and error monitoring for reliable integrations. ## Significant Changes and Updates * The Now LLM Service is deprecated as the default model for AI assets; a third-party LLM is now the default, though manual selection of Now LLM remains available. * The Health Dashboard is relocated to the Service Exchange Center for improved centralized system health visibility and faster troubleshooting. * The Coral theme became the default user interface theme starting with Zurich, enhancing user experience with brand-neutral illustrations and dark mode options. * Service Exchange was renamed from Service Bridge starting with Australia Early Availability releases. ## Activation and Additional Information * Service Exchange is available for installation via the ServiceNow Store. Customers should request it there and consult the version history for cumulative release notes. * No new browser, accessibility, localization, or additional requirements were introduced in the Australia release. ## Practical Guidance for ServiceNow Customers To ensure a successful upgrade and optimal use of Service Exchange, customers should: * Delay upgrading to Australia until Australia Patch 1 is available if using Service Exchange. * Follow migration guides specific to their current Service Exchange version to preserve configurations and entitlements. * Upgrade provider and consumer applications together to maintain compatibility and avoid integration issues. * Leverage new features such as centralized connection management, enhanced onboarding, improved data synchronization, and AI-powered assistance to reduce operational effort and improve integration reliability. * Use the Service Exchange Center for monitoring health, connection status, and performing troubleshooting efficiently. Consolidated page of all release notes for Service Exchange (formerly Service Bridge) from Yokohama to Australia. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Service Exchange (formerly Service Bridge) release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama 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 Service Exchange (formerly Service Bridge) to Australia Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-serviceexchangeformerlyservicebridge-summary__entry__2} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | Upgrade information : Important: Do not upgrade your ServiceNow® instance to the Australia release if you rely on Service Exchange. A known RPS issue prevents Service Exchange from functioning correctly. Proceed with the upgrade only after Australia Patch 1 becomes available. * 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 Australia release, consult the [Service Exchange for Providers (Legacy) - Migration Utility \[KB1499823\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1499823) article in the Now Support Knowledge Base to find out how to migrate your configuration data. * Service Exchange version 1.x.x: When upgrading, consult the [Upgrade Guide - Service Exchange for Providers and Consumers application (v2.x.x release) \[KB1700387\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1700387) article in the Now Support Knowledge Base to find out how to migrate your Service Exchange applications. * Service Exchange version 2.x.x: New entitlements that require the latest compatibility version cannot be activated until both consumers and providers upgrade to Service Exchange version 2.x.x. New entitlements configured with a lower compatibility version can be activated. Older active entitlements continue to work but new ones can't be activated. * 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. If the versions diverge, a scan check will report version mismatches and the Health Dashboard will show a version mismatch issue. After upgrading, run and validate the post‑upgrade scan suite to identify and resolve any post‑upgrade issues. * If you have upgraded to Service Exchange version 2.0.55 before upgrading the platform to the Australia release and your instance has Sales Customer Relationship Management version 1.0.4 installed, the new Deny ACLs aren't installed. After upgrading to the Australia release, select Repair to reinstall the Service Exchange application to ensure Deny ACLs are installed. * If you're upgrading Service Exchange to version 2.3.x, migrate the OAuth grant type on all existing connections from authorization code to client credentials to avoid a "User Not Authenticated" error. Complete this migration on both the provider and consumer instances after the upgrade and before using the connection. For details, see [KB2944968](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2944968). * When you install the Service Exchange application, the Service Exchange Global script include is automatically installed or updated on the following platform versions: * Yokohama * Zurich * Australia | [ ] ## New features Between your current release family and Australia, new features were introduced for Service Exchange (formerly Service Bridge). {#dfrn3-serviceexchangeformerlyservicebridge-summary__entry__10} | Release | Release notes | |-|-| | Yokohama | [Remote Catalog Item Client Scripts](https://www.servicenow.com/docs/access?context=service-bridge-v2-add-scripts-to-rrp&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=service-bridge-v2-copy-catalog-as-rrp&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=now-assist-tmt-exploring&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=service-bridge-v2-consumer-variables&family=yokohama&ft:locale=en-US) : Consumers: Manage requested content and flow better by adding additional variables to add customization to your remote record producers. | | Zurich | [Foundation data sync](https://www.servicenow.com/docs/access?context=service-bridge-v2-explore-foundation-data-sync&family=zurich&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=service-bridge-v2-expolre-journal-field-framework&family=zurich&ft:locale=en-US) : * 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](https://www.servicenow.com/docs/access?context=service-bridge-v2-flow-action&family=zurich&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=service-bridge-v2-explore-magic-link&family=zurich&ft:locale=en-US) : 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. | | Australia | [Connections tab in the Service Exchange Center](https://www.servicenow.com/docs/access?context=se-connections-tab&family=australia&ft:locale=en-US) : Create, view, request, and offboard provider and consumer connections from a single location in the Service Exchange Center. Search and filter connections without navigating across multiple screens. [Improved consumer registration and onboarding](https://www.servicenow.com/docs/access?context=se-provider-center-onboarding&family=australia&ft:locale=en-US) : Onboard consumers faster with a guided, step-by-step registration experience. Consumers are automatically redirected to the new registration experience when upgrading to receive clearer progress indicators during onboarding, and receive actionable messaging for failure and delay scenarios, minimizing onboarding friction and support dependency. [Improved FDS capabilities](https://www.servicenow.com/docs/access?context=service-bridge-v2-explore-foundation-data-sync&family=australia&ft:locale=en-US) : Improve your connection experience, by synchronizing Knowledge Base articles between provider and consumer instances. Reduce data inconsistencies by maintaining CMDB `sys_ids` when inserting net-new CIs through transform maps. Preserve CI functionality on the destination instance by automatically creating CI dependency relationships or managing them manually when the source sends relationship data. Get more referenced field data by including dot-walked fields in your outbound field configuration. [Journal Field Framework enhancements](https://www.servicenow.com/docs/access?context=service-bridge-v2-expolre-journal-field-framework&family=australia&ft:locale=en-US) : Increase flexibility in journal data synchronization between provider and consumer instances by mapping multiple source fields to a single target journal field. Preserved all journal entries during synchronization by supporting journal field type `journal_input`, in addition to the existing journal field type. [Simplified persona management](https://www.servicenow.com/docs/access?context=service-bridge-v2-customer-roles&family=australia&ft:locale=en-US) : Assign Service Exchange Remote Catalog personas to user groups or roles so that persona access is granted automatically based on group membership, reducing manual administration. [ServiceNow product tiers](https://www.servicenow.com/docs/access?context=ai-native-sku-overview&family=australia&ft:locale=en-US) : The ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available: * Foundation: AI basics to deliver insights * Advanced: AI to boost productivity across relevant use cases * Prime: Act autonomously with all AI assets, and create your own Depending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents. [Service Exchange Knowledge Assistant](https://www.servicenow.com/docs/access?context=now-assist-tmt-service-exchange-assistant-se&family=australia&ft:locale=en-US) : Get answers to your Service Exchange questions directly in Now Assist, without leaving your current work. The Service Exchange Knowledge Assistant agentic workflow generates answers grounded in documentation that matches the Service Exchange version installed on your instance, and includes links to the source documentation used for every answer. [Consumer outbound FDS](https://www.servicenow.com/docs/access?context=service-bridge-v2-explore-foundation-data-sync&family=australia&ft:locale=en-US) : Reduce manual effort and eliminate the need to share data externally by sharing selected foundational data types with your provider on a scheduled cadence. This data transfer supports the service life cycle by providing foundational data context for operational workflows. [Service Exchange center](https://www.servicenow.com/docs/access?context=se-se-center&family=australia&ft:locale=en-US) : Detect problems early, understand connection status, and resolve issues efficiently with the Service Exchange center, a centralized interface that provides real-time visibility into scan check issues, connection health and statuses, and access to all Service Exchange scan suites. Service Exchange admins can access their respective centers through the Provider and Consumer center links in the navigation menu. [Auto-onboarding](https://www.servicenow.com/docs/access?context=service-bridge-v2-register&family=australia&ft:locale=en-US) : Reduce onboarding complexity for consumers with automated onboarding. This feature autonomously manages onboarding workflows, establishes secure connections, synchronizes settings, and continuously monitors for errors to ensure reliable, efficient integrations with minimal manual effort. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing Service Exchange (formerly Service Bridge) features. {#dfrn3-serviceexchangeformerlyservicebridge-summary__entry__18} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | Coral theme : Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. | | Australia | [Now LLM service deprecation](https://www.servicenow.com/docs/access?context=exploring-large-language-models&family=australia&ft:locale=en-US) : The Now LLM Service is no longer the default model provider for new or inactive AI assets. A third-party LLM is now selected by default, while existing configurations using the Now LLM Service continue unchanged. The Now LLM Service is still available for manual selection. [Health dashboard](https://www.servicenow.com/docs/access?context=se-se-center&family=australia&ft:locale=en-US) : The Health dashboard has been relocated to the Service Exchange Center. Access a more holistic view of system health that includes a resolution center, connection health, and built-in scan suites providing centralized visibility and faster troubleshooting of integration issues. | [ ] ## Removed Between your current release family and Australia, some Service Exchange (formerly Service Bridge) features or functionality were removed. {#dfrn3-serviceexchangeformerlyservicebridge-summary__entry__26} | 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 Service Exchange (formerly Service Bridge) features or functionality were deprecated. {#dfrn3-serviceexchangeformerlyservicebridge-summary__entry__34} | Release | Release notes | |-|-| | 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 Service Exchange (formerly Service Bridge). {#dfrn3-serviceexchangeformerlyservicebridge-summary__entry__42} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | Activation information : Install Service Exchange by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) 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](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=australia&ft:locale=en-US). Important: Service Exchange is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Service Exchange (formerly Service Bridge) we have noted them here. {#dfrn3-serviceexchangeformerlyservicebridge-summary__entry__50} | 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 Service Exchange (formerly Service Bridge) we have noted them here. {#dfrn3-serviceexchangeformerlyservicebridge-summary__entry__58} | Release | Release notes | |-|-| | 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 Service Exchange (formerly Service Bridge), such as specific requirements or compliance levels. {#dfrn3-serviceexchangeformerlyservicebridge-summary__entry__66} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Service Exchange (formerly Service Bridge) we have noted them here. {#dfrn3-serviceexchangeformerlyservicebridge-summary__entry__74} | 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 Service Exchange (formerly Service Bridge) we have noted them here. {#dfrn3-serviceexchangeformerlyservicebridge-summary__entry__82} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | [Australia Patch 4](https://www.servicenow.com/docs/access?context=australia-patch-4&family=australia&ft:locale=en-US) * Get version-specific answers to your Service Exchange related questions with the Service Exchange Knowledge Assistant agentic workflow in Now Assist. [Australia Patch 3](https://www.servicenow.com/docs/access?context=australia-patch-3&family=australia&ft:locale=en-US) * Manage and monitor all your provider and consumer connections from a single, unified Connections tab in the Service Exchange Center. * Streamline the end-to-end registration and onboarding experience for consumers with an improved, guided onboarding workflow. * Simplify persona management with group-based assignments and persona inheritance to reduce administrative effort and align with enterprise identity and access management (IAM) standards. * Improve data synchronization across instances by synchronizing knowledge base articles, preserving CMDB sys_ids, and replicating CI dependency relationships with expanded foundation data sync (FDS) capabilities. * Map multiple journal fields to the same target field and sync journal type fields alongside journal_input fields using the Journal Field Framework. Australia Early Availability * Service Bridge has been renamed Service Exchange. * Streamline data replication from consumer to provider instances with consumer outbound foundation data sync. * Get enhanced visibility into your instances with the Service Exchange center. * Reduce onboarding complexity for consumers with auto-onboarding. See [Service Exchange](https://www.servicenow.com/docs/access?context=tmt-service-bridge-both-landing-page&family=australia&ft:locale=en-US) for more information. | [ ]