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.
***Edited by Moderator Marissa to update Platform Capability tags****
@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.
Posted: 3 months ago
Posted: 3 Mar 2021 13:06 EST
Marc Lasserre (MarcLasserre_GCS)
Principal Software Solutions Engineer
@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.