The Run toolbar action opens the Run Rule window for the currently displayed rule. You provide test data and then Pega 7 runs the rule and displays the results. If the results are not what you expected, modify the rule and test it again.
The appearance of the Run Rule window varies across rule types, so how you run a rule varies by its type. In general, you complete the following kinds of tasks:
The Run Rule feature uses rule resolution when running the rule. If you click the Run button but a higher version exists of the rule that you currently have open, Pega 7 displays a status message stating it will run the higher version. Accordingly, to test a circumstanced or time-qualified rule, ensure that the circumstances are correct for the rule. Otherwise, the base (unqualified) rule runs instead of the one you intend to test.
After running a rule, you can open the Clipboard tool and examine the output as it appears on the resulting clipboard pages. The Run Rule operation creates the following pages:
RuleToRun
— The clipboard representation of the rule that you tested.runRulePage
— Holds the output from the rule.temp_ pages
— Pages created or copied by the Run Rule feature when it ran the rule. The names of these pages begin with the literal temp_.pySimulationDataPage
— For service rules, a page of the helper class Data-Admin-IS-ClientSimulation. Contains information about the simulated request and response.When you click the Run button for a list view or summary view rule, the Run Rule window does not appear. Instead, Pega 7 runs the report and displays the results.
Before testing service rules, determine how you will provide the sample data for the service to process. For information, see the PDN document Testing Services and Connectors.
Select topics in the following list for information about how to unit test rules of specific types: