Version: 2.0

Release notes

Version 2.1

About Release

New features:

The range of data sources available for Kayla was extended with AMF (Autorité des marchés financiers). You can leverage the integration to make Kayla still more efficient in investigating KYC data changes.
Kayla's onboarding flow is becoming still more user-friendly. Redundant fields were removed from the configuration interface to reflect the shift to the rule-based requirement setup.
The human-in-the loop capability was improved to facilitate manual review in Workspace:
- The assignment layout was optimized for accelerated processing and better information accessibility.
- Instead of a non-informative user ID, you can now see the reviewer's username.
Under the hood, the address verification feature was strengthened by the ability to send addresses both as arrays and strings.

About Release

New features:

Setting even complex requirement logic has become easier and more convenient, and the number of variations required for multiple populations is decreased due to the following improvements in Kayla's user interface:
- Input processing requirements are configurable as field name and value pairs.
- You can now set multiple input source fields per requirement. Kayala checks these in the order they are set. If the primary field name is null or absent, Kayla checks the subsequent one(s).
For details on the above improvements, see Install and configure | Requirements.
A new CSSF (Commission de Surveillance du Secteur Financier) integration is now available on the Data Sources configuration page, allowing you to retrieve entity profile information from yet another provider. For details, see Install and configure | Data Sources.
For greater convience of working with Kayla's analytics, out-of-the-box dashboards were enhanced with semantic coloring.
Kayla's performance was enhanced due to migration to Java Native Worker and removal of the dependency on WebHarvest. For more information on Java Native Worker, refer to the guide.

Corrected issues:

Configured field names are no longer case-sensitive for the Sayari Graph API data provider.
Fixed the issue with Kayla's core BP failing due to a missing input bucket configuration even when the input method is set to email only. Now, if you set Kayla to use only the Microsoft Graph API Email input method, the BP picks the input file from the configured email and processes it as expected without requiring an input bucket configuration.