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.

Transfers Micro App

Unified Transfers Flow

• Domestic transfers (instant or non-instant) can be initiated in any currency, either with BIC or National Clearing code, and the payment system is/can be configured to route the payment to the appropriate clearing.
• International transfers support the emission of payment messages either in MT or MX format of SWIFT.

Confirmation of Payee

• Confirmation of Payee is validated during new payee creation and make transfer flow (Domestic) based on the configuration in Spotlight.
• Customers can re-validate the payee's confirmation during the payment initiation (make transfer flow) for an already verified payee.

Trade Finance Micro App

• Trade Finance Transact Integration

  Implemented below three API flows to integrate with Transact. Trade Finance backend data is stored and retrieved from Transact.

  • CreateImportLC
  • CreateOutwardCOllection
  • CreateGurantee

Trade Lending Micro App

Introduced a Lending Dashboard in Digital Banking so that Corporate/Business customers can have a 360-degree view of Lending Products held with the Bank.

Lending Channel is a tool to access Deal/Facility/Drawing contracts details, and as a corporate, customers can view their existing contracts and balances. Corporate customers can also initiate drawdown requests and view balances, repayments, etc., from channels on this Corporate Lending Dashboard. At any given time, corporate customers should be able to view their Deal/Facility/Drawing contract details with the latest balances.

Introduced feature "Lending Dashboard" and action under 'Master Data Management' in Spotlight application; this feature is enabled only for the Corporate/Business Banking channel as this feature is applicable only for corporate/business customers. Enable these features and actions in the Corporate/Business Banking app through 'Service Definition configuration' and enable this service definition to customer roles "Maker" and "Authorizer."

Lending Dashboard

• Introduced Payment Initiation and Drawdown Request creations via quick links shown in the Lending Dashboard.

Payments Quick Link

• The customer can initiate/make payments towards pending Bills against his Facility/Loans. Customers can pay the amount either at the facility level or loan level.
• The customer can repay the full outstanding amount or a partial/specific amount towards his facility/loan amounts.

Drawdown Request Quick Link

• Customers can request a new loan against the existing facility.
• Customers can select a facility, capture the loan amount and loan tenor, add customers who should be part of the loan and the roles of each customer, capture pay-in and payout details, and submit the drawdown request.

Approval Matrix Micro App

• Introduction of Approval Framework for Non-Monetary Actions.
• The Beneficiary Management Approval Framework will support Single Contract and Multi Contract Scenarios.
• The Beneficiary Management Approval Framework will support notifications in the Notification Centre, email, and SMS for creating, editing, or deleting a Beneficiary from the Initiator and Approver Perspective.
• The initiator can view his request (Create/Edit/Delete) in the Request Dashboard.
• The Approver can also Bulk Approve the Non-Monetary Actions (Create/Edit/Delete).

Approval Matrix functionality has been enabled for Retail customers

• Setting up of Approval Matrix.
• Display of Request and approval Dashboard for Retail customers in OLB.
• Transactions are to be executed based on rules defined in the Approval Matrix.
• To support both user-based and signatory-based approval.

Approval Matrix Functionality has been enabled for Beneficiary Management for the Same Bank, Domestic, and International Transfer flow

• Capture the Beneficiary Details in the Channel App.
• Request to be sent to Approvals and Request Dashboard.
• Non-Monetary Approval Matrix Feature Creation.
• Appropriate notification to be sent to the user logging into the Online Banking Application.
• Appropriate status needs to be shown in Manage Beneficiaries.

Approval Framework 2.0

• Framework 2.0 can work for all approvals but is the preferred method for actions across multiple customer IDs. Beneficiary management is the premier feature action for Framework 2.0.

Approval Request Micro App

Approvals and Requests now supports setting up of rules for non-monetary action - Beneficiary Management.

Creator can raise a request by:

• Adding a new Beneficiary.
• Editing an existing Beneficiary.
• Edit Recipient Linkage - Linking/Delinking a contract, in case of multi contract.
• Removing a Beneficiary.

