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

Issue with max legth of pyAssignedToWorkGroup in History-Wok-



pyWorkGroupName has max length of 64 in its property. So it accepts a workgroup name of characters upto length 64. But when running through a scenario to submit an assignment, it goes to pyAssignedToWorkGroup which has max length of size 32. So the same workgroup name is not acceptable here. There is an error shown in tracer 

(History-GCS-SRA15933-Work121212121212121212121212121212121212)StringTooLong "GCSSRA15933Work121212121212121212121212121212121212" 32

When tried to perform SaveAs of pyAssignedToWorkGroup to increase its max length from 32 to 64, it gives an error saying that the property is already exposed in the database column and hence it cannot be changed.

Error Messages

Error in tracer

(History-GCS-SRA15933-Work121212121212121212121212121212121212)StringTooLong "GCSSRA15933Work121212121212121212121212121212121212" 32

Steps to Reproduce

1. Create a work group with name greater than 32 characters.
2. While execution, perform the submit of any assignment in that workgroup.
3. Observe the tracer for the error in Assign- AddWorkHistory 

Root Cause

An error occurs in the tracer while trying to perform the submission of an assignment which has WorkGroupName more than 32 characters. 


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

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