More about Case Match rules
|
|
A case match rule returns the results to the pxResults property of a Code-Pega-List page on the clipboard. The results can be examined and then displayed, perhaps in a report, or used in an executing application. The results page also includes the following properties:
On each embedded page, the pxMatchScore property holds the score of the case.
Complete two basic steps to specify and use a case match rule.
First, write two activities that interact with the case match rule you create; a content activity to select cases, and a calling activity to evaluate the case match rule. Then complete the Case Match rule form, which references the content activity.
The high-level steps are:
Don't forget to anticipate and handle in your application the possibility that no cases meet the retrieval criteria, or that none of the retrieved cases meet the cutoff score.
A case match rule can combine multiple factors into a single numeric score. The full power of PRPC expressions and functions can compute factors that add into the score. For example, when a customer (or other party) identifier isn't known but the ZIP code is available, a case match rule can retrieve all the customers in that ZIP code and score those who:
and so on.
When you save a case match rule, the system converts the rule to pro forma Java source code. As a learning or debugging aid, you can review this Java code.
C-1665Click the Show Java toolbar button () to see the system-generated Java code that implements the case match rule. The window presents a read-only preview of the Java that implements this rule instance. This Java code is not identical to the Java that executes at runtime, which includes Java code inlined from other rule instances and reflects rules in the requestor's RuleSet list.