ODS - Changes & Fixes

This page covers the changes and fixes provided to ODS in IPF Release 2025.3.0

New

How versioned PDS mappings work

  • Each label mapping to a PDS object takes a list of mappings.

  • Version parameter is optional, if not provided, it defaults to 0.

  • Users are not required to specify mapping for every version; a new mapping only has to be configured if the value of the path changed for the given PDS object type.

  • When the metrics processor processes a PDS object, it will look up the configured mappings and will apply the mapping with the version which either exactly matches with the version of the incoming PDS object, or with the one that closely precedes the version of the object.

Examples based on the above configuration

  • PDS Object with Version 0 → the first mapping under the currency label will be applied for calculation of changes

  • PDS Object with Version 2 → the first mapping in the list of currency will be applied here as well, as version 0 precedes Version 2

  • PDS Object with Version 4 → mapping specified with Version 3 in the currency list will be applied to the incoming object, as Version 3 directly predeces Version 4.

V3 ODS Inquiry API (Beta) specification.

  • Consolidated ODS Inquiry API /views/summaries/ endpoints to be one API call rather than 4 (Payment, Recall, Batch & Bulk), with journeyType now becoming a query parameter rather than a url parameter.

  • The response class for all all/mds-objects and catalogue/mds-objects/ endpoints has changed to MdsObjectSearchItem2, removing the use of distinct response classes.

  • The ODS Inquiry application can handle calls to both the V3, V2 and V1 Inquiry APIs

  • A new set of client connectors can be enabled for the V3 API.

It is important to note that a config change MUST be applied to using the V3 client connectors. Your configuration must be updated to override the client connector version configuration as follows: ods.inquiry.client.version=3

V3 is in beta and could be subject to changes before 2025.4, when it will be finalised.