2 Technical Changes

This topic provides the information on the Technical Changes.

Table 2-1 Technical Changes

Summary	Description
OBRH Template Incremental release	The Oracle Banking Branch now includes an enhancement that streamlines the upload and maintenance of Oracle Banking Routing Hub (OBRH) configuration templates in cloud environments. The obrh-config-feeder-service utility enables direct upload of Provider-level and Service-level JSON templates, simplifying integration configuration management. The enhancement supports granular uploads, allowing provider and service configurations to be updated independently while enforcing data integrity through restrictions on consumer-level modifications.
Migration of Teller Screens using UI Toolkit.	Teller transaction screens have been migrated to UI Toolkit–compliant Oracle JET (OJET) components using common core and native toolkit libraries. The upgraded implementation supports component extensibility and standardized UI behavior across the application, delivering improved user experience consistency, enhanced maintainability, and a scalable foundation for future functional enhancements.
SonarQube corrections	Technical: As part of this release, all high-priority quality issues and blocker vulnerabilities identified through SonarQube analysis were reviewed and resolved across the module. The remediation effort included code cleanup, refactoring, removal of unused code, improved error and null handling, and adoption of coding best practices. With all critical and blocker findings successfully addressed, the application now delivers improved stability, maintainability, and overall code quality, providing a stronger foundation for future enhancements.
Display Artifact Version, Environment Name in Logs	Logs will now clearly show which environment the application is running in along with the version of the build deployed. This makes it easier to identify releases, track changes, and avoid mix-ups between environments.
Display Product version, Environment Name on UI	On the UI, users will now be able to see the environment they are currently working in along with the product version. This helps reduce confusion and provides clear visibility of the running release.
Blue Green Deployment Strategy for Plato	With a Blue-Green deployment strategy, hotfixes, patches, and upgrades occur with near-zero downtime. Applications are now backward compatible with both database and application changes, enabling seamless, disruption-free releases.