Livy Integration is a new feature in TDE, which provides a centralised option to submit and monitor the spark jobs, and control the spark session and context instance.

This feature provides lightweight, client-side (JavaScript or jQuery) framework allowing banks to declare custom buttons for automatic injection into targeted Version screens.

This feature provides a deployment mechanism that can be automated and covers complex scenarios with circular dependencies between packages. The feature also provides a retry option, if the deployment fails for any reason.

To allow continuing overdraft ageing from the legacy system post migration, the Limit Property Class is enhanced with new attributes to capture the first overdraft date from the legacy system during the takeover.

This feature provides a list of cryptographic algorithms using which users can encrypt the plain text password and then use this encrypted password in Integration Framework (IF) products.

This Mechanism is introduced in Temenos Transact, which provides features to consume, convert and store the error records in Temenos Transact.

The Data Packager feature now supports wildcards and content assist when adding a record to a package through web interface or IDE import menu. The wildcard (*) can either be used separately or combined with characters as required, to import records in bulk mode.

Scheduler is a framework feature that comes bundled with Temenos Micro Services Framework (MSF). It enables the underlying microservice applications to schedule the business processes for execution at regular intervals using CRON expressions. It also provides support for monitoring of scheduler instances.

In Data Packager, the data structure feature has been enhanced such that users can now load maximum possible dependencies for a given model. Also, the users can filter and load only L3 records into the package.

NuoDB which is part of Microservices Framework is an elastic SQL database for hybrid cloud applications that scales-out on-demand and ensures continuous availability of services. It provides standard database interfaces, operations, and guarantees consistency and durability.

Entitlements are sets of privileges configured for users which define the type of operations an application user can perform on the resources.

The Lending and Deposits modules in Temenos Transact now support Risk Free Rates (RFRs) processing. The Interest Property Class is enhanced with new attributes to accept appropriate market conventions and compounding methodology and options for margin treatment to support RFRs.

The OTC derivatives operational workflow in Temenos Transact is enhanced to support the transaction reporting requirements of MiFID II.

Application Framework

This feature introduces a scalability mechanism where an external orchestrator such as Kubernetes identifies the workload based on various attributes and issues new containers using scale metric from Temenos Transact.

This feature allows users to capture elastic fields in workload profile for dynamic agent allocation for non-cloud implementation. It is fully compatible with Multi-Server configuration and supports distinct configuration for the multi-servers independent of each other.

The exposure against a Limit can be updated in near real time using the LIMIT.UPDATE.SERVICE. To enable this functionality, the Delay Txn Update field is added to the LIMIT.PARAMETER application.

Users can now send inflow requests using a Restful HTTP API (http://<host:port>/inflow/api/V1/process).

This feature allows users to control the authorisation for every API and restricts anonymous user requests.

The flexible repayment is enhanced with the additional key features to overcome limitations and keep the defaulters in check.

The TXN.ENTRY.MB enquiry is now enhanced to display the entries based on Arrangement ID and Activity ID. The enquiry is also made accessible through context sensitive enquiries (using More Actions tab) of AA.ARRANGEMENT.ACTIVITY.

The Pre Grace attribute is introduced in the Overdue Property Class, which enables the user to configure the system to defer the first overdue processing till the end of the immediate working day when an installment falls on a holiday.

The MONEY.MARKET application that captures and processes (L)IBOR-linked transactions is enhanced to calculate the interest rate in arrears, based on the RFR and interest rate spread.

Analytics

ODS and SDS support PostgreSQL database, in addition to the existing databases.

Additional APIs are now introduced into ODS to access different forms of data in Data Lake solution through Semantic Query Layer, which separates the read from the Temenos Transact system.

Data Store Deployment is a new feature added to TDE to automatically deploy Temenos Transact applications in DES, ODS and SDS, instead of deploying every application manually.

This feature provides users with a standard L1 interface (generic SWIFT Alliance Interface) to process any SWIFT message.

Users can now fetch queue health, current Hostname, and Temenos Transact health using this service.

In DSF Packager, users can now compile and package jBC and Java codes along with Data records.

The API end points of Microservice Framework now supports to upload and download the files through multipart content type.

Based on the entity and API json files available under the model project, it is now possible to generate the metadata.

Bundles are now enhanced to generate an IBAN by attaching a customised routine in Alt Acct Gen Api field in ALT.ACCT.PARAMETER table.

Various attributes are introduced in the CL.PARAMETER, CL.COLLECTION.ITEM and CL.ACTIVITY tables to support multi-currency collections.

The SWAP application that captures and processes (L)IBOR-linked transactions is enhanced to calculate the interest rate in arrears, based on the RFR and interest rate spread.

Azure Event Hub, Azure Data Lake Storage, Azure SQL, and Kubernetes (K8s) features have been added in Temenos Data Engineering (TDE) product to support cloud native service.

If the customer is not blacklisted, Temenos Transact calls the Operation API to validate the eligibility of the customer to perform foreign exchange (FX) transactions. If the API response returns true, then the user will be able to authorise the payment. If the API response returns false, then the user won’t be able to authorise the payment.

The payment amount for future scheduled disbursements can now be calculated progressively and projected to the customer on the arrangement date.

Upfront profit contracts with a flat rate of profit calculation can have multiple disbursements and the profit amount is calculated for the financed period.

In upfront profit contracts with a flat rate of profit calculation, a custom routine can now be attached to the Interest condition to define the conditions for recalculation of the profit amount in the contract.

The interest accruals during initial grace period for a loan repayment can now be capitalised to the principal amount.

This feature allows bank to manage the start or stop for services during Close of Business (COB) and manage the number of agents. This does not require the bank to add that job(s) into the respective COB batch records.

The Legal Fee Cap functionality calculates the charge amount and overrides the final charge amount per day based on the cap fee rule, for each fee available in a particular loan account.

This functionality allows users to define different deposits products offered in Mexico.

This functionality allows the bank to integrate with the Watheeq Edge system. The Watheeq Edge system supports the integration of financial institutions with various statutory organisations of Saudi Arabia.

This feature allows the users to register a switching instruction from an existing Temenos Transact current account to an external account opened in another bank.

The EB.ALERT.REQUEST application is introduced, where the user can create a record to define all the available alert events. The messages and alerts that are sent to the client will be stored in the EVENT.LOG application.

This functionality allows the user to create new customers as per the Indian regulations. When a customer is onboarded, the customer record will be created and the following information will be validated: nationality and residence, address, date of birth, identification documents, industry codes (if applicable) and the customer relation (if applicable).

The Queuing of Payments functionality ensures that the collectible amount shall not be utilised by the customer for any other purpose than the prioritised collections already existing in the queue.