Case Match form
|
|
If this is a pre-Pega 7 Platform case match rule, the Retrieval tab appears. Complete this Evaluation tab — after you complete the Retrieval tab — to specify the criteria by which the system evaluates and scores the list of cases returned by the content activity.
Specify conditions that must match, or evaluate to True, and create weighted match conditions. When a case meets all of the Must Match conditions, AND the threshold for the sum of weighted conditions, it meets the criteria for being a potentially duplicate case, and is displayed to the end user at run-time.
As a best practice, edit the case match rule directly from Case Designer. See: Tracking duplicate cases.
Field |
Description |
| Case Matching Type |
By default, this field is read only and set to Seek Cases. At run time, all cases with a sum of weighted conditions that is equal to or higher than the value that you define are returned. For case match rules that were created prior to version 7 of the Pega 7 Platform, you can set this field to Seek First Case to return the first case that is found with a sum of weighted conditions that is equal to or higher than the value that you define. |
| Must Match Conditions |
Specify conditions that must evaluate to True for the case to be considered a duplicate. This property-based search compares property values found in the database to property values at run-time in the current case. Use the Add button to include further conditions. It is highly recommended that you enter at least one match condition to limit the number of cases that are reported as potential duplicates. |
| Potential Duplicates | Use the SmartPrompt to select a database property value to evaluate against a property on the current case. |
| Relationship | Use the drop-down menu to specify the comparison operation to use between the database property the property in the current case. |
| Current Case | Use the SmartPrompt or enter a property value in the current case to evaluate against the database property entered in the Potential Duplicates field. |
| Show Filter Logic |
Allows configuration of logic performed on the returned list of potential duplicate cases. Click to hide logic. Enter the Boolean logic operations performed on the array that will compute to a True or False result at runtime. You can use and, or, and not in the statement. You can use parentheses to control the order of evaluation. For example, if the table contains four labels A, B, C, and D, you can enter: (A and B) or (C and not D) When you save the rule, if the form contains only one test row, the system inserts the label for that test row here. If you have more than one row, the system defaults to requiring all rows to be true. If that's not what you want, revise the statement and save again. |
| Weighted Match Conditions |
Enter a value between 1-100 that corresponds to the minimum required sum of all weighted conditions in order for the case to be considered a potential duplicate. When a case meets all of the Must Match conditions, AND the threshold for the sum of weighted conditions, it meets the criteria for being a potentially duplicate case, and is displayed to the end user at run-time. Use "Primary" when referencing the current case, i.e. Primary.FirstName. |
| Weight |
Enter a value between 1 and 100 to add to the total weight of the case if the condition specified in the row is true. |
| Condition |
Enter a match condition using properties and values, as appropriate for the function you select. You can also build a function to include conditions such as: "[date] is within [num] days of the current time". |