Release notes

Version 4.3.4

About Release

• Release date: August 26, 2026
• Compatible platform version: Work.AI 10.3+

The Evan v4.3.4 patch resolves the issue that prevented the output step from sending data for the second name when a webhook was enabled with multiple names. Both records are now processed and completed as expected by the AMM Business Process.

Version 4.3.3

About Release

• Release date: August 13, 2026
• Compatible platform version: Work.AI 10.3+

The Evan v4.3.3 patch resolves the issue that prevented users from opening a filtered custom Workspace queue using the manualTaskUrl field from a webhook. Such queues are now opened as expected using the transaction ID attribute.

Version 4.3.2

About Release

• Release date: April 13, 2026
• Compatible platform version: Work.AI 10.2.9+

The Evan v4.3.2 patch introduces a new Business Process (BP) called Adverse Media Monitoring Historical Result Loader. The BP retrieves and returns the latest completed investigations based on provided input parameters.

Version 4.3.1

About Release

• Release date: January 29, 2026
• Compatible platform version: Work.AI 10.2.9+

The Evan v4.3.1 release improves the accuracy of the reporting and name detection capabilities:

• The final report now displays only high-risk countries that were actually identified during the investigation so that the reported risk exposure accurately reflects the investigation results. The improvement eliminates irrelevant noise in final reports, enabling faster decision‑making and clearer stakeholder communication.

• The name detection logic has been enhanced for the cases when search_request exactly matches the name in a text without a surname, but the entity is primarily referenced in the text by the surname. The update improves the name recognition accuracy to deliver more reliable investigation results.

Version 4.3

About Release

• Release date: November 24, 2025
• Compatible platform version: Work.AI 10.2.9+

The Evan v4.3 release streamlines entity processing, improves investigation visibility, and boosts AMM performance. You can now process large volumes of entities faster with the new batch processing capability, adjust the scope of ongoing monitoring straight from manual review tasks, and benefit from improved transparency through customizable investigation statuses and automated compliance-ready comments.

Other major updates include smarter input handling, optimized data purging, ML model improvements for more accurate matching and better performance, and flexible content source prioritization. In addition, we have made the manual review process more transparent and user-friendly and optimized the final report layout.

New features

• To let you process large volumes of entities efficiently and in a shorter time, a new Batch Processing Business Process (BP) has been added to Evan to handle multiple AMM investigations simultaneously. The BP provides centralized management of reporting, notifications, and output generation across all investigations in a batch while coordinating the execution of individual investigations.

• You can now add entities to ongoing monitoring straight from an Ad-Hoc search Manual Task in Workspace, which gives your employees more control over and flexibility in how they handle screened entities. To include a request entity in the ongoing monitoring scope, all you have to do is check the Include request entities in ongoing monitoring flag.

• To improve visibility into the investigation progress, we introduced an Investigation Status matrix in the Worspace manual review interface and the new Investigation Status field in assignments. The collapsible Assignment status customization configuration component allows you to customize status labels when configuring AMM variations.

  The Investigation Status field is populated automatically based on the configured Investigation Status matrix for the corresponding Business Process language. The investigation status is also visible in API responses.

• To provide compliance-ready documentation on AMM investigations and reduce associated manual effort, we enabled the automatic generation of investigation status comments in the Close Investigation popup during manual review in Workspace. When an investigation is closed, Evan automatically determines the final investigation status based on article dispositions and inserts a predefined comment. The comment is generated in English or Spanish, depending on the selected Business Process language.

• The new Generate entity ID automatically based on input fields if it's empty? setting has been added on the Input configuration screen. The feature enables you to streamline decision reapplication by eliminating the need for manual input of the entity ID.

• To improve Evan's stability and performance for high-volume operation, we have enhanced the AI Agent with batch data purging. Now, the Data Purge BP can remove large datasets, for example, over 260,000 records, from Data Stores without OutOfMemory errors.

• To give users control over how input data and downloaded content are prioritized during article creation, we have introduced the Content Source Priority setting in the AMM configuration interface. The setting improves transparency, flexibility, and consistency in how content fields (title, summary, content) are processed and merged.

  In connection with the introduction of the Content Source Priority setting, the translation process has also been revised to correctly handle cases where the setting value is Combine Input and Downloaded Content. When the mode is active, the translation step handles the combined content parts separately to ensure accurate translation and proper language detection.

• You can now tag articles during manual review in Workspace so that, subsequently, the data can be used to retrain the machine learning (ML) model automatically. The new capability enables continuous improvement of the ML model through automated retraining, leading to higher accuracy and reduced manual effort over time.