Non-Monetary actions also support Bulk approvals.

Arrangement / Home page Micro App

• For Mobile Banking app, combined statement generation has been enhanced to accommodate the multi user changes for both Retail and SME, means when the end user selects the accounts associated to multiple customers while generating the statement then the generated statement contains all the customer details associated to the selected accounts.
• In the account summary, we are showing overdraft balance, overdraft limit fields only for current and savings account types, and the OD is attached to the account; if the OD is not attached and the available balance is negative, then we will show the overdraft balance as the available balance.

Embedded Origination in the Mobile Native App

• A new menu item is introduced for the Mobile Native application in the Hamburger menu post login - 'Open New account' for the user to navigate to the 3rd party origination application in the embedded view. This feature can be enabled/ disabled for the user by the bank user from the spotlight application based upon the Feature/action - 'New account opening - Open new account.'
• On clicking this feature, the user will be redirected to the relevant 3rd party origination application (The origination URL endpoint can be configured by the bank user in the Fabric app), where the user will have options to explore and open new products offered by the bank.
• This feature/action - 'New Account Opening,' will be applicable for Retail Banking and Wealth Banking service definitions.

Account Sweeps Micro App

• Account sweep is now being enhanced to integrate with Transact application [AC.CASH.POOL].
• A new parameter is being introduced in the DBP bundle configuration in spotlight to define the Transact Sweep rules to be used in API mapping.
• Restriction removed to map account as a secondary account in different sweep instruction.

Alert Settings Micro App

As part of the user experience improvement exercise, for users having access to a large number of accounts, the UI enhancement has been done to present the listing of a large number of accounts in a better format and improve the response time for UI loading.

The Alert setting module (Alert Settings > Account) has been enhanced to support users having access to more than one contract or a large number of accounts. For multiple contract access, the listing of accounts is based on per customer ID. In the case of large accounts, the listing is paginated for quicker loading. In this release, the enhancement applies only to the web responsive module and not to mobile native.

Authentication Micro App

Embedded Origination in the Mobile Native App

• Introduced a new landing page for the mobile native application for first-time users. Users can view this new landing page when downloading the Temenos Digital application on their mobile device for the first time. The page will contain options - "Explore Products - Directs the user to explore products via the origination flow," "Resume application - Allows the user to resume any partially filled origination application," "Existing user Login - Lands the user to the default login page of the Temenos Digital application."
• The new landing page will be configurable based on the bank's requirements. If this configuration is enabled, the user can view the latest landing page options upon first login. If this configuration is disabled, then the user will be shown the existing sign-in page to the user by default.

Digital Wealth

Multi-Customer Dashboard

Multi-Customer Dashboard feature will be introduced in the Portfolio Management MicroApp. This new feature is designed to enhance user experience by providing access to multiple customers through a single dashboard.

• Unified Access: Users can now seamlessly access two or more customers from a single interface after logging in. The new Dashboard screen will display a list of all accessible customers, streamlining navigation between portfolios.
• Effortless Navigation: Users can easily navigate between different customer details and portfolios without the need to log out and log back in.
• Favorites: Easily mark and filter customers by “Favorite” for quick access to the most frequently accessed customers.

Generic Changes for all the Temenos Digital Apps

Performance improvements are made in the Digital applications (Spotlight and Digital Banking) for the modules listed below in R24.

• Spotlight Contract and Customer management, Customer role, and Retail Banking User Management modules
• Approval request framework, Approval History
• Customer search and Customer details fetch
• Mobile Native login
• Retail Banking login and Dashboard
• Mobile Login Experience API's
• Mobile Login UI enhancements
• Merging of Arrangement into Holdings

Migration API

Migration APIs for the below functionality are now available for the implementation teams to migrate data from the legacy system to Temenos Digital. These APIs can be used for the R23 version as well.

