We have a requirement where we need to move the screen flow assignment to another user. We moved the assignment to the new operator succesfully implementing a local action which moves the assignment to the current operator using pxTransferAssignment. But when the operator submits the screen. the next assignment goes back to the previous operator that was assigned. We have tried the following suggestion.
We are modifying the DefaultAssignTo in the post processing activity of the local action that moves the assignment to the current operator (AssignToMe). But when the assignment is open the pyFlowParameters specifically the DefaultAssignTo and AssignTo properties get refreshed and have the value of the old operator.
It says this is fixed in 8.3.2, but shows how to over-ride the issue. But I think that I would not use pxObjClass as your flag - I would use a property that I create and have full control over, and which will not create other side effects in Pega.
Posted: 6 months ago
Updated: 2 months ago
Posted: 13 Jan 2021 3:04 EST Updated: 5 May 2021 19:47 EDT
Anil Vanaparthi (vanaa)
Tech Lead, Software Engineering - India
@vanaa Hi, I have a similar requirement but it needs to go from a workbasket to a worklist, the above steps seem to work but when it goes to open the next assignment it goes to broken process as it's still looking for a workbasket. is there any way to change it to Assign-Worklist instead of Assign-Workbasket?