Skip to main content


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

Supported and unsupported configurations in simplified declare expressions

Updated on January 14, 2022

As of Pega Platform 8.3, the Change tracking tab has been removed from the declare expression rule form to simplify expression configuration. In these simplified declare expressions, some Target Property Data and Context Execution Behavior configurations are not supported.

Note: To access the Change tracking tab, click ActionsUse legacy expression.

Supported configurations

In simplified declare expressions the target property's value is only calculated whenever used. Additionally, expressions are always executed regardless of the context of the pages they are contained in.

Unsupported configurations

The following Target Property Data field options are not supported for simplified declare expressions. For detailed information about these options, see Declare Expression form - Completing the Change Tracking tab.

  • Whenever inputs change
  • When used, if no value present
  • When used, if property is missing
  • When applied by a Rule Collection
  • When invoked procedurally

The following Context Execution Behavior field options are not supported for simplified declare expressions. For detailed information about these options, see Declare Expression form - Completing the Change Tracking tab.

  • Only when the top-level page is of the Applies To class
  • When the top-level page is of the Applies To class, or specified Allowed Top-Level Classes

Page context changes

In simplified declare expressions, context-bound rules are not supported.

Non-atomic targets

Non-atomic targets are not supported in simplified declare expressions, for example, .page.targetProp.

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