• Create Contract
• Link Existing Customers to Contract
• Create Virtual User (Digital Only)
• Create Signatory Group
• Create Approval Matrix Rule
• Update Approval Matrix Mode
• Create Beneficiary
• Create Beneficiary for P2P
• Create Beneficiary for Bill Pay
• Update Limit- At the contract level
• Update Limit- At the accounts level

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.

• Microservice dependency for Campaigns Designer in Spotlight and Campaigns Engine has been removed and is now configurable to connect either to DBXDB or to Campaigns MS.
• Microservice dependency for ORDMS for Multi-entity has been removed and is now configurable to connect to either DBXDB or ORDMS.

Maker Checker

• Maker Checker has been enabled for the below features:
  • Enroll Customer
  • Edit Customer
  • Create/Edit Contract
  • Create/Update/Delete Signatory Group
  • Create/Update Approval Rules
  • Activate/Suspend User
  • Create/Edit Customer Roles
  • Service Outage Message

  For Enroll Customer, Edit Customer, Create/Edit Contract, Create/Update/Delete Signatory group, handcrafted screens will be there where we show old and new value as well. For other modules, it would be only updated changes in Key-Value pairs.

• The Maker Checker framework can used to apply to other modules in Spotlight to enable Maker Checker.

Fixes

CSR Assist has been deprecated since 202104 and is now in 202404 removed from the permission list and from Spotlight.

Retail Origination Features

See Origination documentation for more information.

1. Collateral Screen Changes in Pre-Submission RM Initiation Process and Post-Submission Assist Flow
   • Pre-Submission – RM Initiation Process: Following are the changes that are done in the collateral screen in the RM Initiation process:
     • Removal of Document Tab: The Document tab in the Collateral section is removed as that screen pertains to capturing the property valuation detail per the Bank's values, which is done only in the post-submission processing. All the necessary validations that refer to this particular tab and the fields within that tab are removed.
     • The Advance Rate: The Advance Rate field in the Overview Tab of the Collateral section will auto-populate from the spotlight configuration and will not be a user-enterable field going forward. By default, the value that is set is 90%. The spotlight will have a new parameter to maintain the advance rate, and if the Bank is required to make changes to the advance, they can do that in the spotlight configuration. Whenever there is a change in the value in the spotlight for the advance rate, the updated value will reflect automatically at the application level. Still, the user has to save the updated calculation in the collateral section to bring that change to the application.
     • The adjusted collateral value will be calculated based on the Property Value (the estimated property value that the customer provides the RM at the time of initiation of the application). The revised formula will be an Adjusted Collateral Value = Property Value (Advance Rate / 100).Users can save the details in any tab in the Collateral section. Till now, the save button was enabled only in the Comments tab, but going forward, the save button will be enabled in all the tabs of the collateral section, and the user can save the details as and when required.
   • Post-Submission – Assist

   Following are the changes that are done in the collateral screen in the Post submission process and the Entity Overview:

   • Document Tab: There is no change in the Document tab in the Collateral section in the Entity Overview and other the overviews in post submission. Initially, when the application moves from pre-submission to post-submission, the "Property Value" from the pre-submission RM screen will be auto-populated in the Valuation Amount field in the document tab. This field will be editable; whenever the Bank does the actual valuation, the updated valuation amount can be captured in the same field.
   • Recalculation of LTV: Whenever the property "Valuation Amount" field is edited, it will automatically recalculate the Loan-to-Value (LTV).
   • Advance Rate Field: The advance rate field will be non-editable in the Assist Post-Submission as well, across all overviews (RO, PO, EO).
   • Users will be allowed to save the details in the Collateral section in any tab when accessing it in the Entity Overview. Till now, the save button was enabled only in the Comments tab, but going forward, the save button will be enabled in all the tabs of the collateral section, and the user can save the details as and when required.
2. LTV Credit Component – Changes in MS

The calculation of credit components or ratios like DTI and Affordability ratio is done based on the formulas configured in the spotlight, and the ratio values are shown at the application level, except the LTV, which was coming from an MS. From now on, even the LTV will be calculated through the formula configured in the spotlight. The option to configure the formula for LTV is already available in the spotlight.

