1.2.2 Non-Functional Features

This topic provides the information about the various non-functional features changes in this release.

Common Entities Length Changes

As part of standardization Common Entities length has been increased, details of which are as follows.

Table 1-1 Common Entities length

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)

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

Kafka Resilience Configuration

As part of Kafka resilience and fault tolerance setup for an On-prem environment, configuration had been done to establish a new Kafka cluster with three brokers using latest kafka version. Resilience properties were configured at both the Kafka brokers and the producer/consumer services to automatically recreate Kafka topics with appropriate resilience settings, such as a replication factor of 3 and a minimum of 2 in-sync replicas.

Redwood Theme Adaption

The Oracle Redwood user experience has been implemented across all the screens in the Oracle Banking Virtual Account Management appshell to provide a consistent and effective user experience to drive efficiency. This implementation does not affect any functionality. A few more details are listed below as Redwood comes into play: 1. Oracle JET class has been deprecated. 2. Inline styling in HTML has been deprecated. 3. CSS utility classes are being used on the component level instead of Custom classes for font size, font-color, padding, margin, bg-color, heading, etc. 4. Images are no longer used for icons. 5. Libraries like lux, moment js, math js, jszip, and timsort are deprecated. Chapter 1 Release Enhancements

Coherence Cache

Oracle Banking Virtual Account Management now supports Coherence. Coherence stores frequently accessed data as serialized key-value pairs for a fast read, write, and query operations to achieve maximum application performance and stability. 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. Refer Oracle Banking Microservices Architecture Installation Guide for the detailed explanation on Coherence implementation with plato-coherence-server.