Creating a circumstance definition
You can create a circumstance definition to evaluate properties in a circumstance template.
- Check whether at least one circumstance template is defined in your application.
-
Make sure that the PegaRULES database supports access by developers to create circumstance definitions. For more information, see Database Name form — Completing the Database tab.
-
Ensure that your changes do not exceed column thresholds. See the Pega Community article Troubleshooting: "Exceeds the maximum number of columns" when creating a Circumstance Definition rule.
- In the header of Dev Studio, click .
-
On the Create Circumstance Definition form, enter values in the
fields to define the context of the flow.
- In the Label field, enter text that describes the purpose of the circumstance definition.
- Optional: To change the default identifier for the circumstance definition, click Edit, and then provide a unique value in the Identifier field.
- In the Template Name field, press the Down Arrow key, and then select the circumstance template that your circumstance definition implements.
- Select the Context.
- In the Apply to field, press the Down Arrow key and select the class that defines the scope of the circumstance definition.
- In the Add to ruleset field, select the name and version of a ruleset that stores the circumstance definition.
- Click Create and open.
-
On the Definition tab, add conditions to the Apply
this definition table that evaluate the properties from the circumstance
template.
-
Click each column heading to choose which operations it supports.
To reset the operations for a column, clear the Use Range check box, and then select = from the Use Operator list.
-
For columns that require a single operation, select an operator from the Use Operator list.
-
For columns that require a range, select the Use Range check box, and then choose operators from the Starting Range and End Range lists.
-
- Click the Insert Row After icon.
- For each column in the row, enter a property or an expression that evaluates properties.
- Drag rows to change the order in which your application evaluates them at run time.As a best practice, list the more likely outcomes in rows at the top of the table.
-
Click each column heading to choose which operations it supports.
- Click Show conflicts to test the completeness or consistency of your conditions.
- Click Save.