3. Funding Screen-related Validation in RM Initiated Process

Following are the additional validations included in the RM-initiated process concerning changes in the funding screen in the Product Information section.

• Requested Loan Amount Validation

1. When the user updates any information in the funding position section and saves the data, the system will verify that the requested loan amount is less than or equal to the maximum eligible loan amount.
2. If there is a mismatch, the system will display an error message and not save the updates. Message text: "The requested loan amount should be less than or equal to the maximum eligible amount."
3. This is an additional validation apart from the existing validation to ensure that the total source of funds is more than or equal to the total use of funds when the deficit is displayed in red. If the validations pass, the changes will be allowed to be saved.
4. Note - for fees defined as a percentage, since only the percentage is stored, the fee amount will be automatically calculated and displayed in the fee section.

Validation in the Submit Button

1. It should ensure that the application moves further only if the "Requested loan amount" is less than or equal to the maximum eligible loan amount.
2. If not, the system will stop the application by displaying the error message "The requested loan amount should be less than or equal to the maximum eligible amount."
3. Also, the system will ensure that the requested loan amount in the funding position matches the overall requested loan amount in the product and drawing sections. If not, the system will move the application and display the error message "Please make sure that the requested loan amount captured in the Funding section matches the overall requested loan amount in the Product section and in the Drawing section."
4. The validations mentioned above will be triggered once the mandatory check validation is successfully passed.

• Recalculation of Credit Components

The recalculation of the credit component ratios will be done automatically once the user saves the Funding Position screen and clicks on continue.

Corporate Lending Origination System (CLOS) Features

See Origination documentation for more information.

CLOS - Keycloak Configurations

Integrate the CLOS application with Keycloak and Spotlight, covering the functionalities below:

• Creation of User profiles (Roles) and User ID management (Users) using Keycloak and Spotlight.
• Migration of CLOS admin panel screen to Spotlight.

Merged the CLOS Admin Application with the Spotlight App to have one common place (i.e., Spotlight and Keycloak) for all Bank user creation, role creation, management and Permissions, and Business Parameter maintenance.

• Creating a deep link for the CLOS Admin panel and User Panel in the Spotlight
• To restrict User and Role Creation functionality built-in CLOS Admin app, as these will be done in Keycloak and linked in Spotlight. We will have Edit/Delete from Spotlight (CLOS Admin screen).
• To use the existing user authentication functionality of Key cloak to authenticate users required to log in to CLOS User Panels, and the same user can be used to log in to Spotlight (as SSO).

User Access Restriction

Users who are not tagged to the user profile admin in the user ID management → user profile setup → user profiles (Admin) should have only the view permission to all Admin screens.

Enhancements in CLOS Screens

• In ORR, FRR, and Financial Analysis, exceptions screens; we introduced a "History" button; this button is displayed only when the customer has data captured in these screens in the previous applications. On click of the History button, previous data pertaining to that screen as captured in previous applications are shown. Note: When the user initiates a new credit application, as the data in ORR/FRR/Financial analysis/Exceptions are all freshly entered, the History button is not shown.
• The exception setup screen is enhanced to add a new field. "Approving User Profile," which shows only user profiles tagged as approvers in the workflow.
• Reject functionality is introduced. When the Approver rejects any requests, the corresponding credit application/memo is updated with the status "Rejected."
• Corporate Lending Origination System (CLOS) Admin and User Panel features are available now both on SaaS and On-prem (earlier CLOS was supporting only On-prem implementation, now it also supports cloud Deployment).

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.

Originations Data Storage

The Origination 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

• Origination Data Storage Microservice has now been enhanced to have single helm charts for any Kubernetes Deployment (On-Premise, AKS in Azure and EKS in AWS).

• Origination Data Storage Microservice now supports Azure containerized (ACA) Deployments in Azure.

• Origination Data Storage Microservice has now been enabled User Audits feature from Microservice Framework for all creation and update of the Party records. With this audit feature enabled, Banks can now audit all financial and non-financial updates by the users and Customers in the Microservices if any.

