Release notes
Version 3.3.1
- Release date: May 1, 2025
- Compatible platform versions: Work.AI 10.2.8+
The release provides compatibility with RHEL 7.9, streamlines rule management, and improves reporting and analytics capabilities.
Tara now fully supports RHEL 7.9, with previous Python library issues addressed to provide a smoother installation and runtime experience.
To simplify the processing pipeline, we removed the filtering step from the PSS core Business Process, along with all associated filter processing, utilities, and configuration. You can leverage the same filtering functionality by writing rules in your custom rule file.
The default rule file is updated to reflect customer feedback, ensuring alignment with actual business needs and providing a more tailored configuration out of the box.
The parser functionality is enhanced to bypass execution of model steps when tag content is empty:
The parser now makes an in-place decision for hits with empty tag content, while other hits continue through the standard processing path.
The parser bot contract is updated to reflect changes, and the analytics bot contract now outputs a final message object.
To support auditability and compliance monitoring, we introduced the hash_update_date column in the continuous learning (CLDS) analytics Data Store and CLDS reports.
When
historical-decisions/hash_status_change_file.csvis uploaded, hash_update_date is populated instead of hash_enabled_date. The latter now only records timestamps when a hash is enabled through Tara's real-time processing.The is_auto_disabled column is no longer set but remains present in the pss_clds_hash_analytics_v1 Data Store for backward compatibility.
Unused code and classes related to Fircosoft data processing are removed, reducing maintenance overhead.
To offer improved visibility and more comprehensive analytics for compliance teams, CLDS report enhancements include:
Correct display of the minimum counter value
Updated CLDS template file that now contains an updated alias for alert_operator and a new hash_all_released column
The logic for processing maximum hits is updated to ensure data accuracy:
Validation is moved from the parsing step to the input processing step.
Requests exceeding the maximum number of hits are now rejected and excluded from further processing and HTML reports.
All invalid requests are logged in the request processing table with the
FAILEDstatus.
The NER model is upgraded to v2.2.0, featuring the following changes:
Enhanced predictions for entity types ORG, LOC, and PER, including:
Improved recognition of
"DMCC"and similar legal endings as company suffixesMore accurate location extraction in case of repetitions, such as
"Tunis, Tunis, TU, Tunisia"Better handling of complex personal names, such as
"Ahmed Fuad Bin Sheikh"or"Ricardo S. De La Cuba"
Resolved the issue where the NER model was stuck when encountering excessively long tokens in input.
The AI Agent configuration is upgraded with the decision model v5.1.1 and Name Matcher v1.1.1, delivering the following improvements:
Introduced more robust handling of middle names with parameter-based control over individual name comparison behavior.
Fixed the issue in the base similarity calculation that caused incorrect comparisons for Arabic names starting with
"al-".Disabled application of the rare token overlap logic for concatenated names with ambiguous stopwords.
Updated the logic for handling
RAREorSCREENEDtoken overlaps: name matches are now returned if two or more tokens match, regardless of their frequency.Improved preprocessing for organization names: the text is now removed after legal forms if found at the end of a name.
Added support for common word variations, such as
"NATL == NATIONS == NATIONAL".Removed the functionality related to using the external Babel name matcher.
Updated the Python environment to
python3.11.5-pss-v4and replaced the C++ Double Metaphone library with a pure Python alternative to ensure compatibility with RHEL 7.9.
Bug fixes:
Resolved the issue when invalid data could be saved in the threshold fields on the Model tab. Field validation now correctly prevents invalid entries, ensuring data integrity.
Resolved the quality control (QC) report issues with wrong values in the hit_name_matcher_score and hit_type_confidence_score columns to provide more accurate quality control metrics.
Fixed issues in CLDS and QC reports that caused failures when running against requests generated with Tara versions prior to v3.3.0.
Fixed the hash mismatch issue caused by tag content ending with a backslash before a newline character. Newline conversion is moved from the generic message converter to the SWIFT message parser to ensure consistent hash calculation.