Brazil, Australia Patch 1, Australia, Zurich Patch 6, Zurich, Yokohama Patch 12, Yokohama
Standalone Application
The Service Exchange (SE) application enables customers to connect with their providers through their ServiceNow instance. Service Exchange provides seamless connections across the provider’s ecosystem to enable flow-through service and support requests, without having to set up costly custom integrations.
Customers can request services and support, track progress, and receive service updates and notifications from their providers in their own ServiceNow instance without having to swivel-chair to an external system.
Fixed
Foundation Data Sync v2.4.19
- Corrected processing for non-CMDB tables with a cmdb_ prefix, such as Model [cmdb_model], so records are synced and failures show as errors instead of Processed.
Foundation Data Sync for Consumers v2.4.19
- Corrected Force Refresh so entitlements on the provider are not stuck in Pending, and the consumer’s Active or Inactive status syncs back.
Service Exchange Base v2.4.19
- Corrected installation and upgrade so application files are no longer skipped with the Skipped Manual Merge status.
- Corrected comment routing on domain-separated instances so provider comments reach the consumer’s parent task when its company is in a different domain from the connection.
- Added the required OAuth authorization scope so connections stay intact through provider plugin upgrades. (PRB2104038)
- Removed stale connection aliases so connections no longer break on both instances after an instance clone.
- Aligned the consumer’s parent task with the provider’s remote task. Once a connection reaches Connected, the parent task takes the provider’s state.
Service Exchange for Consumers v2.4.19
- Corrected connection handling during provider plugin upgrades so outbound messages no longer fail with the “No active remote system found” error. (PRB2104038)
- Corrected Remote Catalog item submission failures on consumer instances for provider categories due to a missing tablename field. Existing records are also fixed on upgrade. (PRB2101059)
- Corrected remote task error handling so a remote task moves to Error after an earlier failure. This happens when the provider’s incident references an assignment group missing on the consumer and a consumer business rule blocks the parent task. (PRB2093208)
- Fixed Force Refresh so entitlements stuck in Pending on the provider are cleared, and the consumer’s Active or Inactive status is sent back.
Service Exchange for Providers v2.4.19
- Restored Resolution Notes on Service Exchange cases moved directly from New to Closed or Canceled. (PRB2086527)
- Aligned the consumer’s parent task with the provider’s remote task. Once a connection reaches Connected, the parent task takes the provider’s state.
- Added the required OAuth authorization scope so connections stay intact through provider plugin upgrades. (PRB2104038)
- Onboarding a consumer on a provider with a lower Service Exchange version would proceed to completion without the “User Not Authorized” error.
Service Exchange Health v2.4.19
- Fixed the "Select a provider to get started" dropdown on the consumer "Create your connection" screen not listing the provider you were trying to connect to. The dropdown now searches all companies. (PRB2097897)
Service Exchange Remote Process Sync Transport
- Stale connection aliases would now be removed on upgrade so connections no longer break on both instances after an instance clone.
- Corrected credential generation so scope mappings are created before access is restricted, and connections are no longer left restricted with no scope. (PRB2104038)
v2.4.19
Foundation Data Sync for Providers
Service Exchange Order Management for Providers
Transporter
These releases update the application to version 2.4.19 with no functional changes outside of the mentions above.
Not applicable for this application version. For more information, please see
Application Runtime Policy
- N/A - All requirements are automatically installed.