Circumstance
Template form
|
Use the Definitions tab to display all the circumstance definition rules that are associated (by their Applies To class and Template Name keys) with this circumstance template rule. You can specify the priority of the circumstance definitions used during runtime and rule resolution.
Field |
Description |
All Definitions |
The fields in this section are read-only. |
Definition |
The name (Purpose key) for this circumstance definition rule. |
Class |
The class to which this rule applies. |
RuleSet |
The RuleSet where this rule is saved. |
Version |
The RuleSet version where this rule is saved. |
Priority Definitions | |
Priority Definitions |
Optional. Select a circumstance definition rule from the list if you want to change the default processing order displayed in the All Definitions field. For example, if the default order is DefA, DefB, and DefC, you can create an array specifying the processing order as DefC, DefA, and DefB. For more information, see the Pega Developer Network article PRKB-25272 How multivariate circumstancing works. |
Click the Show Conflicts button to test the completeness or consistency of the tables among the circumstance definition rules associated with one template rule. Even though the member tables have no conflicts individually, they may appear when assembled as a single table during runtime. When you click the button, a read-only decision table opens in a separate window that displays all the definition values for all the circumstance definition rules in the order that they would be assembled.
Any rows of the table that are unreachable are marked with a warning icon ( ). A warning message also appears when you attempt to save a form that contains conflicts. Resolve them in the appropriate circumstance definition rule table and save the form.