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

Rule resolution issue with Property-set method

SA-8573

Summary



Property name ‘TestProperty” present in 2 classess

XX-XX-XXX-Data-Customer inherits from Data-Party
  • TestProperty – No Max length restriction
Data-Party
  • TestProperty- 5 Max length restriction
 User is using activity to set value using property-set method. System enforced 5 max length restrictions for TestProperty in XX-XX-XXX-Data-Customer. 


Error Messages



"More than 20 Characters for testing Purpose" is too long, maximum length allowed is 5

Steps to Reproduce

  1. Create TestProperty in XX-XX-XXX-Data-Customer (inherit from Data-Party)
  2. Create TestProperty in Data-Party
  3. Create activity to set value to TestProperty in XX-XX-XXX-Data-Customer
  4. Define TestPage (point to work class) , .pyWorkParty(Customer)( points to XX-XX-XXX-Data-Customer)   in Pages & classes
  5. For property-set method give TestPage as Step page
  6. Give .pyWorkParty(Customer).TestProperty as target and "More than 20 Characters for testing Purpose"  as source for property-set

Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules. and this will be fixed in future releases. 


Resolution



This issue is resolved through the following local change: Issue is resolved by providing TestPage.pyWorkParty(Customer)  as step page instead of TestPage for property-set method.

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% 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