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.

Declare Trigger rules -

Updated on April 5, 2022

Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.

Create a Declare Trigger rule by selecting Declare Trigger from the Decision category.

Key parts:

A Declare Trigger rule has two key parts:

FieldDescription
Apply to Select a class for this rule. At runtime, a clipboard page of this class must be a top-level page. The properties to be watched may be in this class (or in the class of an embedded page).

You cannot use a Rule-Declare-* class or any ancestor of the Rule-Declare- class (including @baseclass ) here. You cannot use a class derived from the Code- or Embed- class here.

Identifier Enter a name for this trigger rule. Begin the name with a letter, and use only letters, numbers, the ampersand character, and hyphens.

No other rules explicitly reference this Apply to value. However, because of normal class inheritance, a Declare Trigger rule named NewGoldCard at one level in the class structure may override (and so prevent execution of) a Declare Trigger rule named NewGoldCard at a higher level in the class structure.

Rule resolution

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