Skip to main content
Version: 3.5

Release notes

Version 3.5.4​

About Release
  • Released: April 20, 2026
  • Compatible platform version: Work.AI 10.2.8.54+

The Evelyn 3.5.4 release enhances quality control workflows, name matching precision, and REST API capabilities.

  • A new Rare and Screened option is now available in the Name matcher token overlap dropdown on the Model configuration screen. When the option is selected, matching requires both a rare token overlap and full token coverage of the screened name in the watchlist entry, reducing false positives in high-risk workflows.

  • The REST API response includes the automated quality control field, which indicates whether an alert is selected as a candidate for quality check. This helps downstream systems identify and process alerts that are subject to quality check review more easily.

  • To make quality control details more accessible, you can configure the REST API to return the full content of the quality check report rather than just a link. If the report is missing or corrupted, the response returns an error message instead.

  • Evelyn now supports a discrete risk-based selection mode for automated quality control, allowing alerts to be prioritized based on configurable risk categories (high, medium, and low) and score thresholds relative to the strong name matching threshold. You can define individual false positive selection percentages for each category and score intersection, while all remaining false positive alerts fall back to the default percentage setting.

Version 3.5.0​

About Release
  • Released: July 4, 2025
  • Compatible platform version: Work.AI 10.2.8.54+

The Evelyn v3.5.0 release introduces major enhancements to decision score calculation, location-based screening, output configuration, and usability improvements.

  • The decision score logic is refined to produce more accurate and context-sensitive results:

    • For False positive decisions, the final score now includes only the fields explicitly used during discounting.

    • For Need more information decisions, the final score includes all fields except those marked as Bad_Info or Not_Compared.

  • Evelyn now offers extended report location capabilities. Granular control over report storage paths is introduced, with options to include year, month, week, day, custom folders, and filename prefixes. The configurations apply to both Quality Check (QC) and HTML reports.

  • Location is now available as a new watchlist entity (WLE) type, enhancing screening for location-specific risk scenarios:

    • WLEs of the Location type are matched exclusively against address fields (country, state, city, street).

    • Non-location fields (name, date, identifier, gender) are ignored during parsing.

    • Accurate results require structured address data in both the WLE and screened data. Otherwise, the match returns Bad_Info (-1).

  • A new configuration setting is available on the Model tab to compare names using only first and last names, excluding middle names. This provides greater control over name-matching logic in cases where middle name data is inconsistent or irrelevant.

  • To provide detailed insight into the model's resolution at the individual field level, you can now add match-per-field columns to the QC report using a new setting on the Output tab in the AI Agent configuration form.

  • The previously separate Name enrichment and Location enrichment tabs are combined into a single Enrichment tab to simplify configuration and consolidate enrichment logic in one place.

  • Evelyn now supports custom worker profiles for bot steps, allowing different steps within a Business Process to run with tailored resource configurations. The improvement is particularly beneficial for high-volume operations, such as processing large CSV inputs.

  • Each ScreenedData and WLE record now includes a unique UUID to ensure consistent tracking and mapping across Manual Tasks, QC reports, and HTML reports.

Bug fixes

  • Resolved the issue in the FircoMessageDetailsProcessor bot step where missing nextFpStatus or nextNMIStatus values were not properly validated. Evelyn now displays clear and actionable error messages when expected statuses are missing or invalid in Firco alerts.
Last updated on