Duplicate search functionality in Smart Investigate

From PegaWiki
Duplicate search configuration / This is the approved revision of this page, as well as being the most recent.
Jump to navigation Jump to search

Duplicate search functionality in Smart Investigate

Description Save time by identifying duplicate cases in your application using the duplicate search functionality.
Version as of 8.5
Application Pega Smart Investigate for Payments
Capability/Industry Area Financial Services

Duplicate search functionality in Smart Investigate

The duplicate search functionality saves time by identifying potential duplicate cases in your application and ensuring that each case represents a unique request. Potential duplicate cases match a set of required, weighted conditions.

Smart Investigate uses the scoring definition rule DuplicateScore to set the criteria for identifying potential duplicates.

Defining the conditions for duplicate search

The following example includes 18 conditions for exact matches on case data, including transaction reference, branch, base inquiry amount, and so on. A weight is assigned for each condition.

This scoring definition rule is called from utility SISearchDuplicates, which includes Threshold as an input parameter. Cases with a cumulative weight score above the defined threshold are considered potential duplicates.


Configuring duplicate search for your implementation

Smart Investigate includes default settings for search parameters, which are used to identify cases as duplicates. Review the out-of-the box search parameters and update FetchScoreDetails as business needs require.


Retrieving cases to compare against scoring criteria

Retrieving and comparing cases impacts application performance; therefore, a report definition FetchScoreDetails identifies cases that match initial basic criteria. The filter used is similar to the following example, where amount and transaction dates are compared.


Processing search results

An application is configured to work in straight-through processing (STP) mode if a single match for the defined search criteria is found. If duplicate search results contain more than one case match, users are prompted to manually review the results and take one of the following actions.

  • No Action – Allows you to manually override the system search criteria and treat the case as unique (i.e., not a duplicate).
  • Not Related – Indicates the potential match is not a duplicate and not related to the case.
  • Link – Adds a hyperlink in the related items section of both cases but does not flag the case as a duplicate. 
  • Duplicate – Flags the item as a duplicate and adds a hyperlink labelled duplicate in the related items section of both cases and resolves the case as a duplicate.