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 OnChange form - Completing the Pages & Classes tab

Updated on April 5, 2022

Use this tab to list the pages referenced by name in the OnChange tab. Specify the pages in an array containing these fields. See How to Complete a Pages & Classes tab for basic instructions.

  1. About
  2. New
  3. OnChange Properties;
  4. Pages & Classes
  5. History
  6. More...

If the watched properties are an aggregate or are on an embedded page, complete the Page Context Data fields.

FieldDescription
Pages and Classes
Page Name Optional. Name of a page referenced on the OnChange Properties tab.

You can identify named pages here to support evaluation of a when condition rule referenced on the OnChange Properties tab. However, all tracked properties must be on the page corresponding to the Applies To key part, or a context within that page.

ClassOptional. Select the class of that page.
Page Context Data
Page Context Optional. Leave this blank if the monitored properties are Single Value properties that appear on a top-level page.

Otherwise, identify a Page List or Page Group property reference on the page. You can supply literal index (subscript) values or property-reference index values. Omit any index to indicate that all values of the index are acceptable.

Page Class Optional. Identify the class of the page or pages that are identified in the Page Context field. You cannot use the keywords $ANY, $NONE or $CLASS here.

About Declare OnChange rules

  • Previous topic Declare OnChange form - Completing the OnChange Properties tab
  • Next topic More about Declare OnChange rules

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