The work object references a different assignment than the current one
I am using OTB activity pxTransferAssignment to transfer assignments from current interaction case to a given workbasket or operator's worklist.
When the transferred interaction is opened from the new destination operator's worklist, it opens fine.
However, if the interaction is transferred to a workbasket and opened from there, it throws the error:
"The work object references a different assignment than the current one"
Why?
***Moderator Edit: Vidyaranjan | Updated Categories***
Accepted Solution
BUPA
AU
Hi Yelas,
I think commit is needed. Pls check the below article published by Pega to solve assignment transfer issue. Hopefully this will help.
In case it doesn't help then I would suggest you to run a trace to check error while opening the assignment. Also at the same time run the DB trace to see any rollback is happening or not. It is possible to SLA is corrupting the assignment. Pls remove the SLA and try again.
BUPA
AU
Hi,
Pls check the entry in the pc_assign_workbasket table for the workobject. Ideally this should have the correct workbasket name in the pxassignedoperatorid field. If it is different the probably there is some problem with the parameter value being provided. Pls check and let us know to understand the root cause.
Pegasystems Inc.
US
Thanks Swarendu. The pc_assign_workbasket has 2 entries for this case. One for 'Initial Process Task' assigned to the correct pxAssignedOperatorId (set to correct workbasket name) and the other 'SLAProcessing' with pxAssignedOperatorid= Proprietary information hidden.
The first record has pyAssignmentStatus='Open' until the case is accessed from the workbasket when it changes to 'Error: Assign Mismatch'
Also, if I don't check the 'Commit' option for the call 'pxTransferAssignment', then the case doesn't transfer to the workbasket but stays in my worklist.
Accepted Solution
BUPA
AU
Hi Yelas,
I think commit is needed. Pls check the below article published by Pega to solve assignment transfer issue. Hopefully this will help.
In case it doesn't help then I would suggest you to run a trace to check error while opening the assignment. Also at the same time run the DB trace to see any rollback is happening or not. It is possible to SLA is corrupting the assignment. Pls remove the SLA and try again.