1.1 Common Changes

These are the common changes are released as part of OBELCM 14.8.0.0.0 version.

Redwood Changes

Oracle Redwood Design is the Oracle standard for any of its application’s look and feel. Oracle globally has standardized Redwood implementation to ensure consistency across the user interfaces of all Oracle product offerings. Oracle Enterprise Limits and Collaterals Management is adopting Redwood Design as part of this release. Standard JavaScript Components are being replaced with OJET components and the UI layer - UI rendering, databinding & data transformation are performed using OJET Version v13.1.0.

New OBMA Utilization service based on Helidon and Coherence
  • Utilization services for existing Limits (Liability, Facility and Collateral) have been migrated to OBMA based Helidon and Coherence services. These services have been developed using the OBMA framework, which follows modern software engineering best practices to actively enhance the quality and performance of the existing services. Coherence is a scalable, fault-tolerant, cloud-ready, distributed platform designed for building grid-based applications and ensuring reliable data storage.
  • Customers have the option to adopt the new utilization services by enabling the coherence flag in GEDPARAM. However, existing customers who prefer to continue using the old utilization services can do so without making any configuration changes.
  • The product is packaged with Oracle Coherence Enterprise Edition under a Restricted Use License (RUL). Depending on the volumes, customers may need to increase their RAM capacity and utilize Solid State Drives (SSDs) for coherence cluster backups.
Terms and Conditions
  • Terms and conditions functionality for entities like customer, facility and collateral is supported with the following features.
  • T&C Maintenance
    • Common terms and conditions maintenance for all 3 entities.
    • Creation, modification, inquiry, and summary features for maintenance.
  • T&C Linkage
    • Support for linking terms and conditions with entities like customer, facility, and collateral.
    • One or more conditions can be attached to an entity.
    • For facility and collateral, separate sub-system is provided in existing maintenance screen for Terms and conditions.
    • For customer, separate function is provided for linking terms and conditions.
    • Once a condition is updated as part of tracking, tracking related details are updated in linkage level.
  • T&C Tracking
    • Common tracking screen for conditions of all entities.
    • Condition is available for tracking on or after the due date.
    • As part of tracking condition status can be updated like met, breached, waived, or deferred.
    • New due date can be signified for deferred condition in the linkage screen.
    • Deferred condition can be tracked and taken for a logical closure by updating the status like met, breached, or waived.
Drawing Power
  • OBELCM now supports creation of facilities backed by Drawing Power (DP).
    • Provision to capture if the facility is DP backed by signifying DP amount.
    • New effective line amount basis as min (Limit amount, DP Amount) introduced which is applicable for DP backed facilities.
    • Signifying stock statement submission at facility maintenance (for DP backed facilities) by updating last stock statement submission date and DP amount.
    • Provision to specify the number of days for zeroization of drawing power and zeroizing the DP amount if configured number of days crossed since last stock submission date as part of the batch process.
    • System capability to restore drawing power on submission of latest stock statement.
    • Changes to inventory and account receivable collaterals to signify values based on stock statement submission.
    • Linkage of the collaterals to DP backed facility with handling of effective line amount.
Covenant Linkage Modification
  • Covenants functionality is now enhanced to support modification of the existing covenant linkage attributes.
    • The modification is applicable at all covenant linkage levels – Facility, Collateral and Customer.
    • Below set of attributes are now allowed for modification, post linkage and during covenant lifecycle.
      • Frequency - change the frequency during the covenant period.
      • Notice Days - change a covenant's ‘Notice days” during the covenant period.
      • Grace Days - change a covenant's ‘Grace days” during the covenant period.
      • End Date – modify the covenant’s end date.
      • Covenant Target Condition – modify the covenant’s existing target condition value during the covenant period.
      • Covenant Target Value – modify the covenant’s existing target value based on target condition.
    • System considers modification impact on current/next instance considering further tracking.
JEE Dependency Changes
  • JEE Dependency Exclusion (EJB / MDB):
    • ODT products were specifically designed for deployment on JEE Application Servers. Modifications have been made to improve compatibility with non-JEE deployments.
    • The application source code depends on EJB and MDB components, which are exclusively managed by JEE Application Servers. These components are not supported on non-JEE servers using third-party libraries, as JEE Application Servers provide proprietary lifecycle management for EJBs and MDBs.
    • Successfully transitioned from using JEE (EJB/MDB) to the Spring Framework (Spring Core/Context/JMS).
    • The Entity Manager has been updated to utilize an application-managed Entity manager instead of a server-managed Entity manager.
  • Packaging Changes:
    • As part of this transition, the deployment method for ODT products has been updated. WAR files will be generated instead of EAR for packaging purposes.

Integration with Oracle Banking Routing Hub

OBELCM is now integrated with Oracle Banking Routing Hub.Oracle Banking Routing Hub enables seamless and standardized integrations between Oracle Banking Products using configurations provided as part of the product infrastructure. Both service providers and service consumers can be configured that uses API’s for request/response in JSON/XML format.

Parent topic: Release Highlights