Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

How to create a rule with a single circumstance property

Updated on September 10, 2021

Summary

After creating a rule, you can define qualifiers (such as circumstances) which may be used to create additional versions of your rule for specific situations.  This article describes how to create a rule with a single property as a qualifier.

 

Suggested Approach

Before You Begin

Before you create a circumstanced rule, create the base rule.   Circumstanced rules require a base rule, which is executed when if none of the circumstanced rules are applicable.   See Understanding circumstances and other rule qualifiers

Creating a Circumstanced Rule

1.  Open the base rule on which you wish to define a circumstanced rule.

2.  Click on Save As to save the rule.  The Save Rule Instance under new key dialog box appears.

3.  If desired, change:

  • the Applies To class name
  • the RuleSet Name
  • the RuleSet Version

Important:  For a valid circumstanced rule, these values may only be changed to a descendant of the value in the original rule.  For example, if the original rule is defined on the PegaSample class, the circumstanced rule may be defined on PegaSample, or it may be defined on PegaSample-Task or any other rule that inherits from PegaSample.  If the circumstanced rule is defined on Work-, for example, it will be considered a completely separate rule and would not be considered as a circumstance of the base PegaSample rule during rule resolution at runtime.

4.  Expand the Circumstance section of this form by clicking on the arrow to the right of the Circumstance label.

5.  Choose Property from the Use dropdown box.

6.  For a property-circumstanced rule, enter or select the circumstance Property. 

7.  Enter or select the circumstance Value.

NOTE:  Once you have created the first circumstanced rule, then choosing Save As to create additional copies of that rule will display a dropdown with the previously-chosen property name, instead of a field with a SmartPrompt.

 

Also, after you choose the property, the additional values of that property will display in the Value field:

8.  For a circumstance-date-qualified rule, enter or select the circumstance Date Property.

9.  Enter or select the circumstance Date Value.

10.  Click the Save As toolbar button.

Creating a Date-Range-Qualified Rule

1.  Open the base rule on which you wish to define a date range.

2.  Click Save As to save the rule.  The Save Rule Instance under new key dialog box appears.

3.  If desired, change:

  • the Applies To class name
  • the RuleSet Name
  • the RuleSet Version

Important:  For a valid circumstanced rule, these values may only be changed to a descendant of the value in the original rule.  For example, if the original rule is defined on the PegaSample class, the circumstanced rule may be defined on PegaSample, or it may be defined on PegaSample-Task or any other rule that inherits from PegaSample.  If the circumstanced rule is defined on Work-, for example, it will be considered a completely separate rule and would not be considered as a circumstance of the base PegaSample rule during rule resolution at runtime.

4.  Expand the Date Range section by clicking on the arrow to the right of the Date Range label.

5.  Using the calendar icons, choose a date for the Start of this rule (when this rule will be valid), and the End of the rule (when the rule is no longer valid).

6.  Click Save As to create this rule.

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