Stopping/Completing a workflow in code

Hi, I posted this in the Builder discussion but figured it was worth a try popping it in here too.We have a number of workflow maps in our system that require multiple approvals of a document before it is then PDFd and stamped. Each approval step is configured in parallel and point to a single step to check of all dispositions and progress if they are all approved (see the attachment).The some senior users are not happy that they approve a document then to find that one of the others did not. They have to redo the approval again which bothers them.As I can't see a way of killing the other approval steps once one rejection has occurred I thought of using code to do this in an event script (or similar), specifically $WFMain.WAPIPkg.SetWFStatus. Has anyone found any problems with this? Are there better methods of achieving my goal?Thanks in advance for any reponses,Phil F

Find more posts tagged with

Comments

David_Spirhanzl

Message from David Spirhanzl <David.Spirhanzl@syconix.cz> via eLink

eLink

Hi Philip,

what about placing a Evaluate step in front of each Approval-UserStep. Then during the next circle you can filter out the people that previouslyapproved the document.

Or is there any other consequence?

David

SYCONIX, a.s.

Czech Republic

From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]
Sent: Friday, April 03, 2009 11:30 AM
To: eLink Recipient
Subject: Stopping/Completing a workflow in code

Stopping/Completing a workflow in code

Posted by philipforshaw (Forshaw, Philip) on 2009/04/03 05:26

Hi, I posted this in the Builder discussion but figured it was worth a try popping it in here too.

We have a number of workflow maps in our system that require multiple approvals of a document before it is then PDFd and stamped. Each approval step is configured in parallel and point to a single step to check of all dispositions and progress if they are all approved (see the attachment).

The some senior users are not happy that they approve a document then to find that one of the others did not. They have to redo the approval again which bothers them.

As I can't see a way of killing the other approval steps once one rejection has occurred I thought of using code to do this in an event script (or similar), specifically $WFMain.WAPIPkg.SetWFStatus. Has anyone found any problems with this? Are there better methods of achieving my goal?

Thanks in advance for any reponses,

Phil F

Attachment Links:

parallelSteps.JPG (20 KB)

[To reply to this thread, use your normal E-mail reply function.]
Discussion:	Development Discussion
Livelink Server:	knowledge-wlweb01

To Unsubscribe from this Discussion, send an e-mail to unsubscribe.development@elinkkc.opentext.com.

Philip Forshaw

Message from Philip Forshaw <philip.forshaw@res-ltd.com> via eLink

eLink

David, we need to know for the audit trailthat the Approvers approved the final document, removing them from the list ofapprovers in the next round of approving would not give us this. Thanks for theidea though

PhilF

CONFIDENTIALITY NOTICE: This e-mail, including any attachments, contains information that may be confidential, and is protected by copyright. It is directed to the intended recipient(s) only. If you have received this e-mail in error please e-mail the sender by replying to this message, and then delete the e-mail. Unauthorised disclosure, publication, copying or use of this e-mail is prohibited. Any communication of a personal nature in this e-mail is not made by or on behalf of any RES group company. E-mails sent or received may be monitored to ensure compliance with the law, regulation and/or our policies.