Instantiating Workflow

Lets say we have one workflow consisting of two groups of tasks. The first group of tasks are strictly for content developement and the second group of tasks are for legal matters. Lets say an author creates a content item and it is reviewed by two managers. After both managers approve the content, it is then sent to the legal department/ branch where an attorney wants to assign two paralegals to review the content before he approves it. It is my understanding that all of these assignments would have to be done when the workflow is first instantiated. This is an issue b/c a content manager would not/should not know anything about the para legals being assigned to the workflow. Is there a way to give the attorney the option of choosing which para-legals when the task reaches him?

Find more posts tagged with

Comments

nipper

I assume you are talking TeamSite here, not WS. You do not mention what version of TS you are using, that will help.

It can be done, though it is certainly NOT trivial.

One possible solution (not exact to your specs) is that you have a group task for the review that all paralegals are a member of. In a previous task, you would email ONLY the paralegal assigned to it to work on the task. Again, not perfect but close to your functionality.

The best solution is to create a child workflow job for the approvals. This can be instantiated in the middle of the main workflow with the appropriate reviewers. This will meet your objectives, but if you have not done child workflows, it can be a challenge.

HTH

Andy

Adam Stoller

I assume you are talking TeamSite here, not WS. You do not mention what version of TS you are using, that will help.

It can be done, though it is certainly NOT trivial.

One possible solution (not exact to your specs) is that you have a group task for the review that all paralegals are a member of. In a previous task, you would email ONLY the paralegal assigned to it to work on the task. Again, not perfect but close to your functionality.

The best solution is to create a child workflow job for the approvals. This can be instantiated in the middle of the main workflow with the appropriate reviewers. This will meet your objectives, but if you have not done child workflows, it can be a challenge.

HTH

Andy

It could also be handled with a CGI task that is assigned to the person who would delegate the reviewers for the latter part of the process - and then in the CGI script you could re-assign the ownership of the review tasks as desired. Less messy (IMO) than a nested workflow.

encrypt_decrypt_params.jpg

kaalraa

Lets say we have one workflow consisting of two groups of tasks. The first group of tasks are strictly for content developement and the second group of tasks are for legal matters. Lets say an author creates a content item and it is reviewed by two managers. After both managers approve the content, it is then sent to the legal department/ branch where an attorney wants to assign two paralegals to review the content before he approves it. It is my understanding that all of these assignments would have to be done when the workflow is first instantiated. This is an issue b/c a content manager would not/should not know anything about the para legals being assigned to the workflow. Is there a way to give the attorney the option of choosing which para-legals when the task reaches him?

Before going to para-legals, provide a task to attorney who selects the legals and in turn mail them about the task assigned.