Release notes
Version 2.2.0
- Release date: May 10, 2026
- Compatible platform version: Work.AI 10.2.9+
The Isaac v2.2.0 release delivers new capabilities for counterparty identification and targeted investigation, account‑level risk assessment support, SMB file ingestion, and performance improvements for larger alerts.
New features
The configuration interface now has a section with counterparty selection filters, so you can control which counterparties to include in transaction investigations. You can set Isaac to review all alerted counterparties, those from transaction lists, those associated with high-risk jurisdictions and round-dollar transactions, or a selection of counterparties per type. This feature helps you tailor the investigation scope to your exact needs and reduce unnecessary alerts, improving the investigation efficiency and decision quality.
Isaac now allows counterparty names to be automatically overwritten from transaction descriptions, making it easier to identify the right parties. The overwriting mechanism helps you extract more accurate and relevant names from your transaction data. As a result, you get clearer context, less confusion, and faster investigations.
A new model for account-level analysis is now available. Choose the Model ID in the configuration interface, and it will assess risks at the entity level and get you a summary status, comments, and detailed results. By surfacing a holistic view of account behavior and risk drivers, the feature helps you spot risks more accurately and make decisions faster with less manual work.
Isaac now supports file ingestion from Server Message Block (SMB) shares, enabling seamless data intake from Windows file shares and Linux Samba shares. Using the new capability, you can integrate existing file‑based workflows directly into Isaac without additional data transfer steps. This makes the workflow setup easier and allows you to leverage your current file systems for reliable data ingestion.
Improvements
- Isaac’s heap space has been increased to handle larger and more complex alerts. The change improves the solution's stability and scalability, so you can process more data without performance degradation.