11 December 2023

Release nXP 2023.2.0.0 focuses on the upgrade of the IdentityServer 4 (IDS) to Duende IdentityServer 6 and on features that allow the Corporate segments to manage the users of their contracts on the self-service channels, Internet Banking (IB) and Mobile Banking (MB), by allowing them to manage user access, credentials and add delegates. Personalisation has been improved by allowing IB and MB users to define the widgets they want to see in their dashboards.

At the Architecture level, there have been some improvements and changes related to iOS and Android to support the integration of these platforms in the version 2.0 of Studio X. There are breaking changes that may impact the projects.

This release updates the IdentityServer 4 to Duende IdentityServer 6. This update was required to evolve to a supported version and to improve the platform security, as Duende IdentityServer 6 also brings important security fixes.

The process of upgrading the project, it is not expected to be difficult. One of the main criteria for choosing the Duende IDS was its continuity with the previous one. Please keep the current IDS endpoint when upgrading from nXP 1.1 to nXP 2.0. This will guarantee that all biometric and pin authentication will remain working when final users update the app by downloading the new app from the store. Otherwise, final users must log in with their user and password.

Regarding the licensing of Duende IdentityServer 6, all project versions should communicate with ebankIT before moving into production to ensure the licensing management.

This release launches a new Authentication Server page and the old IDS page is no longer distributed with the ebankIT nXP platform. The user interface (UI) of all authentication options such as login, credentials’ recovery and logout have been reviewed to improve the coherence with other IB functionalities and provide a consistent experience when moving from the IDS to the IB .

A new application, the Contact Centre (CC), has been added to the nXP platform. This application has the same functionality as the Branch Front-office (BFO) but allows the Financial Institutions (FIs) to answer to customer requests remotely via phone, chat or email.

New option available in the IB and MB to manage the credentials and access to the contract. Contract owners can remove or reinstate the access to the contract for all contract users. For delegates (users with access to the contract who are not FI customers) only, if their credentials are locked, the contract owner can easily unlock them directly in the IB or MB. The same can be done with the password. Contract owners can reset the password for delegates. Delegates will then receive a temporary password to use on the next time they log in. Users with access to the contract who are FI customers must reach the FI via BFO or CC to unlock their credentials or reset the password.

Manage credentials

The option to manage credentials in the BFO and CC has been improved in this release. If a contract can be accessed by more than one user, a drop-down allows the BFO user to select each delegate to manage their credentials. For Individual contracts, the contract main owner (the authenticated user) is selected by default. Trustees must be authenticated into their individual contracts to manage their credentials.

Contract owners can now add new users – delegates – to the contract directly in the IB. Delegates are not FI customers. Adding existing customers to the contract can only be done in the BFO or CC.

For project teams, this feature has a number of configurations that help to meet each FI requirements, by defining the fields that are displayed and their rules.

IB and MB users can now define which widgets they want to see in their Dashboards, the landing page after the login. It is possible to define which widgets are visible and in which order. Users can define a different dashboard for IB and for each device where they have installed the MB application, following what they prefer to see on each channel or device.

Dashboard widgets

New widgets have been added to the Dashboard, mainly to improve the experience of the Corporate users:

The limits management has also been updated in this release to give FI and their clients/members greater flexibility when defining the platform, contract and permission group limits. The IB and applications display now the limit for each transaction.

Multiple limits per rule

Users can define multiple limits per rule when setting the limit and permission rules in the platform (EMS) or in the contract and permission groups (BFO). This allows to set the same rule limits for different frequencies and limits for both amounts and number of transactions.

Limit buckets

This release includes the possibility to have different creation and approval limit counters that are independently controlled. This means a limit for the transactions' creation and another one for the transactions’ approval. For instance, a limit defined fort the creation of transactions will not impact the approval limit.

Transaction limits

New component that can be added to transactions that displays the available limit for that transaction. This option is available for IB and MB.

The EMS now has a new area dedicated to audit logs. Designed to meet the audit and compliance requirements of Financial Institutions, it collects the history of the platform management of all users and types of action. In this area, it is possible to view all the platform changes made using the EMS and track other updates made during the same session, as well as the entire history of changes concerning a specific activity.

New option in the EMS for FIs to manage the backups of their databases.

In the BFO and CC, it is now possible to edit the contacts, email and phone number, of the authenticated client and of the delegates with access to the authenticated contract. Trustees must to be authenticated to their individual contract to change the contacts.

The FI can choose to collect data from the campaigns. This data includes information about campaign responses, number of views, and more. The flexible and straightforward campaigns management module is the key of the FI to improve their performance.

When saving the campaign data, the customisable data purging mechanism allows to set a timeframe to keep the information. Otherwise, the rules that define when a campaign is displayed to a user are associated with the priority defined for each campaign, as with this configuration there is no data to display.

Users can now manage their privacy consents in the MB. This option was already available in the IB. In the BFO, the privacy consents are only available for Individual users, as this option does not concern companies or Corporate groups.

The option to Manage mobile devices in the BFO or CC has been improved in this release. If a contract can be accessed by more than one user, a dropdown allows the BFO user to select each delegate to manage their mobile devices. For Individual contracts, the contract main owner (the authenticated user) is selected by default. Trustees must be authenticated into their individual contracts to manage their own mobile devices.

When a BFO/CC user selects the option to handle a process, they become its owner, which means that no other user can handle it. From this release onward, users with the Supervisor or Administrator role can remove the process owner so it can be assigned to another user. This logic is now available for all process types.

Process search

To improve the performance when searching for processes in the BFO and CC, the list of processes is now arranged by status:

Users can now change their password also in the Mobile Banking.

To improve security, the OTP and contacts data are now obfuscated in the log files.

The UI of the following features has been reviewed to ensure a better user experience (UX). The improvements followed the insights gathered from the usability tests:

Minimum software requirements for development.

Minimum software requirements to run the applications.

Download the complete Technical Release notes, including release requirements, fixes and improvements.