Release notes

Version 3.3.0

About Release

• Release date: April 4, 2025
• Compatible platform versions: Work.AI 10.2.8+

The Tara v3.3.0 release extends the address verification capabilities and introduces a way to set custom disposition rules. Mind that the release is compatible with models of v5.0.2 or higher versions, while older models will no longer work with the solution.

• Tara now supports multiple locations for screened and sanction data, entailing the following changes:

  • Tara's input contracts were updated, and its REST API can now handle multiple addresses in both screened and sanctioned data for each alert. For the purpose, two new fields were introduced: screenedData.locations and sanctionData.locations. The PSS Business Process, however, remains backward compatible, and older inputs will not fail.

  • Geocoder now searches all screened addresses and saves multiple search results. The isLocationValid parameter has been split into isCountryValid to define whether the found country can be used for location match or mismatch and isAddressValid to confirm whether a street address is a real postal address for a building.

  • The v5.0.2 decision model now supports the mentioned new location fields and geocoder search results. The v5.0.2 model is backward compatible with Business Processes prior to Tara v3.3.0 and works with the older Geocoder version. However, the v5.0.1 and earlier models cannot recognize the new location fields added in the PSS Business Process for Tara v.3.3.0.

  • The rule mapping was updated to reflect supported multiple locations, while unused fields were removed.

• The new address comparison capability allows you to verify if the screened and sanctioned addresses match using one of the address matchers: Geocoder API, in-house address verification API, or literal string comparison. You can configure the capability and choose an address matcher on the Model step in Tara's configuration user interface.

  To support the address comparison feature, the following updates were made to Tara's rule configuration: the locationMatch object was renamed into countryMatch, and the new addressMatch object was added.

• To allow you to define custom disposition rules, we provided a possibility to set custom attributes in Tara's input. For that, new customAttributes maps were added to JSON requests and made available in the rules.

Bug fixes:

• Fixed the issue with the last token of addresses incorrectly identified as an ISO country code (for instance, in the 123 AMSTERDAM 1077 BL address string, the correct country is NL, not BL).