0
2.4.10
Australia Patch 1, Australia, Zurich, Yokohama
Standalone Application
Foundation Data Sync for Consumers enables customers to request and receive foundational data from their providers without costly third-party integration. This version enables the structured, periodic sharing of data from consumer to provider instances. It ensures that providers have access to accurate, up-to-date foundational data from consumers, supporting better service delivery and operational alignment.
- Quickly request data from your connected providers: Consumers can receive and request pre-defined foundational data offerings from their providers with a built-in request mechanism.
- Ensure the data meets your Identification and Reconciliation Engine rules before accepting: Once requested, providers can send you a test sampling that can be tested against the IRE rules for your instance. If the data meets your standards you can then accept the subscription and start receiving the initial seed of data along with updates.
Foundation Data Sync for Consumers — v2.4.10
No functional changes.
Service Exchange for Consumers — v2.4.10
Fixed
- Attachments could queue unnecessary background jobs regardless of connection state. (PRB2070888)
- A remote task wasn't created when its trigger condition referenced a child-table-only field. (PRB2070471)
Foundation Data Sync — v2.4.10
Fixed
- Multi-value list fields could truncate when a later batch sent more data than the first. (PRB2068326)
- Requesting an offering referencing a table missing on the requester blocked further requests. (PRB2063217)
- Initial payload sync could duplicate or skip records if source data changed mid-sync. (PRB2061531)
- Batches after the first could stop processing during bulk sync. (PRB2068330)
- Knowledge article attachment sync now correctly handles tables that extend a base table.
Changed
- Synced KB articles now default to including the provider name in the target KB name.
Service Exchange Base — v2.4.10
Fixed
- Near-simultaneous updates on provider and consumer could drop one side's change. (PRB2029744)
- output.ignore=true on a transform didn't actually exclude the field from the sync payload. (PRB2066768)
- The Case table lacked a proper label/plural, showing an auto-generated name to some users. (PRB1923483)
- A multi-row variable set on a record producer overwrote all rows with the last row's value. (PRB2061638)
Changed
- Restart Connection after a clone/upgrade now also reactivates capture definitions automatically.
New
- Added a scheduled sweep to reactivate capture definitions left inactive after a clone/upgrade.
Service Exchange Remote Process Sync Transport — v2.4.10
Fixed
- Onboarding could time out on slow connections, leaving OAuth credentials empty. (PRB2064896)
- OAuth credentials during onboarding were sent via URL query params instead of the request body. (PRB2060125)
Transporter — v2.4.10
No functional changes.
Service Exchange Health — v2.4.10
Fixed
- Integration-user-naming scan check didn't validate the required prefix. (PRB2023585)
- Some pre-onboarding scan failures didn't generate an Issue record, hiding the block reason. (PRB2025384)
- Tightened ACLs on Health records; removed a console log exposing connection data. (PRB2071380)
- Fixed message alignment and a duplicate message on the admin-group scan check. (PRB2067053)
- Connection Dashboard now shows accurate inbound/outbound transport queue backlog counts.
Changed
- Consolidated two magic-link scan checks into one, gated on whether magic links are enabled.
New
- Added a clearer down-connection warning about data loss after 7+ days.
- Added a notification to admins when the Admin group has no users.
- Added warning messages for missing roles (itil, cmdb_read, personalize, import_admin).
Not applicable for this application version.
- Required plugins and products
- Foundation Data Sync (com.sn_fds)
- Foundation Data Sync for Consumers (com.sn_fds_con)
- Dependencies:
- Service Exchange Base (com.sn_sb)
- Service Exchange for Consumers (com.sn_sb_con)
- 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