Understanding the grouptask concept

i have a grouptask for approving content. 4 people are in this group. all can see the workflow task. one of the four people takes the task. i can now see the owner is the person that did the "take". my question is, should the other three people still be able to approve or reject the content? i did not "take" the task but was able to approve the content. is this the way it is suppose to work?

Find more posts tagged with

Comments

Pawan

Which version of TS are you working on ?
On TS 6.7.1 its not this way, once a user has taken the ownership of a group task his is the owner and he can only approve/reject the task, unless he releases the ownership.

kaalraa

i have a grouptask for approving content. 4 people are in this group. all can see the workflow task. one of the four people takes the task. i can now see the owner is the person that did the "take". my question is, should the other three people still be able to approve or reject the content? i did not "take" the task but was able to approve the content. is this the way it is suppose to work?

Are the other 3 grouptask members are having 'master' role?? If yes, then answer to your query would also be Yes.

If not, then as per me... i could not see any reason as why anyone of the other 3 can approve / reject the content.

Bhargav Coca

Trun on your workflow debugger and see the flow? if you say that you didn't take the task, then you should automatically be an owner for that approval task? see if your debugger shows you as owner of that task.

Thanks

Migrateduser

maybe you misunderstood my question. Someone else in the group took ownership of the task. Why am I still able to approve or reject the task? Is it because i am defined as a master administrator?

Adam Stoller

maybe you misunderstood my question. Someone else in the group took ownership of the task. Why am I still able to approve or reject the task? Is it because i am defined as a master administrator?

If you have the ability to login as a Master user (pre-6.7.1) or have Master privs for the branch associated with the workflow (6.7.1+) then, I believe by default, you have the ability to act on tasks without necessarily taking ownership of them.

It also used to be the case (and perhaps still is) that the job owner / creator could act on tasks without being owner.

If you're trying to test stuff - do so with accounts that do not have master priv's.

nipper

Is there a reason you asked the same questions and received the same answer a couple weeks ago ?

Migrateduser

wow, my bad. this old age thing is killing me. too many projects going on at one time.