User with long name can`t perform tasks (workparty problem)
When workparty is added to workobject, it`s pyLabel is generated automatically in activity GetOperatorIDFromClipboard from operator`s pyTitle and pyUserName
If operator have long title and pyUserName, party`s pyLabel exceed 64 symbols and validation error occurs.
User is not able to start or perform new task.
GetOperatorIDFromClipboard activity is final, and we can`t correct it.
pyLabel is defined in Pega-RULES @baseclass with max length 64, and we can`t override this by resaving in our rulesets.
We tried Edit Input and Declare OnChange for pyLabel property in Data-Party class without success.
Is there any way to avoid this problem?
***Updated by moderator: Lochan to add Categories***
***Updated by moderator: Lochan to close post*** This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
You can not change the maximum length specified for pyLabel property as it is exposed in database with that size limit. The alternate way is to truncate the user name so that it matches the size and they can proceed with case creation.
Can you try using the Work-NewDefaults activity by saving it in your local ruleset and use the truncateLongText function to truncate the entries so that the length does not go beyond 64.
NewDefaults activity is an extension points activity and gets called from Work-.New and Work-.NewCovered, This activity allows the user to customize or extend the steps that are performed while creating new work page for the new harness.
You can use a property set method and set the values for pyLabel like this : @(Pega-RULES:String).truncateLongText(.pyWorkPage.pyWorkParty(Interested), 50)
Assuming we set the workpool in the access group to "PegaSample" (available out-of-box) and then run the "PegaSample-CustomerRequest . NewWork" flow, can someone please explain what specifically to do to illustrate the problem being discussed here ?
One thing you'd need to be real careful about if you expand the pyLabel column to more than 64 characters (and all the validation rules and max limit settings for properties, and recompile all the activities whose generated java includes "setEntryCode" calls that refer to the old max limit) , is to worry about any places that copy the pyLabel into other fields that have a limit less than the large value you're thinking of expanding pyLabel to. In other words, this sounds like a dangerous thing to do. /Eric
Yes, I'd also agree here too. We've had similair issues not with the PEGA restirction but more trying to share the user name who performed the action to other down stream applications - these systems didn't like long user names. So even if you fix in PEGA, IF you ever plan to use that name to say drive writing details into another system then they would need to support your new length too. Truncating in the end was just easier.