Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Controlling the order of circumstance definitions

Updated on November 15, 2021

Provide relevant processing in scenarios when multiple conditions evaluate to true, to ensure that users of your application interact with the intended data and application behavior. By defining the priority of circumstance definitions, you determine how your application behaves when more than one definition meets specified conditions.

Consider a situation in which a circumstance template includes a property that holds a loan amount. Two circumstance definitions correspond with the template; one definition that evaluates the property against values greater than 4,000, and a second definition that evaluates a property against values greater than 7,000. A customer creates a loan request for 10,000. Because both circumstance definitions evaluate to true, you can select which definition you want your application to use.
Before you begin: Define a circumstance template that stores properties and at least two circumstance definitions that store values to evaluate against the template. For more information, see Creating a circumstance template and Creating a circumstance definition.
  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Technical category and click Circumstance Template.
  3. In the list of circumstance templates instances, click the template that you want to open.
  4. Click the Definitions tab.
    Result: The All Definitions section displays all circumstance definitions that correspond to the open circumstance template.
  5. In the Priority Definitions section, in the field in row 1, enter the circumstance definition that you want your application to run first.
  6. To add more circumstance definitions, click Add a row, and then in the row that appears, enter the definition that you want your application to run next.
    Tip: You can also drag a field to a different position in the list to change its run-time priority.
  7. To check the correctness of your circumstance definitions, on the toolbar, click Show Conflicts.
    Result: A read-only decision table opens in a separate window that displays all the definition values for all the circumstance definition rules in the specified order. A warning icon appears next to the rows of the table that are unreachable. A warning message also appears when you attempt to save a form that contains conflicts. Even though the tables might not have any conflicts individually, conflicts might generate when the system assembles the definitions as a single table at run time.
  8. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us