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

Size of pyLabel property in @baseclass requires change

SA-19991

Summary



Issue occurs while creating work party with user name more than 64 characters. The error does not appear in front end. The work object was in open status when viewed under Audit. However, the money was deducted.

Error Messages



Trying to save an invalid page: ** ** .pyWorkParty(PropertyOwner).pyLabel: "DFC (Project Management) Pty Ltd DFC (Project Management) Pty Ltd" is too long, maximum length allowed is 64 .pyWorkParty(PropertyOwner).pyLabel: "DFC (Project Management) Pty Ltd DFC (Project Management) Pty Ltd" is too long, maximum length allowed is 64 Trying to save an invalid page: page is not valid .pyWorkParty(PropertyOwner).pyLabel: "DFC (Project Management) Pty Ltd DFC (Project Management) Pty Ltd" is too long, maximum length allowed is 64”.

Steps to Reproduce



1. Create an operator with full name exceeding 64 characters.
2. Add the operator as a work party.


Root Cause



The root cause of this problem is a defect in Pegasystems’ code or rules.
pyLabel property in the Data-Party.WorkPartyRetrieve activity is assigned with OperatorId's pyTitle and pyUserName. But, it can hold only 64 characters that caused the error.

Resolution



Perform the following local-change:

1. SaveAs the Data-Party.WorkPartyRetrieve activity in the custom ruleset.
2. Truncate the pyLabel value in the the activity to make it less than 64 characters.
Suggest Edit

Published February 26, 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