nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Group task ownership

voanu

Is there any way we can have control on who takes the ownership of a task in a group task while running the workflow according to our requirement?

Find more posts tagged with

Comments

kaalraa

Is there any way we can have control on who takes the ownership of a task in a group task while running the workflow according to our requirement?

Group task is always shared by number of users... and anyone can take the ownership. However if you need to define owner while running a workflow... its better to use a Usertask and Set the owner at run time from a script.

Sailesh

Don't know your requirement but won't it be good idea to make a user task and change the owner based on requirement..

voanu

I’m doing some user validation while in the workflow instantiation screen like two tasks cannot have the same user. But a group also can be selected to be assigned to a task and so two tasks can have same group but when taking the ownership both the tasks should not be able to assign it to same user. Can this be achieved? Is there a way we can control the take ownership while the workflow is running based on the owner of the previous task?

I also have one more validation where in a user with only author role can be assigned to a particular task. I’m able deal that validation when a single user is selected in the workflow instantiation screen but group can also be selected to be assigned to a task and when a group is assigned to that task the ownership can be taken by anyone irrespective of their privileges. What can I do to deny the permissions when a user without proper privileges tries to take ownership?

Adding an other user task doesn't agree with my requirement.

Thanks
anu

Sailesh

Regarding your first query; how about having a separate list of users assigned to the group task (perl variable and not from the user group) and based on who has taken the first task remove that user from the list for the second group task.

Adam Stoller

I’m doing some user validation while in the workflow instantiation screen like two tasks cannot have the same user. But a group also can be selected to be assigned to a task and so two tasks can have same group but when taking the ownership both the tasks should not be able to assign it to same user. Can this be achieved? Is there a way we can control the take ownership while the workflow is running based on the owner of the previous task?

I also have one more validation where in a user with only author role can be assigned to a particular task. I’m able deal that validation when a single user is selected in the workflow instantiation screen but group can also be selected to be assigned to a task and when a group is assigned to that task the ownership can be taken by anyone irrespective of their privileges. What can I do to deny the permissions when a user without proper privileges tries to take ownership?

Adding an other user task doesn't agree with my requirement.

Thanks
anu

For the first - the approach I would take would be to have an iwat trigger script set to monitor the taking of the first grouptask which notes who took ownership - and then examine / modify the sharedby element of the second grouptask (expand all group memberships and remove the group entries from the sharedby list; eliminate duplicate entries [if any]; eliminate the user who took ownership of the first grouptask; re-set the sharedby element to the remaining list of users).

Yeah, it sounds a bit difficult, but it really shouldn't be too bad - just figure out the design so that you understand clearly what you are going to do before you plunge forward trying to implement it.

For the second - you can do that either in a similar manner to the above, but via an externaltask near the beginning of the workflow - or within the WFT itself. Essentially you take the group you wish to share responsibility for the task; expand it to its constituent members; eliminate any members who are not authorized to login with the Author role(*); re-set the sharedby element with the remaining list of users.

(* If a user can login with Author and other roles - it is assumed that it is okay for them to take ownership of the task - even if they happen to be logged in with another role at the time they attempt to take ownership. If you really want to make sure that the person who takes ownership of the task is currently logged in as an author it will be more difficult and the user interface will probably be pretty bad)