Support Article
Assignment issue after performing Transfer Assign(Reassign)
SA-15469
Summary
When user A opens an assignment from work basket that assignment is getting assigned to User A and is performing certain steps and using Transfer local flow action user A is assigning this to a work basket. Now when user B opens the same assignment from work basket the assignment is not attached to user B. Instead it is still in the work basket.
Tracer log files are attached when an user clicks on the assignment for the first time (Tracer_WBIssue_UserA.rar) and an user clicks on the same assignment after performing transfer action(Tracer_WBIssue_UserB.rar).
Error Messages
Not Applicable.
Steps to Reproduce
Assume that an assignment has been assigned to an Workbasket.
1. Login as User A, select workbasket and then click on an assignment
- assignment is now in user A worklist
2. As user A, transfer assignment to same/any workbasket
3. As user B, select same workbasket and select same assignment which
user A transferred to workbasket - Assignment is not in user B worklist.
Root Cause
User is expecting an option or configuration on the workbasket assignment , such that, whenever the user clicks on any assignment in that workbasket , it gets automatically assigned to that operator.
Resolution
Perform the following local-change:
With out-of-the-box (OOTB) functionality, clicking on assignment link in work basket assignment will not automatically assign to user worklist.
To assign automaticall one must open that assignment and use the transfer local action( pxTransferAssignment) or need to write a custom activity which moves workobject to worklist .
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.