I have this issue where the task is getting assigned to two users when I am actually configuring it to assign task to one user alone. I created a process variable called assignee of type User and this is the logic:
if( pv!reopenTaskFlag = true(), pv!IA_Task.requestedBy, pp!initiator )
In the case where I am having the issue, pv!reopenTaskFlag=true() so it should be returning pv!IA_Task.requestedBy which is of type User. When I monitor the instance, pv!assignee has the correct value (just one user). But for some reason the task is also getting assigned to the initiator... Below is a screenshot of the user input task assignment node. Any idea what the problem could be?
Discussion posts and replies are publicly visible
Are you using activity chaining into the form? If you use chaining, then whoever was assigned the most recent task (or whoever started the process) will also be assigned to this task when they are chained together.
This is interesting, if Employee fills a form and it goes to Manager 1 for approval and Manager 2 gets it after Manager 1 submit. If those UI tasks are chained, Manager 2 can see Manager 1 task?.. isn't this odd?
Do you mean "Manager 1 can see Manager 2's task"? Assuming that's what you mean, this is expected behavior when using activity chaining. Chaining will always link chained task together with the same user. In general, activity chaining should be used sparingly - only use it if the same user needs to view the next step in the process immediately after submission of a form.