• To enable more precise entity profiling and support advanced analytics, we have added the new gender field in the AMM input data.

• Evan's ML model now supports the focalityScore and matchedEntitiesfields fields, enabling more accurate entity matching and richer contextual insights for improved decision-making and compliance.

Improvements

• The Core Business Process has been refactored to improve maintainability and ensure a more logical process flow. Among the multiple issues we corrected as part of the refactoring, the major ones are moving the steps specific to batch processing to a separate flow and changing the position of the final output generation step to a more appropriate one.

• The File Ingestion Business Process no longer invokes the core AMM logic. Instead, the BP has been updated to prepare the necessary input data and then trigger the new Batch Processing BP asynchronously. The change allows for the unification of the AMM core processing flows, eliminates code duplication, and aligns ingestion paths.

• The Ad hoc Investigation Business Process no longer invokes the core AMM logic and no longer uses synchronous steps to poll for completion. Instead, the BP has been updated to prepare the input data and trigger the new Batch Processing BP asynchronously. The improvement allows for the unification of the core AMM processing flows and eliminates the need for internal waiting steps.

• To improve assignment tracking and enhance user experience with manual review, a new status column has been added in the assignments table. It is intended to let users differentiate between newly created assignments and those that have already been opened and saved as drafts. Three values are supported: New to label unopened assignments, Draft for open but incomplete ones, and {TBC} for reopened investigations.

• The investigation status assignment logic was updated to ensure analysts follow the correct review workflow, reducing errors and improving compliance by enforcing appropriate status options at each review stage. Previously, when the Restrict the analyst from closing an investigation with True Positive status on the initial review? setting was enabled, the True Match options were greyed out during the first investigation round. With this version, we have modified the logic so that, during the second round, the Escalated (Needs Investigation) options are greyed out and the only available options are Excluded (False Positive) or True Match (True Positive).

• To improve the investigation accuracy and alignment with real-life flows, we have redesigned the article disposition logic. Previously, Evan decided whether a disposition was in the first or second stage based on whether the investigation was opened for the first or second time. In this version, instead of relying on the investigation order, the AI Agent determines the disposition stage based on the user group to which the task is assigned.

• The input and output Data Transfer Objects (DTO) are now extracted to a separate library, which simplifies integrations with AMM and promotes modularity, faster development, and easier maintenance.

• To help you better organize task management, we have introduced customizable assignment titles. You can now customize them using a variation name, a custom name, or a default name.

• To make the manual review process more transparent, duplicate articles are now enumerated.

• Incorporating the updated Trafilatura article parser enhances content extraction accuracy and reliability, ensuring better data quality for downstream processing and analysis.

• The following changes were introduced to the final report content and layout to enhance its clarity and completeness:

  • Articles are now visually separated for better readability and easier content review.

  • Excluded articles are now visible in the report as well, providing full transparency and supporting comprehensive analysis.

• In manual review assignments, the entity type is now shown as an icon instead of as a separate field, which improves visual clarity and speeds up manual review.

• The ML model was improved to ensure more reliable performance and correct processing of several corner cases.

Bug fixes

• Eliminated the issue that caused parsing failures for downloaded articles.

• Corrected webhook configuration errors to appear in a more user-friendly format.

• Fixed the issue causing the blocked_url field in the amm_content_relevance_feedback Data Store to be populated incorrectly when the Allow users to add websites to ignore list? setting is disabled. Now, when you submit article feedback, the field remains empty as per the disabled setting.

• Resolved the problem causing the Close investigation dialog to be completely disabled when the Restricts the analyst from closing an investigation with True Positive status on the initial review setting is enabled. Now, you can select False Positive or True Positive options in the dialog.

• Eliminated the ML execution failure during document processing that was caused by a NoneType operand used in a subtraction operation.

• Resolved the issue causing AMM to incorrectly recognize foreign-language articles as English.

• Fixed the incorrect operation of the ArticleContentValidator.validateArticleEmptiness validator when it checks whether an article is empty. Now, it not only evaluates whether the input string is empty but also examines the actual HTML content. As a result, the content like <html><body></body></html> is correctly marked as empty.

• Eliminated the issue with the incomplete deletion of disposition comments after clearing the shorthand dropdowns in the Summary page, Article review page, or Close investigation popup.

• Fixed the inconsistent cursor behavior across the article navigation, investigation toolbar, and article sections to prevent it from appearing in non-editable or non-interactive areas.

• Eliminated the AMM Core BP failure at the analytics step with disabled report generation.