I am using OOTB pyTransferAssignment (customized little but to use only transfer to operator, removed when rule pxIsNotInternalAssignment in security tab of flow action because flow action is not available as case wide action when it is already assigned to a user) as a case wide action.
When end user trying to transfer the assignment from workbasket to an user there is no issue but when end user try to transfer the same assignment to different user then it is creating a new assignment with name "Internal flow" assigned to new user selected.
Looks like OOTB pyTransferAssignment is not designed for transferring assignment from one user to another as I have to remove the when rule in security of flow action.
Please note when the user begin the assignment and try to transfer assignment (case wide action) then it is working as expected. Also user with developer access is able to do it successfully.
Can someone tell me what i did wrong
***Edited by Moderator: Bhavana S to add capability tags***
@nagavenkatan5018 I think I have faced similar kind of issue. If end user opens that case from worklist and then do transfer assignment via case wide local actions, then it would work.
I assume your scenario is, if assignment is on person A's worklist, then A will transferring assignment to another person. If person C is the one who should be transferring from A to B, then C is actually playing manager role. And you need to give manager access so that users can access worklist of another users.