You can use a custom field on the previous Task Screen set, say a CAB Approval to have a Search Field (Single) that can be selected manually. This can then be used for the assignment of the next (or other tasks) in the workflow. Alternatively you can also use Stakeholders on a Service or Configuration Item to steer the assignments further on in the workflow.

Hi Clive,

I don't know if this is of any help to you, but we have similar on our Project Request, we don't know at the point of logging who will need to be involved.

We have an initial review task and on there I created a custom multi field for support teams, the project team can pick all the teams they want to be involved in reviewing the project. Then on the task that follows (for actually reviewing the project) I assigned the task to that field - it creates a task for every team that was picked. You do need to leave a fair amount of blank space for these tasks to appear into depending on how many you might think will be needed. Not sure if would work for your request it sounds a bit more complicated than mine but might be worth a try.

Thanks Ken, very much appreciate your response but your suggestion does not meet our need. What we need is to be able to assign Tasks 'dynamically', and as the workflow progresses. This requirement is within our Change Management process which has a generic workflow and so, dependent on the reason for the change and the teams involved, we may have various specialists/experts who may need to comment on/fulfil a Task pertinent to a given change. We cannot and do not know who (or which team) will be responsible at the inception of the change workflow.

Tasks can be assigned to Individuals or groups using the assign option when creating the workflow.

Each task in the workflow can be assigned to the correct support team or analyst for that task automatically by predefining where it is to be assigned once activated.

If assigned to a group, all members of that group can then take ownership of the task. Once ownerrship is taken, the task dissapears from the group view and it's owner is changed to the analyst that has taken ownership.

Is this what you were looking for?