Infinity Release Notes

Digital Banking Servicing Micro Apps Features

For more information on the apps shipped in this initial release, see Micro Apps documentation.

Micro Apps are applications with specific functionality which are fast and efficient than monolithic applications. While traditional monolithic apps contain a wide range of functionality including front-end and back-end operations, Micro Apps are simple, lightweight in nature with targeted functionality.

Wealth

• Infinity is integrated with Wealth FO for Advisory Portfolio features.
• Technical Switch - A unique bearer token per customer is sent for customers that are being enrolled in Infinity. This would strengthen the security in integration between Infinity and TAP.

Bulk Payments

• Bulk Payments-Strategic Enhancements involved the development on the Gaps identified during Euro Bank SIT testing. Below items are addressed in Bulk Payments journey.
  • Special Characters Validation in Payment Reference field.
  • Sorting for Recipient Name, Amount, Fees Paid By will happen within the sub headers for Same Bank, Domestic and International Beneficiary.
  • In Multiprocessing mode, after the template creation whatever the currency provided by Beneficiary will be displayed during the edit flows.
  • User will be able to see the data points same as that when he clicks on download icon in the Payment status tab, Payment History tab, Approval (Pending & History Dashboard), Request (Pending & History Dashboard).
  • Introduced View Details Button, even when the user payment is in “Uploaded” for the purpose of refresh.
  • Suppressed the Upload ID value in Bulk Reference ID when the record status is Uploaded, Extracting Payments or Extraction Failed.
  • Removal of currency symbol in Payment status, Payment History, Approval & Request Dashboards. Total Amount field is renamed to Batch Amount.

Trade Finance Micro App

Receivable Financing – Single Application

• The Receivable Financing Single Application is now available for corporate user.
• The Corporate user can create Single Application with appropriate need.
• New Dashboards for the Single Application with receivable type (bill and batch) and Amount Graphs along with Statuses count in Display.
• Added Search, Sort, Filter functions for Single application in the Overview Screen.
• The Corporate User can initiate Single Application both manually and by CSV upload with all required field data along with Upload Document facility.
• The Corporate User Can Print / Download the individual or list of bills
• The Corporate User can raise a query and receive notification and alerts for receivable financing single application.

Spotlight Features

Spotlight application is used to set up and maintain customer and employee-related information and to configure the behavior of digital banking applications associated with this information. See Spotlight documentation for more information.

• Multi-Entity
  • Alerts Configuration in Spotlight - The capability to define alert groups under a selected category which will be multi-entity enabled and add corresponding alerts for the associated alert Group.
  • Migration Utility for Alerts - Convert the non-multi-entity data to multi-entity in DBXDB/Microservices.
  • Introduction of New Actions - New Action: Add user to another entity.
  • Multi-entity enabled Alerts Framework.
• Online Banking application (OLB/MB)  
  • Alerts Settings - Ability to edit, enable/disable a particular alert in a specific legal entity.

Infinity Installer Features

• Added support to pick passwords from azure key vaults instead of reading plain text from property file.
• Added new microapps support in Digital banking and Origination (Both Fabric and client Apps).
  • TradeSupplyFinance – Fabric and TradeSupplyFinMA – Client (Digital banking)
  • ResourcesHID (Both Digital banking and Origination).
• Automated the process of multi entity setup (MYSQL and MSSQL).
• Added support for dynamic key cloak realm login authorization.
• Added support to do SCA build for Retail Banking (Both Fabric and Client).
• Automated the process of executing ORDMS postman collections for multi entity.
• Upgraded MFCLI Jar to 9.7.1.0.

Microservices Enhancements

Microservices is an architectural style that structures an application as a collection of small autonomous services, modeled around a business domain. Each service is self-contained and implements a single business capability. Microservices can be reused in more than one different process or over different business channels. These services exist as independent artifacts, that can be scaled without any dependence on other microservices. See Microservices documentation for more information.

Savings Pot

Savings Pot Microservice provides an independent cloud-enabled solution for managing savings pot information that is required for both the front office (Infinity) and back office (could be Transact or any other back-office system of the bank).

Based on the data access interfaces planned, the NoSQL database model is chosen as the data model for managing savings pot information. NoSQL is the standard language for dealing with unstructured text. NoSQL can be used to insert, update, and retrieve database records. NoSQL databases are more scalable and provide superior performance.

The distribution service of Savings Pot Microservice is fully containerized and deployed independently irrespective of any back-office system of the bank.

Enhancements

• No enhancements.

Originations Data Storage

The Originations Data Storage (ODS) microservice is the storage service that implements the storage features offered by Journey Manager. This is mainly because the requirements will come from the development of custom user Journeys and Journey Manager has been developed from many years of writing these journeys and it makes sense to learn and expand these features rather than start from scratch.

Enhancements : NA

• Bug Fixes : NA
• Framework adoption : 202304.0.0

Release Highlights

• Start-up time reduction changes.
• Helm rollback and upgrade.
• Update in Mongo DB in K8s.
• Removed create statements from DDL scripts.

