Decision rules are used for configuring decision data flows for actions such as loading customer data, executing a decision strategy, and writing results into interaction history. Types of decision rules include decision tables, decision trees, when rules, map values, collections, and declare expressions.

• Unit testing a decision table

  You can test a decision table individually, before testing it in the context of the application that you are developing. Additionally, you can convert the test run to a Pega unit test case.

• Unit testing a decision tree

  You can use the Run Rule feature to test a decision tree individually before testing it in the context of the application that you are developing.

• Unit testing a when rule

  You can test a when rule individually before testing it in the context of the application that you are developing. Additionally, you can convert the test into a Pega unit test case to validate application data by comparing expected property values to the actual values that are returned by the test.

• Unit testing a map value

  You can test a map value individually, before testing it in the context of the application that you are developing. Additionally, you can convert the test run to a Pega unit test case.

• Unit testing a collection

  You can test a collection individually, before testing it in the context of the application that you are developing.

• Unit testing a declare expression

  You can test a declare expression individually, before testing it in the context of the application that you are developing. Additionally, you can convert the test run to a Pega unit test case.

• Unit testing event strategies

  Evaluate event strategy logic by testing it against sample events. This option facilitates event strategy design and enables troubleshooting potential issues.

• Unit testing individual rules