Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Duplicate search

Duplicate cases

A user may create a case which has the same data values as another case in the system. For instance, two purchase requests may have the same request date and list of items, or the same customer name. In this scenario, where a specific combination of data values or unique identifiers match, the new case may be a duplicate.

For example, a health care services application handles requests to authorize insurance coverage for surgical procedures. A user enters a request for a specific surgeon to replace a patient’s knee joint on March 18. Two days later, the patient health care provider discovers that the surgeon is not available on the specified date. The provider submits a new request for the same patient and type of surgery, with a date of February 26. As the patient and type of surgery match an existing case it’s likely the new request is a duplicate. To avoid double-booking the surgical procedure, if the user determines the new case is a duplicate it should be resolved and the procedure date for the original case modified to February 26.

Search duplicate cases step

Pega Platform™ provides the search duplicate cases process to help users identify and resolve duplicate cases. This process is implemented in the case life cycle as a Search duplicate cases step. When a case enters the step, the system uses basic conditions and weighted conditions to compare specific property values with cases already present in the system.

In the following image, click the + icons to read how Pega Platform™ processes the Search duplicate cases step.

Customizations to the search duplicate step behavior

When a user decides the current case is a duplicate it is resolved (status Resolved-Duplicate) and processing of the case terminates.  Processing can be customized to enable the user to open the original case to make any necessary updates.

Example

In the health care services application example, assume that the patient date of birth is the basic condition. The surgeon name, surgical type, procedure, and procedure date are the weighted conditions with a value of 25 each and a threshold of 50. The system displays the case entered on February 26th as a duplicate because the date of birth, surgeon name, surgical type, and procedure match the values in the original case, and the total weighted condition value is 75, exceeding the matching threshold of 50. The user decides that the second request is a duplicate and resolves the case as Resolved-Duplicate. The user then continues with the initial case and updates the procedure date.

In the following image, click the + icon to view the duplicate case analysis.

Check your knowledge with the following interaction.


If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice