Take back task greyed out

Hello all,

We upgraded TS to 6.7.1 and Take back task under actions is grayed out so approvers can’t take ownership of the tasks. Does anyone have any suggestions please?

Thank you.

Find more posts tagged with

Comments

Adam Stoller

Hello all,

We upgraded TS to 6.7.1 and Take back task under actions is grayed out so approvers can’t take ownership of the tasks. Does anyone have any suggestions please?

Thank you.

You're not providing enough context about your WF

There may be other questions but those two will help for a start.

gpfsmurf

It's a WFT workflow.
The current task is a grouptask, and the next task is an external task.

The approver (who is also a master) cannot take ownership of the task. The "Take task" link doesn't appear below the owner field, and the "Take back task" menu item is grayed out under Actions. The current owner is "no user", which is normal.

It's on Solaris, and the issue arose after upgrading from 6.1sp2 to 6.7.1sp1

Thanks for your help

Adam Stoller

It's a WFT workflow.
The current task is a grouptask, and the next task is an external task.

The approver (who is also a master) cannot take ownership of the task. The "Take task" link doesn't appear below the owner field, and the "Take back task" menu item is grayed out under Actions. The current owner is "no user", which is normal.

It's on Solaris, and the issue arose after upgrading from 6.1sp2 to 6.7.1sp1

Thanks for your help

If the next task is an externaltask - you generally will only have a small window of opportunity to take the task back from the externaltask to the grouptask - so having take task back being greyed-out is normal under that circumstance.

The "Take task" link for the grouptask is a different issue - for that you need to look at the sharedby element for the grouptask and make sure that the users / groups referenced there are still applicable on your upgraded system

gpfsmurf

The "Take task" link for the grouptask is a different issue - for that you need to look at the sharedby element for the grouptask and make sure that the users / groups referenced there are still applicable on your upgraded system

The sharedby element is valid and has the user in question in the list.

I also noted that using iwtaketask from the command line works

Do you know any other possible source of the problem?

Adam Stoller

The sharedby element is valid and has the user in question in the list.

I also noted that using iwtaketask from the command line works

Do you know any other possible source of the problem?

Without actually sitting in your environment and looking at the problem, I'm not sure what else I can suggest as ideas besides: Contact Support

Sorry

gpfsmurf

Will do

Thanks for your help