Build Details

Application	Versions
MS Version	R24
MSF Version	R24
IRF Version	NA

Defects

• Packing pubsub JSON in catalog folder for SaaS deployment.

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 Microservice is fully containerized and can be deployed independently irrespective of any back-office system of the Bank.

Enhancements

• Organisational Reference Data Microservice has now been enhanced to have single helm charts for any Kubernetes Deployment (On-Premise, AKS in Azure and EKS in AWS).
• Organisational Reference Data Microservice now supports Azure containerized (ACA) Deployments in Azure.

Build Details

Application	Versions
MS Version	R24
MSF Version	R24
IRF Version	NA

Defects

• Packing pubsub JSON in catalog folder for SaaS deployment.
• SIT script correction according to MSF error response code standardization.

Arrangement

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

Enhancements

Arrangement Microservice now supports Azure containerized(ACA) Deployments in Azure.

Marketing Catalog

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

Enhancements

• Marketing Catalog Microservice has now been enhanced to have single helm charts for any Kubernetes Deployment (On-Premise, AKS in Azure and EKS in AWS).
• Marketing Catalog Microservice now supports Azure containerized(ACA) Deployments in Azure.
• Marketing Catalog Microservice now supports the Data Ingestion using Data Events (.json formatted events) and emitted using Outbox feature available in Transact when the commit capture happens at individual application level in Transact.

Build Details

Application	Versions
MS Version	R24
MSF Version	R24
IRF Version	NA

Defects

• Encode productId when productId has special characters like / to pass it as a path param in the IRIS API call.
• Packing pubsub JSON in catalog folder for SaaS deployment.

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 Microservice has now been enhanced to have single helm charts for any Kubernetes Deployment (On-Premise, AKS in Azure and EKS in AWS).
• Due Diligence Microservice now supports Azure containerized (ACA) Deployments in Azure.
• Due Diligence Microservice has now been enabled User Audits feature from Microservice Framework for all creation and update of the Party records. With this audit feature enabled, Banks can now audit all financial and non-financial updates by the users and Customers in the Microservices if any.

Build Details

Application	Versions
MS Version	R24
MSF Version	R24
IRF Version	NA

Defects

• Packing pubsub JSON in catalog folder for SaaS deployment.
• Reference data, Holdings, SRMS, Campaign, Account Aggregation, MCMS, and consent doesn't have a common health check path.

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

• Holdings Microservice now supports Azure containerized (ACA) package for deployment in Azure.
• Holdings Microservice has now been enabled User Audits feature from Microservice Framework for all creation and update of the Arrangements, Accounts and Portfolio records. With this audit feature enabled, Banks can now audit all financial and non-financial updates by the users and Customers in the Microservices if any. For Holdings Microservice, this Audit feature will work for external arrangements created/updated using APIs.
• Holdings Microservice is now capable of creating external arrangements like Line of Credit (LoC). It does also provide the balance update details to the mirror of external arrangements in the Transact system through events
• Holdings Microservice supports Temenos Packager for packaging and release the Master data/Reference data. This Temenos Packager can be used to release the base master data/reference data from L1, L2 and also L3 after deploying the Microservices.
• Holdings Microservice now supports the Data Ingestion using Data Events (JSON formatted events) and emitted using Outbox feature available in Transact.
• Enhanced to consider the balances update in Holdings for current value dated entry and their corresponding balances. In case the client has a setup of Value Dated accounting and any future value-dated entries coming, then persist the entries in the Transactions entity; the balance update should only be considered to update during SOD (Start of the day) of the COB on the particular future value date is reached.

Build Details

Application	Versions
MS Version	R24
MSF Version	R24
IRF Version	NA

Defects

• SIT script correction according to MSF error response code standardization.
• Events from transact not processed from holdings inconsistently.

Document Storage

