Press "Enter" to skip to content

Duplicate search in case management

36

Introduction

In this post we will see in detail about duplicate search in case management.

I used the claim cycle as example.

Please visit the below links to know more in detail

Case management – Introduction

Case management – configuration settings in stages, processes and steps

Letโ€™s take the insurance claim example.

  • I have a business requirement like, the same insurance policy cannot have more than one claim.This is an obvious requirement ๐Ÿ™‚

Now think how can we determine a case as a duplicate?

  • We have to check if a case is already present in the system with the same attributes.

In Pega, we refer properties as attributes.

So we come to a conclusion, that properties can be used to search and check if a duplicate case is already available in the system.

  • Now there comes certain situation, where some properties may not be available ( not mandatory), then how we can identify the duplicate?

We can use some group of properties and use some weighted calculation to determine the duplicate.

For example: XYZ is an Insurance company that provides policies to customers. They face certain situation that they receive same request multiple times and end up creating duplicate insurance policy cases for customers. To avoid this, they designed some duplicate search requirement.

Below is their requirement: Same customer cannot multiple policies in same insurance type, say Insurance type = home.

Their business say, Use the 4 customer attributes โ€“ Name, date of birth, Phone number & address.

So if any existing case that matches Insurance type and 3 out of 4 customer attributes, then the existing case can be considered duplicate

How to implement such scenario??

Case match rule can be used to identify the duplicate case

What is a case match rule?

  • Case match rule can be used to fetch the duplicate cases present matching the criteria specified.
  • It is kind of more or less like a Obj-Browse.

Duplicate Search smart shape uses case match rule to identify the duplicate case.

  • First let see how to use a case match rule

For testing purpose, create a new case match rule

Records -> Decision -> Case match rule

The rule contains a single main tab.

Note: Prior to Pega 7, you get a retrieval tab where you can specify a activity to fetch the duplicate.

Case Matching type โ€“ It was originally designed as dropdown with two values

a) Seek cases โ€“ Fetches all the duplicate cases that match the conditions specified

b) Seek first case โ€“ fetch only the first case ( this is deprecated in pega 7)

You have two matching conditions block

  • Must match conditions
  • Weighted match condition

Must match condition

Specify the conditions that must evaluate to true for the case to be considered duplicate.

Potential duplicates โ€“ Select the property name.

Relationship โ€“ Specify the relation

  • You can add multiple must match conditions and use filter logic.

Weighted match conditions

  • You can use weighted condition to determine the potential duplicate.
  • I would like to show the picture again.

  • As per the business requirement,ย  out of 4 customer attributes, 3 have to match to identify it as a potential duplicate.
  • Letโ€™s do simple math. We can give 25% as weight for each attribute and overall, it should score 75% (Just like the CSA, CSSA, LSA cut off scores :D)

  • You can specify weight for each condition and the overall weight should be greater than or equal to the Pass mark ๐Ÿ™‚

Note: ย Weighted condition is always mandatory, where must match condition is optional

Letโ€™s configure this from case designer.

As usual, case designer accepts some input and creates the Case match at the back end.

How to configure duplicate search from case designer?

Step 1: Open the case designer and go to Settings tab.

Step 2: Click on track duplicates.

Step 3: Scroll up and configure the weighted conditions and must match conditions.

  • In this claims case, I can have the Insurance ID as the only required property to identify if there is already a claim is requested for the same insurance.
  • Since weighted condition is mandatory, I am treating weighted as must match ( tweaking!)
  • Uncheck must match condition.

Now letโ€™s see the case match rule created at the back end. pyDefaultCaseMatch

  • Now we have configure the duplicate search business logic with the Claims case
  • Next step is to decide where to invoke this duplicate search!

Ideally it should follow the step where we collect the Claim request details

Step 1: Go to case designer โ€“ workflow tab

Click add new step in stage 1. Select more.

Step 2: from utilities select โ€˜Duplicate searchโ€™.

Step 3: Drag the step to the second place after collect information.

Step 4: Save the case and check the โ€˜ClaimRequestโ€™ flow.

You can see โ€˜Duplicate search casesโ€™ shape is added automatically.

Now letโ€™s test the duplicate search

Step 1: create a new case C-13 and enter Insurance ID as โ€œA-1234โ€

Step 2: now create another case C-14 providing same Insurance ID. ( 2 people are raising the claim for same Insurance)

Step 3: click submit and proceed.

Now you will get an assignment listing all the duplicate cases.

  • You select and mark the current case C-14 as duplicate.
  • You also have an option to continue without resolving duplicate case

Step 4: Select resolve as duplicate.

Technically, pega uses the flow pyDuplicateSearchCases to search and display the duplicate cases.

This flow is in available state and can be extended to your application class!

We are at the end of duplicate search functionality post!

Hope you liked it.