Portfolio Holdings

The Portfolioholdings Microservice stores the portfolio balances, instrument details, and customer allocation details based on the asset and sub-asset details.

Enhancements

• No enhancements.

Organisational Reference Data Microservice

Organisational Reference Data Microservices needs to provide an independent cloud-enabled solution for managing Organisation Structure's information that will then be used across the banking solution through dedicated configuration data. It contains all reference data describing the structure of Financial institutions.

Based on the data access interfaces planned, the NoSQL database model is chosen as the data model for managing Organisation Structure's information. NoSQL is the standard language for dealing with unstructured text. NoSQL can be used to insert, update, and retrieve database records. NoSQL databases are more scalable and provide superior performance.

Moreover, this distribution service of Organisation Structure MS is fully containerized and can be deployed independently irrespective of any back-office system of the Bank.

Enhancements

• Consumed latest 202304.0.1 MSF version.
• Helm Package reduction is implemented to reduce the size of the Helm package.

Marketing Catalog

Product Marketing Catalog Microservices provides an independent cloud-enabled solution for manage Marketing information of any Backoffice systems. Microservice exposes management APIs through IRIS for bank users to manage marketing information for products provided in the bank.

Enhancements: NA

• Bug Fixes : NA
• Framework adoption : 202304.0.0

Release Highlights

• Start-up time reduction changes.
• Helm rollback and upgrade.
• Removed create statements from DDL scripts.

Due Diligence

Due Diligence is the investigation or exercise of care that a reasonable business or person is normally expected to take before entering into any agreement or contract with another party or an act with a certain standard of care. Thus, Due Diligence APIs paves a way to maintain the investigation or assessment details of a party.

Enhancements

• Due Diligence MS: interestRate, sourceOrProviderName, termRemaining are made mandatory in V1 APIs.
• Azure Stack-enablement and testing for Enhancing Financial Information - Retail - Secured and Unsecured Lending.
• Helm Upgrade , rollback , build changes - CDD.

Holdings

Holdings Microservice has APIS to get Balance details and Transaction details of an account. It has a DB to store the same. It is capable of both internal (t24) ingestion and also external Ingestion from aggregator. HMS has the capabilities to store the Portfolio Details and Allocations of an account.

Enhancements

• Merging of Arrangements functionality into Holdings MS.
• Enabling the support to store details of the services linked with an account.
• Enabled the property “db_upgrade_start_version” in all the stacks to specify the version of the microservice solution from which the DB upgrade is being performed.
• Upgraded the Tomcat image version for docker and Kubernetes deployments.

Changes incorporated in HMS

Dependencies

Application	Versions
HMS Version	23.0.0
MSF Version	23.0.0

Defects

• Duplicate transaction details for the account loaded in the OLB transaction listing.
• Ingestor having multiple errors in Holdings Microservices.
• Updated the metadata files to fix the AWS and AZURE automation related issues.

Document Storage

Document Microservice is used for uploading and downloading the documents. It integrates with FormPipe for upload and download of Documents.

Enhancements

• Changed MySQL db instance from Aurora to MySQL Community in EKS setup.
• Helm rollback and build changes.
• Changed EKS file structure.
• Startup time reduction.
• Change in default database.

2021.08 release is the first version that fully supports multi-language. It’s recommended for all clients to use in production. No changes are required.

DO NOT use any previous internal release in production.

Consent Management

Consent Microservice is used to create, modify, and retrieve consents. As a part of Account Aggregation, it is important to record Customer’s consent to retrieve his account information from external providers like Salt edge. Consent Microservice is used to maintain the consent given by the user, and defines the scope of the consent.

Enhancements

• Enabled the property “db_upgrade_start_version” in all the stacks to specify the version of the microservice solution from which the DB upgrade is being performed.
• Upgraded the Tomcat image version for docker and Kubernetes deployments.

Changes incorporated in CMS

Dependencies

Application	Versions
CMS Version	23.0.0
MSF Version	23.0.0

Defects

• Updated the metadata files to fix the AWS and AZURE automation related issues.

Campaign

Campaign Microservice enables the branch users of banks to define and store the details of the campaigns created through the front office solution developed for the campaign management, which is called as Real Time Engagement (RTE).

Enhancements

• Consumed latest MSF version 202304.0.1.

Account Aggregation

The Account Aggregation Microservice contains the following elements:

• The Other Bank Directory holds the other bank details.
• The Salt Edge Integrator communicates with the Third-Party Provider (TPP) and transfers the respective account and transaction details to the Arrangement and Holdings microservices. The Arrangement microservice will hold the static details of the accounts received from the TPP provider.
• Account balances and transactions are stored in the Holdings Microservice.
• The External Connection Manager holds the connection details for the TPP for every digital profile user.
• The Tracker component tracks whether the account transactions and balances are successfully loaded to the respective Microservice.
• The Consent Microservice will store the consent received.

Enhancements

• Enabled the property “db_upgrade_start_version” in all the stacks to specify the version of the Microservice solution from which the DB upgrade is being performed.
• Upgraded the Tomcat image version for docker and Kubernetes deployments.

