Technical Enhancements of Retail Accounts and Retail Deposits

This topic provides the technical enhancements of retail accounts and retail deposits.

  • Additional information in Audit Log details : The Audit Log Details section has been improved to offer a clearer overview of changes. This improvement features:
    • Field Value Tracking – Displays both old and new values of modified fields.
    • Maker and Checker Information – Retains details of the users who initiated and approved the changes.

    This enhancement ensures greater transparency and traceability in audit logs.

  • Compliance with Personally Identifiable Information (PII) for RESTful APIs has been updated. The GET method in current APIs, which previously included the Customer Number or Account Number in the URLs, has now been changed to POST. Now, these identifiers are included in the request body instead of being passed in the URL. This adjustment improves:
    • Security – Reduces exposure of sensitive data in URLs.
    • Compliance – Aligns with best practices for handling customer/account information in cloud.
  • Auto Transport Cloud Configurations

    In order to ensure seamless movement of configuration data across cloud environments (e.g., from pre-production to testing or production) a new user interface (UI) and processes have been introduced to define source and target environments. Extra options are available for importing and exporting customizable data for different maintenance activities.

    This improvement allows banks to transfer configurations reliably and uniformly, reducing mistakes and speeding up the deployment process.

    Note:

    For UI details, steps and guidelines, refer to the Common Core User Guide
  • API Enhancements to support Data Segment level modifications.

    The current RESTful APIs have been improved to enable detailed data changes, allowing applications that call the API to access or modify individual fields rather than whole records. This improvement simplifies the process of returning large data sets. It also lessens the data burden on the calling application since it is not required to send the entire data segment.

  • List of new End of Day (Batches) added/modified in the EOD workflow:
    New batches added are:
    • AbortExistingWithdrBalanceUpdateBatchJob
    • CheckWithdrBalanceUpdateJobStatusCompleted
    • WithdrBalanceUpdateBatchJob
    • AbortExistingWithdrBalanceUpdateBatchJobPostIC
    • CheckWithdrBalanceUpdateJobStatusCompletedPostIC
    • WithdrBalanceUpdateBatchJobPostIC
    • AbortExistingWithdrBalanceUpdateBatchJobPostRevaluation
    • CheckWithdrBalanceUpdateJobStatusCompletedPostRevaluation
    • WithdrBalanceUpdateBatchJobPostRevaluation
    Batches removed from the EOD workflow:
    • EOFI.PreGlHandoff

    Note:

    Refer EOD Configurations User Guide for details on the above batches.