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

Updated on May 27, 2008

This presentation is part of the Declarative Expressions Self-Study Course.


In an Expressions rule, the Pages & Classes tab works in a similar fashion to the way it works in other rule types, with a few added extras.

It is the place where you define the names and classes of any pages that this rule will reference. It is for defining the design time references to ensure you build a valid rule. Remember: Properties in these other pages are not change tracked.

Let’s start by looking at the Page Context Data section of the form and the Class field. There are some important version differences to note:

  • In PRPC versions 4.1 to 5.3, expressions have to be built, or inherited into, the Work-Object class. So any expression that targets a property in an embedded page has to be created with the embedded page context as part of its name.
  • From PRPC version 5.4, expressions can be built in any class. This dramatically simplifies building expressions, as it removes the need for page context and class on the form.  You simply add expressions in the classes of their target properties.

Moving to the Page Name and Page Class fields, these fields work in the same way as in other rule types. Simply type the names and classes of the pages you are going to reference in them. The system uses these references to validate your rule at design time.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us