More about Decision Tables
|
|
If you have in advance a Microsoft Excel spreadsheet in XLS file format that contains useful starting information for a decision table, you can incorporate (or "harvest") the XLS file and the information it contains directly into the decision table.
This feature lets people with no access to the Pega Platform record their decision rules using a familiar software program.
In an activity, to evaluate a decision table and derive a value, your application can:
In an activity, call the method Property-Map-DecisionTable method. As parameters, enter the target property name and the name of the decision table.
In an activity, call the standard function named DecisionTable.ObtainValue to evaluate a decision table. Use the syntax:
Lib(Pega-RULES:DecisionTable).ObtainValue(this, myStepPage, "decisiontablename")
The Pega Platform does not limit the number of rows in a decision table. However, as a best practice to avoid slow performance when updating the form and also avoid the Java 64KB code maximum, limit your decision tables to no more than 300 to 500 rows.
The standard activity named @baseclass.DecisionTableLookup also evaluates a decision table. (This approach is deprecated.)
Click Actions > View Java to view the generated Java of a rule. You can use the Java code to debug your application or to examine how rules are implemented.
When a Declare Expression rule has Result of decision table for the Set Property To field, special processing occurs at runtime when a property referenced in the decision table is not present on the clipboard. Ordinarily such decision rules fail with an error message; in this case the Otherwise value is returned instead. For details, see PDN article Troubleshooting: Declarative Expression does not execute when a decision rule provides no return value.
Despite the class name, the Rule-Declare-DecisionTable rule type does not produce forward or backward chaining. Technically, it is not a declarative rule type.