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

Property-Ref does not work for page when classes mismatched



If two pages have different classes and different inheritance structure, the Property-Ref method will not reference between the two pages.

Data Page: D_TestPage

class : Application-FW-ImpLayer-Work-WorkType
Property: PropTestPage1 (Page, Class: Application-FW-ImpLayer-Work-WorkType)

Data Page: D_TestPage3
Class: NewTest (extending from @baseclass)
Property: TryPage1 (Page, Class: NewTest-Test1) (Allow use as reference property in activities checked)

Error Messages


Property-Ref from D_TestPage3.TryPage1 = D_TestPage.PropTestPage1 does not work because of conflict of class.

Hence pages with different class cannot be Ref.


Steps to Reproduce

  1. Create an activity.
  2. Specify a step to perform a Property-Ref method between a property of a class type A and a source property of class type B (Class type A has a completely separate inheritance stucture as compared to Class type B).
  3. Attempt to save the activity and observe the error displayed at the top of the activity.


Root Cause

This issue was determined to be a product enhancement request.

The current behavior is expected and is documented on the help at the following URL:



An enhancement request, FDBK-16628, has been created for consideration by Pega Product Management. 



Published September 23, 2016 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 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