Skip to main content

 –

Declare OnChange rules -

Suggest edit Updated on October 13, 2021

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 OnChange rule by selecting Declare OnChange from the Decision category.

Key parts:

A Declare OnChange 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 unique name for this OnChange rule within the class. Begin the name with a letter and use only letters, numbers, the ampersand character, and hyphens.

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

Rule resolution

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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