Skip to main content
Version: 4.2

Release notes

Version 4.2.0​

About Release
  • Released: August 17, 2026
  • Compatible platform version: Work.AI 10.3.2+

The v4.2.0 Evelyn release improves billing transparency, strengthens security, simplifies screening provider configuration, and introduces a naming convention for Firco unit format files.

Features

  • NSS billing events now use the standard WorkFusion billing contract and include extended metadata. The following updates ensure clearer billing attribution and remove the need for custom billing interpretation:

    • Evelyn emits one billing event for every successfully processed transaction.
    • Billing events include metadata, such as dw_name, dw_skill, and variation_name.
    • Business Process details are cached by the run UUID to avoid repeated Control Tower calls when multiple transactions are processed in the same run.
    • If a variation name cannot be retrieved, NSS logs a warning and sends an empty value.
    • If billing delivery fails, NSS logs the failure without interrupting transaction completion.
    • The legacy custom billing Data Transfer Object (DTO) and deprecated string-based API have been replaced with the typed BillingInfo API.
    • The odf_transaction_uuid field is replaced by transaction_uuid.

  • The NSS configuration has been simplified by removing the proactive and retrospective screening selection. The change enables you to select the correct screening provider faster without changing how existing integrations send or process screening requests.

    The How entities be screened? option has been removed from the configuration interface. The screening system setup now uses a single drop-down selector listing all supported providers: Dow Jones Risk & Compliance, World-Check One, Firco Trust, and Thomson Reuters CLEAR. The existing ongoing_monitoring payload value and backend processing remain unchanged for compatibility.

Improvements

  • To strengthen the solution's security, critical code vulnerabilities have been addressed by upgrading and aligning dependencies in the root Maven configuration:

    • Spring Boot upgraded to v3.5.16

    • Spring Framework upgraded to v6.2.19

    • Java Native Worker (JNW) parent BOM upgraded to v2.1.0.56 and Worker base to v2.1.0.46

    • Jackson BOM upgraded to v2.21.5

    • Apache HttpClient upgraded to 5.6.2

    • Apache HttpCore H2 to v5.4.3

    • Logback upgraded to v1.5.36

    • AssertJ upgraded to v3.27.7

  • The Firco Trust provider input configuration now specifies the format file convention for the Firco Trust unit field. The expected pattern is <unit_name>_format.csv. The update prevents processing errors and accelerates provider setup.

Bug fixes

  • Fixed the issue where the Name Screening Business Process failed with the Cannot parse value for key 'connector_output' as JSON of type java.lang.String error while processing the output from the Thomson Reuters (TR) connector. The TR response processor now handles the connector output correctly.

  • Resolved the UnsupportedClassVersionError exception in address lookup where Java Worker failed because it was compiled with a newer Java class file version than the runtime supported.

Last updated on