The Document Storage Microservice provides the virus-free documents hosting capability for Temenos Digital. This is to support the upload of attachment against a journey (In-flight) or any other situation where documents upload/download is required. All files uploaded will be virus checked before they are persisted into the environment. Under the hood, it connects the various Document Management System (Currently being Apache Sling or Formpipe Autoform DM) and provides a set of common APIs to achieve a generic Document Storage solution that is vendor agnostic and core agnostic.

Enhancements

• Document Microservice has now been enhanced to have single helm charts for any Kubernetes Deployment (On-Premise, AKS in Azure and EKS in AWS).
• Document Microservice now supports Azure containerized (ACA) Deployments in Azure.

Build Details

Application	Versions
MS Version	R24
MSF Version	R24
IRF Version	NA

Defects

• Packing pubsub JSON in catalog folder for SaaS deployment.
• SIT script correction according to MSF error response code standardization.

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

• Consent Microservice now been enhanced to have single helm charts for any Kubernetes Deployment (On-Premise, AKS in Azure and EKS in AWS).
• Consent Microservice now supports Azure containerized (ACA) Deployments in Azure.

Build Details

Application	Versions
MS Version	R24
Parent (MSF) Version	R24
IRF Version	NA

Defects

• Kafka Apache URL issue - TPM MS.
• Packing pubsub JSON in catalog folder for SaaS deployment.
• UTP - Savings Pot MS, MCMS is not working in Stack 09.

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

• Campaign Microservice has now been enhanced to have single helm charts for any Kubernetes Deployment (On-Premise, AKS in Azure and EKS in AWS).
• Campaign Microservice now supports Azure containerized (ACA) Deployments in Azure.

Build Details

Application	Versions
MS Version	R24
MSF Version	R24
IRF Version	NA

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

• Origination Processing Microservice has now been enhanced to have single helm charts for any Kubernetes Deployment (On-Premise, AKS in Azure and EKS in AWS).
• Origination Processing Microservice now supports Azure containerized (ACA) Deployments in Azure.
• Origination Processing Microservice has now been enabled User Audits feature from Microservice Framework for all creation and update of the Party records. With this audit feature enabled, Banks can now audit all financial and non-financial updates by the users and Customers in the Microservices if any.

Build Details

Application	Versions
MS Version	R24
MSF Version	R24
IRF Version	NA

Defects

• Packing pubsub JSON in catalog folder for SaaS deployment.

Party

Enhancements

• Party Microservice now supports Azure containerized (ACA) package for deployment in Azure.
• Party Microservice now supports Alternate Id features that are available in Microservice Framework - Alternate Keys are used for fetching same data within Microservice, in addition to that of the existing record key attributes of any database.
• Party Microservice now supports the Data Ingestion using Data Events (JSON formatted events) and emitted using Outbox feature available in Transact.

Defects

• Kafka version change in Apache.
• Packing pubsub JSON in catalog folder for SaaS deployment
• Reference data, Holdings, SRMS, Campaign, Account Aggregation, MCMS, and consent don't have a common health check path.
• Facing issues due to multi-threading in Party MS.

Build Details

Application	Versions
MS Version	R24
MSF Version	R24
IRF Version	NA

Account Sweeps Micro App Known Issues

Resources Uniken Micro App

• This is a new Micro App added in shared which will be used for Uniken related features.

Configuration

• This app, by default, is 'excluded from build' in the OnlineBanking/DigitalBanking_composite app project.manifest file.
• To do a build run → SCAConfig.py in Visualizer\OnlineBanking directory (command python SCAConfig.py --scaType 2). This will include all the modules in the build.

Bulk Payments Micro App Known Issues

• Mortgage servicing changes repayment day and changes repayment account flows; current repayment day and current repayment account number are stubbed data instead of T24 data.
• Account setting screen rending is taking more time.
• Check management: The checkbook header is displayed before the list of raised checkbooks is shown in the UI.

Arrangements Micro App Known Issues

