Version: 2.4.2

Release notes

Version 2.4.2

About Release

New features

Updated NSS REST API contracts, enabling you to send the following parameters when an NSS execution is triggered via REST API:
- Additional customer and hit entity data for sending information to be displayed in Additional Information (extdata) fields in manual review assignments.
- Customer and hit entity category.
- Detailed names, such as the first, middle, and last names of customers and hit entities.
Implemented a configuration map for sending JSON code as part of REST requests to override existing manual assignment settings in Workspace. These settings include task assignee, priority, title, or forcing requests to go to manual review or to be skipped regardless of the skill's initial configuration.
Implemented REST request status tracking for NSS variations executed via REST API with the Human-in-the-loop capability. To enable the tracking, a dedicated Data Store is updated whenever a new Manual Task is created or saved or a manual review request is completed.
Refined the NSS classification model's decision-making process by introducing additional Strong match and Strong mismatch thresholds for the Date and Name comparison factors. Thus, the model now provides four outcomes: Strong match, Weak mismatch, Strong mismatch, Not available.

Improvements

Simplified the narrative language and updated it to support the more granular model factor decisions.

Bug fixes

Fixed the issue with an invalid customer ID sent from NSS Billing API.
Resolved the issue with incorrect name matching when comparing words with dots by improving the pre-processing of names.
Fixed the problem with UI configuration steps becoming non-clickable.
Updated billing SKUs.