1.2.2 Non-Functional Changes
This topic describes about the Non-Functional Changes.
Common Entities Length Changes
- As part of standardization Common Entities length has been increased, details of which are as follows.
| S No | Entity | Old Length | New Length |
|---|---|---|---|
| 1 | Branch Code | VARCHAR2(3) | VARCHAR2(6) |
| 2 | User ID | VARCHAR2(12) | VARCHAR2(320) |
| 3 | Customer Name | VARCHAR2(35) | VARCHAR2(140) |
| 4 | Account Number | VARCHAR2(20) | VARCHAR2(34) |
| 5 | Account Description | VARCHAR2(105) | VARCHAR2(140) |
Dashboard Changes
- Currency Selection dropdown is introduced for Top Cross Border Sweeps and Top 5 Customer Balance by Currency
- The widget name Currency wise Liability is renamed to Currency wise Balance.
- The Dashboard widgets data will now be updated through kafka events.
Coherence Adoption
- Oracle Banking Liquidity Management now supports Coherence. Coherence stores frequently accessed data as serialized key-value pairs for fast read, write, and query operations to achieve maximum application performance and stability.
- Oracle Banking Liquidity Management implemented remote caching solution for static/dynamic data using Oracle Coherence.
- The use cases for coherence in domain services include replacing REST API calls to common core services with coherence wrapper methods, replacing Spring caches and new methods to cache processed data.
- For more information on the coherence adoption, refer to Oracle Banking Microservices Platform Foundation Installation Guide.
Audit Changes
- Audit Date/DateTime will be stored in UTC. Along with the UTC timestamp, the branch context of the user making the changes will also be displayed.
Archival and Purging
Archival and purging adopted in Oracle Banking Liquidity Management. For more information on archival and purging adoption, refer to Oracle Banking Microservices Platform Foundation User Guide.
Parent topic: Release Enhancements