Hi Sam,

At a time the work-object can be assigned to only one operator. If the work-object to be accessible to the multiple operators then create an work-queue.

But when one operator picks the work-object from the work-queue and if another operator tries to open the same work-object from work-queue at the same time then a work object lock message gets displayed for the second operator if the case was configured with the default locking.

The first operator who picks the work-object from work-queue gets moved to their worklist.

If the case was configured with the optimistic locking, then both the operators can open the work-object at the same time. In this case if operator1 opens the work-object and submit the case first and the same-time if operator2 works and submit the case then the operator2 gets the message saying that the case was updated by operator1 and asking to refresh the screen to get the updated values.

But the following approaches suggests transferring the work-object assignment to another operator when any of the operators is working on the case.

Approach 1:

You can simply configure the OOTB flow action: Work- pyTransferAssignment as local action and transfer the current work object assignment to other operator worklist or work basket.

Approach 2:

call "pxTransferAssignment" OOTB activity at the place you need to transfer your case. Just pass these required params.

AssignmentID - pzInsKey of the Assignment To be Transferred

DestinationType -  Type of destination Worklist (Operator Id) or Workbasket

DestinationName - Name of the destination Worklist(Operator Id) or Workbasket (Name of workbasket)