Skip to main content

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 Circumstance Template rule

Suggest edit Updated on September 10, 2021

Summary

Circumstance Template rules are one of two types of rules which you create to qualify a rule by more than one circumstance property (see How Multivariate Circumstancing Works).

These circumstance rules are then referenced in the circumstance setup for an activity, When, or other rule.

 

Suggested Approach

Before you begin

Before creating the Circumstance Template, determine which properties are going to be used as circumstance properties in the multivariate circumstancing setup. These properties must exist in an appropriate class (for example, if these properties will apply to creating new invoices, they must be in the invoice class).

Create the rule

1.  From the Rules by Type explorer, expand the Technical link.  Right-click on Circumstance Template, and click New.

2.  On the New form, complete the fields as follows:

            a.  In the Applies To field, enter the name of the class to which this Template applies.

            b.  For Purpose of Rule, enter a name which describes the type of circumstancing this rule will provide (examples:  “CustomerStatus”, “SendNotices”, “StateTax”).

            c.  In the RuleSet – Name field, enter the name of the RuleSet where this rule will be saved.

            d.  In the Version field, enter the RuleSet version.

            e.  Click Create.

3.  On the Template tab, enter the properties which will be used as circumstances for this Template, along with the labels for each property that will display in the Circumstance Definitions.

4.  Click the Save toolbar button..

Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

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

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