Skip to main content


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

Constraints form - Completing the Pages & Classes tab

Updated on November 15, 2021

Complete this tab to list the pages referenced by name in the Constraints tab, and to identify the context of the properties constrained.

  1. About
  2. New
  3. Constraints
  4. Pages & Classes
  5. History
  6. More...

For basic instructions, see How to Complete a Pages & Classes tab.

FieldDescription
Page Name Optional. Identify a page that is the source of properties referenced on the Constraints tab.

Optionally, add a row with the keyword Top as the page name, to identify a top-level page. The Top keyword allows you to use the syntax Top.propertyref to identify properties, on other tabs of this rule form.

ClassOptional. Select the class of that page.
Locate Page ExpressionThe Locate Page Expression option is not supported. Use a data page instead. Rules created in previous versions that use the Locate Page Expression display this field. New rules do not display this field. Changes to a rule that uses this option cannot be saved unless Locate Page Expression is replaced by supported functionality.
Locate Page ActivityThe Locate Page Activity option is not supported. Use a data page instead. Rules created in previous versions that use the Locate Page Activity display this field. New rules do not display this field. Changes to a rule that uses this option cannot be saved unless Locate Page Activity is replaced by supported functionality.
Page Context Data
Page Context Optional. Leave this blank if the constrained property or properties (on the Constraints tab) all have mode Single Value.

Otherwise, identify a Page List or Page Group property on the clipboard. You can supply literal index (subscript) values or property-reference index values. Precede the property reference with a period.

To indicate that all the values of the index are acceptable, omit any index between parentheses. For example, these are acceptable:

Invoices.py Orders(2).pyItems("Manuals").pyItems
Invoices.py Orders().pyItems().pyItemNames
Page Class Optional. If the Page Context field is not blank, identify the class of the page or pages that are identified in the Page Context field. (You cannot use the $ANY, $NONE or $CLASS keywords here.)

About Constraints 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