Changes incorporated in AAMS

Dependencies

Application	Versions
AAMS Version	23.0.0
MSF Version	23.0.0

Defects

• Updated the metadata files to fix the AWS and AZURE automation related issues.

Arrangement

Arrangement Microservices needs to provide an independent cloud-enabled solution for managing Accounts information for a customer.

Enhancements

• Enabled an API for access through MDAL layer to retrieve posting restriction details associated with an arrangement.
• Enabled an API for access through MDAL layer to retrieve account payment details for an account with a capability to query based on alternate references such as IBAN, Account Id (Id mapped to the record in ACCOUNT table) and so on.
• Enabled the property “db_upgrade_start_version” in all the stacks to specify the version of the Microservice solution from which the DB upgrade is being performed.
• Upgraded the Tomcat image version for docker and Kubernetes deployments.

Changes incorporated in AMS

Dependencies

Application	Versions
AMS Version	23.0.0
MSF Version	23.0.0
IRF Version	23.0.0

Defects

• Updated the metadata files to fix the AWS and AZURE automation related issues.
• MSV-1032 -- AMS v2021.10- get arrangements by product line.

Service Request

Service Request Microservice is a generic order management system that helps to capture different service requests raised by customers from Digital Retail Banking channels and refers to maintain the entire lifecycle of all service requests.

Enhancements

• No enhancements.

Corporate LOS

This Microservice enables lending facility for a corporate customer under Bilateral lending arrangement. The corporate loan origination service (LOS) micro-service does help the Banks to do different tasks/flows involved in Corporate origination. It also facilitates to orchestrate and capture all the related information like Borrower details, Parties involved, Deal Details, Facilities etc.

Enhancements: NA

• Bug Fixes : NA
• Framework adoption : 202304.0.0

Release Highlights

• Start-up time reduction changes.
• Helm rollback and upgrade.
• Removed create statements from DDL scripts.

Party

Introduction

• AKS enablement.
• ImposePartyId- getPartyV1 API retrieved the party details when supplied with Transact Customer ID. Party ID returned in the output payload contained the internal Autogenerated Party ID.

Release Highlights

• AKS enablement.
• ImposePartyId- getPartyV1 API retrieved the party details when supplied with Transact Customer ID. Party ID returned in the output payload contained the internal Auto-generated Party ID.

Enhancements

• Enhancement for impose party id, to gat the party details based on the business key. If the party MS is slave, then to inject the customer record from T24 CUSTOMER application the customer id will save into to business key column with legal entity. Based on the business Key the party details will reply.
• AKS enablement is done for party MS.

Digital Banking Servicing Channel Micro Apps Known Issues

• Special Character Validation in the edit flow of the Review Payment in Payment Status tab is not handled.

Spotlight Known Issues

• Auto subscribe option under Alerts configuration is not functionable and will not automatically subscribe the newly enrolled users to the configured alerts.

Wealth Known Issues

• Risk Analysis design and implementation completed, testing to be done in official R23 AMR TAP release.
• In Asset allocation under portfolio health section, the table and graph needs to be displayed only for accounted positions.
• In personalize strategy, the model portfolios and Instruments should not be allowed for personalization.
• In IOS app the asset allocation card inside the Portfolio Health Check section have graphs missing parent segments and labels indicated as having issues for both Portfolios.
• Holding constraints are displayed when linked to an IP is displayed in Allocation view. This would be deleted from the allocation view in future release.
• Type Error - TAP - IOS - In IOS Type error is getting displayed in Review Proposal screen.
• When we navigate to Place a New Order screen from instrument search/ Holdings the cash balance is not getting displayed.
• Facing scroll issues in Allocation Carousal for Sector Allocation.
• Personalize Strategy - Unable to modify/personalize the same segment more than one time.

Wealth - TAP Known Issues

• For a newly created bond instrument (t24) in an end to end TAP environment, the TTI mapping rating field needs to be changed and new mapping needs to be provided with respect to Rating Attribution table.
• For DX Instruments the denomination name field is not mapped under instrument details api, this requires to be enhanced.
• In TAP for derivative instruments, the instrument code is displayed with forward slashes, but instrument code needs to be passed as query param, this requires an API change.
• Fees and Taxes is not flowing from T24 to TAP in cloud environment.
• Modifying DMA & NDMA orders is reflected in TAP but not in T24.
• For an advisory/Non advisory portfolio when the customer and portfolio currencies are different there is a data issue with the unrealized PL value.

Retail Origination Known Issues

• Inconsistent getTask failures because of timeout issue.
• Inconsistent Technical error while doing customer action tasks.
• After approving the document, the focus doesn't stay on the current expanded section.
• Accessibility issue in few screens in Origination.

SME Origination Known Issues

• Inconsistent getTask failures because of timeout issue.
• Inconsistent Technical error while doing customer action tasks.
• After approving the document, the focus doesn't stay on the current expanded section.
• Accessibility issue in few screens in Origination.