Question
Capgemini
IN
Last activity: 10 Jun 2021 11:53 EDT
Error: Assign Mismatch while transferring to Work List from WorkBasket
Hello Team,
While assigning Assignment to worklist from workbasket we are facing issue like instance is removing from assignworkbasket and inserting in to assign worklist table with PYASSIGNMENTSTATUS as "Error: Assign Mismatch". The issue happening for few cases in production.
Its not updating the pxFlow in clipboard ,In pxFlow it is still pxAssignClass->Assign-WorkBasket
In newAssignPage --pxAssignClass->Assign-Worklist only
Appreciate your help here.
Prem K
Pegasystems Inc.
FR
Never seen this issue before. Have you been able to trace it? Can you share the tracer XML file?
Capgemini
IN
@MarcLasserre_GCS Hi Marc Thanks for responding. We are unable to reproduce the issue in lower environments and so no tracer file. However need one clarification on pre-condition when at step no 8 from the activity "pxTransferAssignment", where when there is an error on "newAssignPage" "Rollback" step is skipped even if there is no issue on work page. Attached the screen shot.
Appreciate your help.
Thanks
Prem K
Pegasystems Inc.
FR
Right I see.
If you are not able to trace it will be difficult to find out. Maybe your log files could tell us a bit more on what was happening.
Concerning the Step8 of the activity, I think this is perfectly normal. The 2 first when will check if the transfer has been executed correctly and of course rollback if not.
But you could have done the transfer and still get a remaining message on your step page depending on the scenario. There rollback will not be needed.
Capgemini
IN
@MarcLasserre_GCS The strange issue here is when we are transferring Assignment from WB to WL using "Reassign" activity, the WB entry is deleted and creating an entry in WL which is an corrupted entry. In our logic we have defer saves and not commits unless when there is no issue. But somehow the changes are committed to WL and WB table but not the work object. Due to this we see pxFlow Assignment key is still with Assign-Workbasket while the entry is in WL table. If transaction is rollbacked then all the defer saves including WB and WL should be rolled back which is not happening in this case.
Appreciate your insights here.
Thanks
Prem K
Pegasystems Inc.
IN
Verify the newAssignPage property pxRefObjectPageName
It should have the correct case context i.e, pyWorkPage