Skip to main content
Version: 3.10

Release notes

Version 3.10.1​

About Release
  • Released: August 21, 2026
  • Compatible platform version: Work.AI 10.2.9

The release improves usability and security by cleaning up the AI Agent configuration and updating a core third-party component to address known vulnerabilities.

  • The obsolete Stopwords settings are removed from the Model configuration, ensuring only relevant configuration options are displayed.

  • The log4j dependency is upgraded to v2.25.5 to address security vulnerabilities.

Version 3.10​

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

The Evelyn v3.10 release introduces more precise location matching, missing data handling in the discounting rules matrix, clearer CSV file upload settings, and improved validation on the output configuration step. Several reporting and matching issues have also been resolved for more consistent processing.

Features

  • The location matching logic now uses only selected address components to determine whether two addresses match or mismatch. Address components that are present in the data but are not selected do not affect the decision. For example, if only City is selected and both the input address and the hit address contain a country and a city, Evelyn compares the city values and ignores the country values.

    If a selected component is missing from either the input address or the hit address, Evelyn returns Need more information and routes the case to manual review.

    Component selection applies only to addresses supplied as separate components, whether one or several components are present. If an address is supplied as a single full address string, component selection has no effect and Evelyn compares the address as a whole.

  • The rules matrix now includes the Missing data option for comparison fields, such as date, location, and type. The new option lets you define how Evelyn handles incomplete data.

    When you select Missing data for a field, the rule matches when the field has no value in the input data, the hit data, or both. A matching rule resolves the hit as False positive. For example, a date rule set to Missing data matches when the date is missing from either side of the comparison or from both sides.

    Known issue: do not select Missing data for a name rule. Although the decision matrix allows this configuration, missing names are not currently supported. Evelyn returns a runtime error if the name is missing from either side of the comparison.

Improvements

  • Input configuration labels for CSV file upload have been updated to reduce confusion between input files and format files. The clearer wording enables faster NSS setup with fewer mistakes.

  • The Output step validation has been updated for the Custom folders and Custom file prefix fields. These fields now support only alphanumeric characters, underscores, and hyphens, with a maximum length of 25 characters. This prevents invalid output paths or file names.

Bug fixes

  • Fixed model matching for location hits when input_record_type = INDIVIDUAL and hit_record_type = LOCATION. When location watch list entity matching is enabled, the model now returns Not Compared for all non-location fields instead of returning mixed results.

  • Eliminated the issue where alerts were incorrectly classified as Needs More Information when all compared fields, including Gender, resulted in a mismatch. Now, alerts are correctly classified as False Positive based on the configured field mismatch discounting rules.

  • Fixed the issue that caused quality control (QC) reports to use an incorrect naming convention. Reports are now generated with consistent naming.

  • Eliminated duplicate QC report generation.

  • Fixed the deadlock issue that caused interruptions in NSS processing.

Last updated on