Skip to main content

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

Circumstance definitions

Updated on August 16, 2022

A circumstance is an optional qualification available for supported rule types and is built upon the base rule.

Using circumstances in your application allows you to easily support a variety of use cases. For example, you might want a different data transform to execute depending on a customer's geographic location (for example, when .StateCode = "MA"). Instead of maintaining the logic for all cases in one large rule, start with a base rule and extend (or specialize) it as needed. At runtime, the Pega Platform automatically selects the correct version to execute as part of its rule resolution process.

The following figure illustrates example logic for evaluating geographic location and other properties in a case.

Definition Table

You can create a circumstance of a base rule by a single value property, template (multiple properties), or date.

Note: If you have upgraded to Pega 7.2, all date circumstance rules will be upgraded automatically and can be modified, except the rules circumstanced by date range and as-of date. These rules continue to run without issues but must be manually upgraded to use the new date circumstancing options.

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