Skip to main content
This page lists the changes since 5.3.0-M1 and 5.3.0-beta, and explains any changes required to migrate from these early releases to the stated version of :

Changes since 5.3.0-beta

Summary

  • IRT Desk improvements: IRT Desk membership is now specified directly at the book level. Additionally, it is possible to dynamically change which books are members of the IRT Desk.
  • Reinstating the Categories hierarchy: The Categories hierarchy that was removed in 5.1.0 can be re-instated with the configuration property categories-hierarchy.enabled=true.

Added

Changed

Changed

Removed

Fixed

Fixed issues introduced in 5.3.0-beta

None.

Migrate to 5.3.0

Upgrading from version 5.3.0, see 5.3 Release Notes. uses 6.0.14-sb3 and 5.1.x. For new features and fixes included in these releases, please see the documentation and Migration Notes, and the release notes for . For clients licensed to use ActiveMonitor, a skeleton module based on version 6.0.14-sb3 is included with the 5.3.0 release.

Breaking Changes

  • obligor_category field: input field is no longer being converted to canonical value within DefaultRiskChargeTuplePublisher. This logic has been moved to a column calculator which is enabled by default but will be disabled in future releases. To re-enable, set drc.bucket.cleaning to true.

Summary

See 5.3.0 Migration Notes for details on:
  • Reinstating the Categories hierarchy.
  • IRT Desk improvements.

Input file formats

Added

Deprecated

Configuration files

Files Modified

application.yaml
New properties: Updated properties:
frtb-config.properties
New properties:
frtb-data-load.properties
New properties:

Datastores

Added stores

Cube schema

Added

Changed

Fixed

Fixed issues introduced in 5.3.0-M1

Migrate to 5.3.0-BETA

Upgrading from version 5.3.0-M1, see 5.3-BETA Release Notes. uses 6.0.12-sb3 and 5.1.x. For new features and fixes included in these releases, please see the documentation and Migration Notes, and the release notes for . For clients licensed to use ActiveMonitor, a skeleton module based on version 6.0.12-sb3 is included with the 5.3.0-BETA release.

Breaking Changes

  • IRT_Desk field: Moved from the DeskDescription store to the BookDescription store. This change is also reflected in DirectQuery Tables.
    The BookDescription store was previously named BookDeskMapping. Backwards compatibility with old input files is maintained, though the use of the IRT_Desk field in DeskDescription files has been deprecated.

Summary

See 5.3.0 Migration Notes for details on:
  • EBA Reporting : Additional measures have been included to support new EBA reporting templates.
    • The “Imported” measures used for the old reporting templates have been deprecated.
  • UI Activation : An import of react-query is required when using {serverName}-sdk. See UI activation for more details.
  • DirectQuery IMA Support: Added support for using the IMA-ES cube (InternalModelApproachCube) with DirectQuery.
  • Configuration Property Naming Convention: Configuration properties inside application.yaml have been updated from camelCase to kebab-case. This change is to align with the Spring Boot naming convention. Both naming conventions are interchangeable/compatible with each other.
  • IMA and IMA-DRC query cubes: The IMA and IMA-DRC query cubes have been added to the InternalModelApproachCube and InternalModelApproachDrcCube respectively. These cubes are used to query the IMA and IMA-DRC data across data nodes. A complete list of measures can be found here.

Input file formats

Added

Modified

Deprecated

Configuration files

Files Modified

application.yaml
New properties: Deleted properties:
frtb-config.properties
New properties:
frtb-data-load.properties
Updated properties:

Datastores

Added tables

Deprecated

DirectQuery

Added

Changed

Removed

Databases

Added tables

Deprecated

Cube schema

No changes.

Measures

Added

Moved

The following measures have been moved form the CombinedCube into the respective query cubes. By moving these measures into the query cube, we can now query across dates and data nodes without the measure needing to be defined in the CombinedCube. These measures will still exist in the CombinedCube and on all data-nodes.

Context values

No changes.