Skip to main content

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

Finding rules by circumstance

Updated on January 14, 2022

To verify if an existing rule is either a base rule or a circumstance, open it in Dev Studio and inspect the form header. Click the Circumstanced link to see circumstance values or an indication that the rule is a base version. The link does not appear if the existing rule is neither a base nor a circumstanced version.

To see all available circumstances for a given base rule, navigate to the rule in the Application Explorer. Use the expand icon next to the name of the base rule to display each of the circumstanced instances and their values.

Select ConfigureCase ManagementToolsFind Rules Find by Circumstance to create a report comprising single-property and multiple-property circumstance rules. You can filter the report by searching on the following default circumstance properties: U.S. State Codes, Channels, and Customer Level. You can also search for circumstance rules by entering text used in key parts ( Apply to or Identifier ) in the Name Contains field.

For more information on how to report on circumstance rules, or how to add or change the circumstance property columns for the report, see the Pega Community article How to find rules with a specific circumstance.

Use the Data-Circumstance-Duplicates.CircumstanceMultiples.ALL report to identify single circumstance rules that incorrectly use two or more different properties. Such conflicts can arise when rules are imported into a rulesetthat already contains some circumstanced rules. To access this report, select ConfigureApplicationInventoryInventory Reports. Enter Rule as the Category and circumstance as the search text.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us