Foundation Data Sync (FDS) enables the structured, periodic sharing of data from provider to consumer instances. It ensures that consumers have access to accurate, up-to-date foundational data from providers, supporting better service delivery and operational alignment.
FDS is a data synchronization mechanism that enables a provider instance to share foundational data with consumer instances on a scheduled basis, such as daily, weekly, or monthly.
FDS supports all CMDB tables and the following non-CMDB tables: Asset, Company, User, Group, Location, Department, Stockroom, Product Model, Knowledge, Hardware Model, Consumable Model, Hardware, and Consumable.
- Create and Publish an Offering: Define the data that you, as a provider want to share with the Service Exchange consumer.
- Receive and manage a Offering Request: Customers with Foundation Data Sync for Consumers can request that offering from their ServiceNow instance.
- Refine, Validate, and Send the data with Subscription Items: Once requested, Foundation Data Sync will pre-generate the subscription items defined in the offering, which can then be filtered further by the provider if desired. When ready, a provider can then test and validate the data sharing before sending in full.
Foundation Data Sync v2.4.17
Changed
- Improved the attachment sync strategy between provider and consumer.
Service Exchange Remote Process Sync Transport v2.4.17
Fixed
- Tightened OAuth client-credential token scope, limiting what a token can access. (PRB2067950)
- Removed the snc_internal role requirement from the REST API that failed if the role was missing (PRB2076065)
Service Exchange Health v2.4.17
New
- When a connection goes down, some known issues are now auto-diagnosed and fixed, with the outcome logged on the resulting health issue.
- Connection health now tracks slow/down occurrences, resetting monthly.
- Overridden consumer updates now generate a visible error record instead of failing silently.
- Existing error code 999 unknown health issues converted to known issue types
Changed
- Stale slow/down status indicators now clear automatically once a connection recovers.
Fixed
- Fixed translation issues in scan-suite filtering, offboarding, and a connection status label. (PRB2038126)
Service Exchange for Consumers v2.4.17
New
- Error code 999 health issues now include more context on what's affected.
Fixed
- Fixed a localization issue found during a routine scan. (PRB2083235)
- Fixed embedded images appearing broken, or as raw HTML, when synced to the provider. (PRB2076772)
Service Exchange for Providers v2.4.17
New
- Existing error code 999 unknown health issues converted to known issue types
Fixed
- Fixed catalog item variable-set order not carrying over when published as a Remote Record Producer. (PRB2074741)
Service Exchange Base v2.4.17
New
- Admins can upgrade a connection from legacy OAuth to Client Credentials directly from the connection record.
- Sync job frequency is now configurable via a system property instead of fixed.
Fixed
- Tightened OAuth client-credential token scope, limiting what a token can access. (PRB2067950)
- Fixed an issue blocking simultaneous inbound and outbound transforms on the same field. (PRB2075724)
- Fixed a Remote Record Producer publish issue where a dependent variable kept pointing to the prior version. (PRB2074843)
- Fixed a missing translation label on the Case table. (PRB2083234)
- The Service Exchange Admins group is no longer selectable as a task/problem assignment group. (PRB2079342)
v2.4.17
Foundation Data Sync for Consumers
Foundation Data Sync for Providers
Service Exchange Order Management for Providers
Transporter
These releases update the application to version 2.4.17 with no functional changes outside of the mentions above.
Not applicable for this application version.
- Required plugins and products
- Foundation Data Sync (com.sn_fds)
- Foundation Data Sync for Providers (com.sn_fds_pro)
- Dependencies:
- Service Exchange Base (com.sn_sb)
- Service Exchange for Providers (com.sn_sb_pro)
- Properties that need to be created or set to activate the content pack: N/A
- Affected business rules: N/A
- Affected script includes: N/A
- .jar files that need to get uploaded, if applicable: N/A