More frequent posts on case management are coming!!! ๐Ÿ™‚

 

  1. Santhosh Santhosh

    Firstly thank you prem.I really appreciate you prem ,I am beginner in Pega this post is really very nice.I am expecting more Posts on case management.

    • Premkumar G Premkumar G

      You are most welcome, Santhosh. ๐Ÿ™‚
      Thank you so much for your appreciation, Santhosh. ๐Ÿ™‚
      Happy to hear that you are finding my blog useful. Yeah I’ll post more posts. Stay tuned. ๐Ÿ™‚

  2. sarath babu sarath babu

    Thank you very useful post. I love this blog for your frequent updates on Pega Knowledge.

    • Premkumar G Premkumar G

      You are welcome, Sarath. ๐Ÿ™‚
      Thank you so much, Sarath. ๐Ÿ™‚

  3. shweta bhatia shweta bhatia

    If Weighted Condition is mandatory than Insurancetype should have been a mandatory condition , therefore why is it kept in must match?

    If the must match is false and weighted conditions is true, we don’t want to proceed. right?

  4. PrasuR PrasuR

    Hi Prem

    Thank you so much for sharing your knowledge with free of cost and putting your full of efforts. I think thx is very small word for what you are doing.

    Can you please share on how to work on covers and folders in depth.

    • Premkumar G Premkumar G

      Hi Prasu,

      You are most welcome and I thank you very much for your heartfelt appreciation. I’m feeling glad to read your comment. ๐Ÿ™‚

      Yeah, I’ll post about it soon. Stay tuned. ๐Ÿ™‚

  5. PrasuR PrasuR

    Hi Prem,

    Thank you so much for posting this very useful topic. Can you please post covers and folders

    • Premkumar G Premkumar G

      Hi Prasu,

      You are most welcome. I’ll post about covers and folders soon. Stay tuned. ๐Ÿ™‚

  6. Raj Raj

    Thank you very much Prem. All your posts are really good.We all wish you reach great heights in you career and life from pega community.Please do continue this great work.
    Hope I will meet you one day and tell you how this blog is helping pega community.

    • Premkumar G Premkumar G

      First of all, thank you so very much for your well-wishes and appreciation, Raj. ๐Ÿ˜€
      Comments like these motivate me to work hard more. Thank you so much for your motivating comments. ๐Ÿ™‚
      I’ll definitely keep on posting new stuffs. Stay tuned. ๐Ÿ™‚
      You are most welcome, Raj and I will be glad to meet you too. ๐Ÿ˜€
      I am eager to hear what you have got to say. ๐Ÿ™‚

  7. Santhosh Santhosh

    Good one. Please post on User Interface topics, Repeating grids, Repeating Layouts??

    • Premkumar G Premkumar G

      Thank you, Santhosh. ๐Ÿ™‚
      Yeah, I’ll post about them as soon as possible. Stay tuned. ๐Ÿ™‚

  8. Mohit Mohit

    you are really doing great work , other people in market are charging 15k for pega tutorials and not even providing that much content. as a beginner in pega it really makes me understand. keep up good work. I wish you all success in your career. if possible please post on Cover and folder , data propagation.

  9. Guptha Guptha

    Hi Bro,

    You are doing an awesome job. Superb explanation with real time illustrations.
    Can you please post, how AQM works in Standard Agents with an live example.

  10. keerthi keerthi

    Thanks! Your posts are really worth reading! I just have a question about this particular post.
    Do we call this Case match rule from somewhere?

  11. Raghu K Raghu K

    Hi Prem,

    Thanks for the post on Case Management. I have learnt something from this post in this blog. Keep go on posting some topics related in this blog. ๐Ÿ™‚

  12. satish satish

    Please share the more exemple of covered and folder in casemanagement

  13. vinod kumar vinod kumar

    Could you please do one example on Repeating grid layout

  14. Madhav Madhav

    Hi Prem Kumar did a wonderful job

    Thank you .

  15. Venkat Venkat

    Highly useful post Prem!!

    I understand that case match rule will get created in the back end when given the required input in the case designer
    But I am little curious to know where we actually using case match rule otherwise

  16. vinod kumar vinod kumar

    Please do one session about repeating grid layout and – user interface

  17. Krishn Krishn

    Thank you so much Prem.
    Your blogs are really helpful.I didnโ€™t find any blog like this.well explained.Really doing great help.

    Please post on file listeners and logs.

  18. ranjeet ranjeet

    Thanks Prem for all post these are really helpful…please share your knowledge on TICKETS also ๐Ÿ™‚

  19. Zohreen Zohreen

    Hi Prem,

    All your posts are really excellent and very easy to understand the most complex topics. All my friends refer your page and have gained knowledge. It has boosted my confidence in many topics with clear ideas with your explanation in a very simple way. Awesome job wish you all success in your life.

  20. Sam Sam

    Awesome Work!!Really helpful! Please do more posts on Case Management.
    Try to create a tab-frequently asked interview questions will be useful to everyone.

  21. lucky lucky

    Good one and excelent

    • Premkumar G Premkumar G

      Thank you, Lucky. ๐Ÿ™‚

  22. Sravya Sravya

    Hi Prem,
    Nice explanation. Able to learn lot of new things from your posts.

    Have a doubt in above post,
    1. if we manually create a casematch rule, where should i refer it inorder the rule to be invoked.
    2. if we are creating defaultcasematch rule by mentioning in settings tab, where will the pyDefaultCaseMatchRule be referred.

    Thanks in Advance. ๐Ÿ™‚

  23. Dibakar Dibakar

    Another great post. Thanks for sharing this. ๐Ÿ™‚

    • Premkumar G Premkumar G

      Thank you so much and you are welcome, Dibakar. ๐Ÿ™‚

  24. vamsikumar neelisetty vamsikumar neelisetty

    HI Prem,

    Appreciation for your effort in this blog.

    I have a question in this topic.

    How can I call my own case match rule instead of using “pyDefaultCaseMatch”?

    I found pyDuplicateSearchcases smart shape is always taking pyDefaultCaseMatch rule to serach the duplicates.

    For eg: I want to call different case match rules in different stages of the flow. How this can be achived?

  25. vamsikumar neelisetty vamsikumar neelisetty

    Question on case match rule

  26. Suneel Reddy Suneel Reddy

    Thank you Prem. Thanks for sharing knowledge.

  27. sagar sagar

    HI Good thanks for the post

  28. sunny sunny

    Thank you prem, this site is simple superb, easy to understand, i appreciate your hard work…

Leave a Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!