Multiple Authors Approval WorkFlow

Hi,
The scenario of the Workflow which I am trying to implemet is:

There are multiple authors who edit a DCT. For example 2 Authors edit a DCT and send it for approval to 1 Approver. The Approver in the workflow wants to approve the work done by Author 1 and reject work done by author 2. So the approver should have 2 checkboxes with the author names alongside, of which 1 he can approve and 2nd he can reject. Now individual mails are sent simulatneously to the authors. For 1 author its rejection and the 2nd author its approval.

Has anyone done such kind of a workflow. If yes pls do help and if possible attach a sample wft file.

Thanks and Best Regards
Abhi

Find more posts tagged with

Comments

Adam Stoller

Is it possible - yes, but it might take a bit of implementation...

Assuming the 2 authors are chosen during instantiation time (i.e. via TAG_Info() fields) - you can have the Review task take multiple successorsets:

1) Approve Both
2) Approve userA - Reject userB
3) Approve userB - Reject userA
4) Reject Both

The values for userA and userB would come from the values selected during instantiation.

Each of the successorsets would then transition to *their own* externaltask to perform notification (so that the message is correct for the recpients), and then transition from there to wherever is appropriate.

My recommendation - draw it out carefully on paper / white-board or using something like Visio (stencils available to assist with the latter on this site) - then, and only then, start coding the wft.

--fish
(Interwoven Senior Technical Consultant)

abhishek_gupta

Hi,
Thanks for the reply.
What if there are about 10 authors working on a single DCT and sending it for approval to a single Approver(Editor). The Editor can Approve or Reject any one of those 10 authors in 1 workflow. So in such a case, having so many permutation combinations would be difficult.
Is there a simpler way out.
To make the problem easier to understand...the DCT is kind of a Newsletter where 10 authors enter content in seperate containers and send it for approval to 1 editor.

Any solution...?

Regards
Abhi

Adam Stoller

I'd recommend figuring out a way to break the newsletter into separate DCRs representing "columns", with perhaps a common field (e.g. Publication Date) that can be used afterwards to tie them together. This way (a) you can have the authors work in parallel, (b) the workflow for each "column" is far simpler than what you were originally thinking of.

--fish
(Interwoven Senior Technical Consultant)