2 Technical Changes

This topic provides the information on the Technical Changes.

Table 2-1 Technical Changes

Summary	Description
OBRH Template Incremental release	A new enhancement in the Oracle Banking Branch streamlines the upload of Oracle Banking Routing Hub (OBRH) configuration templates in cloud environments. The obrh-config-feeder-service utility now enables users to upload Provider-level and Service-level JSON templates directly, improving the process for maintaining integration configurations. With this enhancement, the utility supports granular uploads—allowing you to update provider and service configurations independently, while enforcing robust data integrity by restricting consumer-level changes.
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 screens support component extensions and standardized UI behavior across the application. This ensures improved consistency, better maintainability, and a scalable UI foundation for future functional enhancements.
SonarQube corrections	Technical: As part of this development cycle, all SonarQube critical issues and blocker vulnerabilities identified across the module were analyzed and resolved. This includes code refactoring, dead code removal, improved null handling, optimized logic, and updated best-practice implementations. The codebase now meets the targeted quality gate standards with zero critical and zero blocker findings, resulting in enhanced maintainability, readability, and overall application reliability.non-technical: In this release, we completed a full cleanup of all high-priority quality issues reported in SonarQube. All critical and blocker items have been successfully resolved, improving overall code health and stability. The application is now cleaner, more reliable, and better prepared 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.