Release notes
Version 3.1.0
- Release date: July 2, 2024
- Compatible platform versions: IA Cloud 10.2.7, Work.AI 10.2.8 and 10.2.9
The Tara v3.1.0 release aims at enhancing efficiency, reliability, and overall performance and provides the following capabilities:
Enhancements to the Decision Reapplication process allow for more precise and granular control, enabling partial message resolutions and more detailed analytics tracking. These changes are particularly beneficial for users dealing with complex payment messages and diverse data formats, such as SWIFT and SWIFT_MX.
Model updates focus on improving the Named Entity Recognition (NER) and Decision models, enhancing their ability to accurately identify and process relevant entities. Due to refining preprocessing and post-processing steps and updating algorithms and matchers, the models are more robust and reliable, producing even more accurate results and increasing the solution's overall effectiveness.
The updated ISO20022 parser enables more flexible tag name lookups, ensuring that Tara can seamlessly handle a wider variety of data formats.
In addition to new features, several issues related to country matching, name concatenation, and entity detection have been resolved to ensure a smoother user experience.
New features
Business Processes:
Updated the ISO20022 parser tag name lookup to enable finding ISO tag names regardless of the case used.
Updated the AI Agent configuration > the Decision Reapplication step.
Added the Require tag content match for decision reapplication option (disabled by default) that requires the text of the payment message tag (for example, SWF_4_50K) to match the historical message for a decision to be reapplied.
Added the Decision Level option used to specify the level on which the decision reapplication will be applied—a hit level or a message one (by default, set to Hit Level).
Added a possibility to configure message tags for multiple formats.
Enabled ID-prefix matching.
Updated the hit text logic to use a WLE name if the hit text contains a WLE name.
Removed the redundant Read Settings bot step. All configurations are now read directly from a system-provided configuration JSON object, saving execution time.
Updated the Named Entity Recognition (NER) model to v1.6.13.
Updated the Decision model to v4.1.7.
Decision Reapplication
Applied resolutions to individual hits instead of entire messages, allowing partial resolution of messages by Decision Reapplication.
Added the decision_reapplied column in the Analytics table to record which hits and entire messages are resolved by Decision Reapplication.
Added the support for the SWIFT format.
Added the support for the SWIFT_NPP format.
Added the support for the SWIFT_MX format:
Updated the ISO (XML) parser to better match tag content using the combination of the
tag_nameandhit_textvalues.Updated the type dictionary to group related entity information together (for example, name, address, ID).
Updated rules to treat the Country type the same as Location.
Introduced a solution to multiple hit-text logic. Hits are now split when multiple hit texts are found in the tag content, and each sub-hit is adjudicated separately. Sub-hits are merged back during decision processing. A
NO_DECISIONhit is returned if any sub-hit isNO_DECISION. The change may decrease the automation rate but prevents mistakes due to choosing the wrong entity to compare.
Models
NER model:
- Improved pre- and post-processing.
Decision model:
Added ID prefix matching as an option enabled in Business Process additional parameters.
Enabled check for blacklisted countries in a screened name (for example,
ORGANIZATION "PDVSA CUBA S.A").Updated the name matcher to v0.2.8.
Updated stop word lists.
Modified the algorithm to use the location matcher only if the second name (WLE) type is Location or Default.
Improved name matcher preprocessing for the Organization type.
Bug fixes:
Resolved the issue with a wrong value for the country match if a country name is not set correctly and introduced additional validation to parsed countries.
Resolved the issue with low scores for concatenated names.
In addition to the default Tara name matching algorithm, which finds the best matching token pairs and then aggregates them to the final score, Tara now additionally generates a name pair that treats names as one concatenated token without spaces and calculate the similarity for such pairs as well.
Resolved the issue with finding an incorrect NER entity in the hit text. Updated the multiple-hit logic is updated to avoid splitting hits if an NER entity contains all tokens present in the hit text.
Resolved the issue with overwriting the model's
location.matchvalue and added a check for processed values.