1.2.3 Technical Changes

This topic provides the information about the technical changes added in this release.

• Liquibase Migration:

  Adoption of SQLcL instead of flyway.

• Cyclic Sequence Changes:

  To overcome and manage sequence getting exhausted, Cyclic sequences were adopted.Plato Batch Adoption - Enable dynamic parameters to be included in the request body for the /runBatch endpoint, based on a flag set in the batch server. This ensures required parameters are fetched from the Domain service, updated in the existing parameters, and formatted as needed.

• Plato Batch GCS Adoption:

  Tables excluded from Plato Batch Schema for maker and checker flow are now aligned for as per GCS framework.

• Breaking Change in OBRH:

  New Placeholder created for Oracle Banking Cash Management where it will consume appid from OBRH and will apply common to domain services.

• API Versioning
  All the web and service URLs used across Oracle Banking Cash Management application have been versioned for current release.

  Note:

  For more details on endpoints, utilize the API hub and refer to the API Hub documentation.
• Application version Display
• • The user logs will display the current artifact version and environment name configured.
  • The application user interface will display product release version in the About Section and environment name configured on the app-shell header after Login.
• Event Hub Enhancement
  • Sequential message processing - For failed messages
  • Retry mechanism for Kafka Messages in case of fire and forget scenarios - For cloud environment
  • EventHub Message Retry scheduler : managing schedulers in distributed systems using ShedLock library
• Blue-Green deployment- software deployment strategy has been adopted to reduce risk and minimize downtime – nearly zero downtime