Skip to main content

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.

Support Article

Unable to save Declare Expression, which is using Page Reference



Post upgrade from PRPC 6.3 SP1 to Pega 7.1.9, when trying to perform a Save-As of existing declare expression rule, receives an error. 

Error Messages

"The expression (right hand side): No input properties detected. To use this expression, please change 'Calculate Value' (under the Change Tracking tab) to one of the "When used" options." 

Steps to Reproduce

1) Create a Declare Expression rule. 
2) Use input as PageName.PropertyName. For example, @max(100,@toInt(pyWorkPage.pxUrgencyWork))
3) Define Page in Pages & Classes.
4) Use Whenever inputs change.

Root Cause

This is an expected behaviour with Pega.

The reason behind this issue is, it is getting saved, which is a BUG in PRPC 6.3 SP1.

There should be a design time validation fired once you try to save the rule. This is fixed in PRPC 6.3 SP1 as well with HFix-7286.

Post this HFix the rule is not saved in PRPC 6.3 SP1 as well.


Forward chaining is never supported on pages other than primary page.

An expression can reference properties on other pages using a page name (defined on pages & classes tab) and property reference but these properties are not change tracked.

So only the property reference that inherits from primary page or a top level page may work, if the property is specified with page reference in expression. 

For example, change from:


If .pxUrgencyWork is in primary page, it works fine.

Suggest Edit

Published February 9, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us