1.2.5 Enhancements in Teller
The following are the updates as a part of Teller in this release:
- Merger of Micro Services: Following micro services are merged and bundled as 2 micro services application. This would reduce interservice calls during Teller transaction processing.
Old Micro Services
- obremo-srv-adp-adapter-services
- obremo-srv-bcn-branchcommon-services
- obremo-srv-cas-cash-services
- obremo-srv-cmn-ml-processing
- obremo-srv-cmn-transaction-services
- obremo-srv-cmn-utils-services
- obremo-srv-cus-customer-services
- obremo-srv-pay-payment-services
- obremo-srv-prj-projection-services
- obremo-srv-tds-term-deposit-services
New Micro Services- obremo-srv-branch-teller-services
- obremo-srv-brntlr-async-services
- Enhancement in Transaction Screens: Enhancement is done to display the transaction reference number in the transaction screens.
- Invoke EOD: When the teller invokes EOD, an alert message will be displayed for acceptance to proceed with the EOD. The pop-up screen displays an alert message as Invoke EOD will be run for Branch Code (Branch Description) <> for Date <>, Next Working Date will be <>. Do You want to continue?.
- Charge Modification and Waiver:
- Charge Modification: The charge amount can be modified if enabled in Function Code Preferences screen. User modified charge amount will be validated against the minimum and maximum charge amount configured at the Charge Maintenance screen. When an individual charge amount is modified, then the system will recalculate all the dependent charges as per the charge maintenance set-up.
- Waiver: When the charge waiver is enabled, the value under the charge amount will be waived and no charge accounting entries will be passed. However, the charge amount will remain as is and not be defaulted to zero. Charge waiver can be enabled at individual charge levels without impacting other linked charges. The minimum charge amount configured at the charge maintenance level, will not be validated when the charge is waived.
- Two-Step Completion of Transactions: Earlier, when the maker makes the transaction and the checker approves it, the transaction goes to the maker to submit again to complete the transaction. Enhancement is done for teller transactions to get completed once the checker approves the transaction. The earlier flow of transactions was maker-checker-maker. The revised transaction flow is maker-checker.
To enable two-step authorization process, maintain the value as Y in the FINISHTXN_ON_APP parameter in the SRV_TM_BC_PARAM_DTLS table.
- Support for Reversal in Remittance Issue: Cash Remittance Issue Transactions can be reversed from Electronic Journal or Servicing Journal by enabling Reversal Allowed in Function Code Definition.
- Multi BC: Enhancement is done in the Multi BC Issuance screen to issue multiple bankers cheque against multiple beneficiaries for a single remitter account or against Cash GL for Walk-in customers.
- Denomination Defaulting based on Configuration: The denomination details will be auto populated by default in the withdrawal transaction screens. If the user maintains a value as 'N' in the DEF_DEN_FR_WTDWL parameter in the SRV_TM_BC_PARAM_DTLS table, the auto population of denomination details will be disabled. With this maintenance, the Teller can update the denomination based on the customer's request.
- Instrument Status Update Screen: This screen is used to change the status of instrument numbers from ‘Used’ to ‘Unused’. Using this screen, the instruments can be reused.
- Coherence Adoption: Implemented remote caching solution for static/dynamic data using Oracle Coherence.
Parent topic: Release Enhancements