Optional Further Approval

Hi,

I need to implement a workflow template where the approvers needs a checkbox on their template GUI which they can check if they cannot approve and they want to send the same content for further approval, and if thats get approved the content gets submitted. And if they let the checkbox remain un-checked then it can directly go for submit operation.

A situation something like this : The contributors contribute content using teamsite templates and then send it for approval to their editiors. Now the editors want an checkbox on thier workflow template screen wherein they can check if they are not in a position to approve and they want to send them for further approval to their managers.

Is to possible to do something like this? Can I have a sample workflow template which does similar to this. Can configurable workflow help me ?

regards
Sunil

TeamSite Consultant

Find more posts tagged with

Comments

abhishek_gupta

This is possible easily in the wft. You just have to have a 'if loop' in the templatescript for the checkbox, and on check or uncheck of the checkbox the respective successor tasks should be given.

AK
Interwoven Consultant

jbonifaci

I believe you're saying that the person that kicks off the workflow is NOT the person who is picking this optional approval task, is that correct? If so, the easiest way to do this would be to have two approval transactions for your 'editor'. Name them something like "Approve - Submit" and "Approve - Needs Further Review". If the editor transitions the task and selects the first, it transitions to your submit task. If the editor picks the second, it transitions to a cgi task that allows the user to pick the additional approver and then transitions to the additional approval task.

You could also just have the editor task always transition to the cgi task and handle everything there. But then the editors have to deal with the extra step every single time.

Hope this helps,
Jeff Bonifaci

sunil_j

Hi A_G,

I never realized that *IF* statement is a *loop*. I would rather prefer to use the term *if statement*.

Cheers
Sunil

TeamSite Consultant

Adam Stoller

If you're dealing with a serial approval process - then the suggestion made for the cgitask to prompt for, and then reset ownership on the review task makes sense - you'd probably also want to make use of something like iwsend_mail's ability to use task-level variables for email recipients and have the same code that sets the owner of the review task also alter the task-level variables for the notification steps.

I did this once with an arbitrary number of concurrent reviewers using a wftask and cgitasks combined - but unfortunately don't remember all the details and don't have time to dig them up right now. It went something along the lines of initiate a new workflow which has a TAG_info() prompt for requesting the *number* of reviewers - having the wft dynamically generate the review (and auxilary tasks like notification) tasks, and then have the first task be a cgitask owned by the same user - which prompts for the names and then performs all the ownership assignments before farming out the review requests.

Hope that helps

--fish
(Interwoven Senior Technical Consultant)