Question
WellFargo
IN
Last activity: 24 Sep 2018 6:42 EDT
Getting error as "The work object references a different assignment than the current one." when opening the case from WorkList/WorkBasket
I'm transferring claim from work basket to Worklist (or Worklist to WorkBasket) and when I try to open the claim from the WorkList , its throwing an error as.
The work object references a different assignment than the current one.
Due to this I'm unable to transfer the claim to different WorkList / WorkBasket
Functionality is working fine for WorkBasket to WorkBasket / Worklist to WorkList transfer
Did anyone face this issue ?
Accepted Solution
WellFargo
IN
Yes we are using 7.3.1 and at 15th step flow page is updated.
Issue has been resolved now. It was happening because we had customized TransferSelectedClaims and during transfer, it was unable lock the claim and save it.
Now we have included that step and used obj-save and issue got resolved
Thank you so much for the guidance, it helped a lot understand logic behind this
Pegasystems Inc.
US
What activity are you using for the transfer? What do you see for the assignment handle on the newAssignPage and the pyWorkPage flow page?
WellFargo
IN
I'm using Reassign activity for transfer.
I can see the assignment handle in newAssignPage but not in pyWorkPage ( My understanding of Assignment handle is that it shows class and timestamp , correct me if I'm wrong)
Pegasystems Inc.
US
The assignment handle is usually the class, pxRefObjectKey, and pxFlowName. The pxFlow page under pyWorkPage should show the pxAssignmentKey. It sounds like the newAssignPage and pxFlow page are not in sync. I am looking at the Reassign activity in a 7.3.1 system and see there is a Page-Change-Class step for the newAssignPage. There is also a step to update the pxFlow page on the work object if the page exists. Can you trace the reassign process and check to see if both the assignment and work page are being updated the same?
Pegasystems Inc.
US
What about the pxAssignmentKey on the pxFlow page?
Here I have a worklist assignment and my newAssignPage shows the ASSIGN-WORKLIST ... pzInsKey.
On the corresponding pxFlow page under pyWorkPage, I see the pxAssignmentKey value matches my assignment page.
WellFargo
IN
In pyWorkPage pxAssignmentKey property is available but its having value as Assign-WorkBasket.....
In newAssignPage I can see the value as Assign-WorkList...
Both values are not matching
Pegasystems Inc.
US
And did you see the step execute to update the flow page? I am not sure what Pega version you are using. In 7.3.1, I see Work-.Reassign in Pega-ProcessEngine:07-10-31 and the flow page should be updated in step 15 if pxFlow exists.
Accepted Solution
WellFargo
IN
Yes we are using 7.3.1 and at 15th step flow page is updated.
Issue has been resolved now. It was happening because we had customized TransferSelectedClaims and during transfer, it was unable lock the claim and save it.
Now we have included that step and used obj-save and issue got resolved
Thank you so much for the guidance, it helped a lot understand logic behind this
Standard Chartered
IN
If you are already having lock on your case, no need to open the case. But use refresh-And-lock method after your commit happens on pyworkpage.
Hope this helps..