• In the dashboard at Mobile Banking, there was an issue with handling overdrawn labels for account types. It has been fixed now, and the overdrawn label appears only for savings and checking accounts.
• Mortgage servicing changes repayment day and changes repayment account flows; current repayment day and current repayment account number are stubbed data instead of T24 data.
• Account setting screen rending is taking more time.
• Check management: The Checkbook Header is displayed before the list of raised checkbooks gets displayed in the UI.

Settings Communication Micro App Known Issues

• When the user tries to search for a specific notification, the app crashes in a few scenarios.
• This issue is happening for a few devices and not for all.

Spotlight Known Issues

Reports

Quantum Fabric supports Jasper and Power BI, Jasper on Azure, and Power BI on AWS.

In Spotlight Reports, the Fabric Custom reports are showcased. This is supported only when Fabric is integrated with Jasper.

When Fabric is integrated with Power BI, these reports cannot be shown on Spotlight and would require enhancement.

Smart Business Banking Known Issues

• Only business/contract level permissions are working in the SBA application, where changes must be made to make customer-level permission to work from the SBA application.
• Multi-business/contract permissions are yet to be implemented in the SBA Application.

Retail Banking Known Issues

• UI Overlapping in Cards Set Limit screen.
• Combined Statement-PDF - USD Currency is displayed by default for all accounts.
• Back Navigation in the E-Statements screen is not working in OLB.
• Blocked Funds - The date column is displayed instead of the Reference Number while exiting print preview screen.
• Deposit Accounts - Delay in showing the balances in Account Overview screen.
• Advanced Search is not functioning for the selected category in the "My Money" feature.
• Mobile Native - Unable to edit/delete a sweep.
• Mortgage Facility_ Partial repayment_Installment flow and Tenure are not working in mock frmCardManagement Print button is not working in the Acknowledgement screen.
• Loan schedule, Loan details, Mortgage facility and Mortgage drawings are slow.
• Unable to Create chequebook requests in Oracle DB.
• MB-Servicing Homepage - Business cash position graph and Timeframe filter is not displaying.
• OLB/iPad - The dropdown list is not disappearing if we close/Click dropdown upwards or by clicking anywhere in the screen except in Dashboard.
• Created cards are not displayed after user clicks on Go to my cards page in Oracle DB.
• Cardless cash is not working when DB is Oracle.

Wealth - TAP Known Issues

• TAP (Instrument Details API Enhancement) - For DX Instruments the denomination name field is not mapped under instrument details api. Kindly do the enhancement.
• TAP API - New TAP API for Recent Operations / Transactions Api for View transactions should be provided.
• Fees and Taxes is not flowing from T24 to TAP in TAP_UTP environment.
• Modifying DMA and NDMA orders is reflected in TAP but not in T24.
• TAP - Include Orders - Pending Orders - For the partially executed orders when few of the quantities are partially executed and moved to history orders still its shown as pending orders quantity in Include Orders TAP API.
• TAP (10.0.0.5) - INT_E2E_UPG environment migrated to 10.0.0.5 host - When we try to add cash accounts to a customer in t24 and when we do trading post that the data point "Asset Code" is displayed as "Null" in the consolidated summary TAP API

Retail Origination Known Issues

• Temenos Digital Assist: Input validation for APIs is missing, i.e., adequately formed entered data is not ensured in the work-flow in an information system.
• Temenos Digital Origination: Weak Cryptographic Hash: hardcoded salt used and not obfuscated.
• In the Assist dashboard, Keycloak API is slow.
• Temenos Digital Assist: Low Vulnerable libraries (bcprov-jdk15on,jackson-databind,json,json-path,json-smart,kotlin-stdlib,okio) are not upgraded to the latest.
• Temenos Digital Origination: Low-vulnerable libraries are not updated to the latest secure version.
• RM details are not showing up in the Request Section in the Request, Facility, and Drawing overview when we deploy the latest Keycloak.

CLOS Known Issues

• In Credit Committee Decision - For Credit Committee members, "Deciding action" should be disabled, but it is currently enabled.
• While adding an additional party, address information is getting fetched from the main Borrower.