How to avoid Take ownership in the group task.

I have group task in which I have shared by as available users and passed the users.

Now I want to avoid Take ownership of task i.e when grouptask comes
every user in the group task has ownership.
If any user Accept or Reject the content, then workflow will continue.

If anybody has done similar thing..... Please Reply...

TS:6.7.2
OS=Window 2003

Thanks....

Find more posts tagged with

Comments

Adam Stoller

I have group task in which I have shared by as available users and passed the users.

Now I want to avoid Take ownership of task i.e when grouptask comes
every user in the group task has ownership.
If any user Accept or Reject the content, then workflow will continue.

If anybody has done similar thing..... Please Reply...

TS:6.7.2
OS=Window 2003

Thanks....

This is not a Group Task. This is a concurrent workflow process model in which the preceding task transitions to N user tasks and you use an OR gateway to determine whether to proceed to the next task or transition back to an earlier task (presumably preceded by an Email Task).

Search for both "concurrent" and "resets" (two separate searches) in the Workflow Developer's Guide (not the WFM Guide) for more information.

vaibhav2288

This is not a Group Task. This is a concurrent workflow process model in which the preceding task transitions to N user tasks and you use an OR gateway to determine whether to proceed to the next task or transition back to an earlier task (presumably preceded by an Email Task).

Search for both "concurrent" and "resets" (two separate searches) in the Workflow Developer's Guide (not the WFM Guide) for more information.

Thanks for response.

As you said for resets, but by using that I will be able to do AND, OR, NOT such conditions, but to apply those conditions someone needs to take ownership of that task in order to enale Accept or Reject to select and continue.

What I have to do is that, user dont have to click Take button in group task, directly task has to assigned to all the users in the group, then one of the user can accept or reject, then I can use the resets as suggested by you for determining whether Accepted or Rejected by one of the users.

Thanks .....

ISCBorisB

Thanks for response.

As you said for resets, but by using that I will be able to do AND, OR, NOT such conditions, but to apply those conditions someone needs to take ownership of that task in order to enale Accept or Reject to select and continue.

What I have to do is that, user dont have to click Take button in group task, directly task has to assigned to all the users in the group, then one of the user can accept or reject, then I can use the resets as suggested by you for determining whether Accepted or Rejected by one of the users.

Thanks .....

You can not do it with the group task, it is that simple.

Re-read Ghoti's post carefully. He's proposing to make concurrent user tasks, one for each reviewer.
You do not have to "take" any of those. Depending on your gateway logic, individual reviewer actions
will then define the flow.

vaibhav2288

You can not do it with the group task, it is that simple.

Re-read Ghoti's post carefully. He's proposing to make concurrent user tasks, one for each reviewer.
You do not have to "take" any of those. Depending on your gateway logic, individual reviewer actions
will then define the flow.

Sorry for the late response. Thanks.

How can I convert my group task into concurrent user task. so that all user should get the usertask. Do I need to use the Review task or User task.

Thanks .....

Adam Stoller

Sorry for the late response. Thanks.

How can I convert my group task into concurrent user task. so that all user should get the usertask. Do I need to use the Review task or User task.

Thanks .....

You need to use N User Tasks - determining the number and owner of each dynamically during instantiation based on the users / groups you chose in the instantiation form.

I don't recall off the top-of-my-head how one does this in a WFM. In a WFT you just write a loop in Perl (there are OOTB examples in IWHOME/local/config/wft/solutions if I recall)

(for WFM, I think it might be the use of concurrent serial Review Tasks. I think you can specify the number of such tasks as a variable that you can then set within a custom instantiation form)

vaibhav2288

You need to use N User Tasks - determining the number and owner of each dynamically during instantiation based on the users / groups you chose in the instantiation form.

I don't recall off the top-of-my-head how one does this in a WFM. In a WFT you just write a loop in Perl (there are OOTB examples in IWHOME/local/config/wft/solutions if I recall)

(for WFM, I think it might be the use of concurrent serial Review Tasks. I think you can specify the number of such tasks as a variable that you can then set within a custom instantiation form)

Thanks for response.

I can know the number of users in this task and can pass this number and user ID's of those user as variable in the workflow.
But after email is sent to all the user, how can i create those N user tasks dynamically for each user.

Thanks