Release notes

Version 3.1.21

About Release

• Release date: November 11, 2024
• Compatible platform versions: IA Cloud 10.2.7, Work.AI 10.2.8 and 10.2.9

The 3.1.21 patch focuses on improving data processing efficiency, streamlining rule management, and strengthening system resilience. The enhancements to Tara's models result in faster, more accurate processing with reduced downtime, ensuring smoother operations and more consistent data-driven decision-making.

• To eliminate redundant processing, we removed unused logic for Additional Data and Account Holder Name from the Business Process workflow. The decision model is also upgraded to version 4.3.8, which omits the usage of Additional and Self-Service data along with Account Holder data.

• The rule management mechanism was enhanced by introducing version control for the custom rule file.

  • The default rule file is now stored in a versioned directory, such as doc-upload/sanctions/{$tara_version}/rules/rules_v1.drl. Modifying the default file is not recommended.

  • You can place a custom rule file in a designated directory for it not to be overwritten during updates. This custom file will take precedence over the default one.

  For more details, see Install and configure | Model and Make decisions.

• The AI Agent configuration is upgraded with the NER model v1.6.17 that addresses the ID recognition issue caused by the ID post-processor’s reliance on specific SWIFT tag names. The updated model enhances the accuracy of digital identity verification and ensures consistent data extraction.

• We reverted a change introduced in Tara v3.1.19 that previously batched historical data queries. While reducing the memory consumption, the batching also led to significantly slower CLDS execution. Instead, we increased the heap memory size from 512 MB to 1024 MB in the configuration YML file to prevent rare out-of-memory exceptions. Additionally, the select query for fetching historical data is updated to load all results in one query, improving execution speed and efficiency.

Bug fixes

• Resolved the 503 error when accessing the default rule file from S3 due to connectivity issues with S3 MinIO. If S3 is temporarily unavailable, the system loads the latest known rule file from cache to ensure uninterrupted access.

• Fixed the issue when the connector failed to return a response in case the input originated from the connector. Now, when Tara receives input from a connector, it searches for JSON input within the connector_request field. The output is then generated in the connector_response column and sent back to the connector.