Stopping/Completing a workflow in code

Hi, 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 though 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

John W. Simon, Jr.

One problem I can see...if I am a reviewer and I have notifications turned on, I get an assignment and an email telling me about it, somebody else rejects, so you kill my step, I get an error when I click on the link in my email.We have something close...We have a list of reviewers in parallel as you describe. If any one of them rejects the document it goes back to the initiator to fix. Then when coming back thru for review, our requirement was that anyone who previously approved does not have to approve again (so skip them the 2nd, 3rd, etc... time thru).In our case we had a form driving the process (but attributes would also work). Basically each reviewer had an attribute (true/false) that was used to decide if the reviewer needed to review. Then we set the true/false appropriately based on the previous review.part of the code we used below (wfDispositionData contains the users actions for each step)...// get the form data.dynamic formObject = $WFMain.WFPackageSubSystem.GetItemByName('Form')dynamic formData = formObject.LoadWorkData( prgctx, work, workid )// get the disposition datadynamic wfDispositionData = $WFMAIN.WAPIPkg.GetDispositionData( prgCtx, workid )// get the task status datadynamic wfTasks = WAPI.LoadTaskStatus( prgCtx.wSession().fSession, workid )// manipulate the form data here...// update the form with the new datadynamic formUpdate = formObject.SaveWorkData( prgctx, work, undefined, formData )

Philip Forshaw

John I agree that the error is not ideal, but we can't use your method (a good idea by the way) because we need approval of the final document by all.I'll set up some test workflows and see what happens when I kill the steps/workflow. If anything useful comes out of it I'll post it here.

John_Underhill_(john.underhill@cgi.com_(Delete)_24

Did you get anywhere with this? I have a similar requirement in that one branch of a workflow (snooze/alarm loop) needs to kill the other branch (waiting), then complete and end the workflow. i.e. I want the snooze/alarm loop to stop the whole process if the users chooses.

My thoughts so far were to $WFMain.WAPIPkg.SetWFStatus to WAPI.WORK_STATUS_STOPPED or do WAPI.StopWork, but this causes a SQL error on WLOCK table.

Next I thought to set a WF Attribute and send on the waiting step to make the decision to die.

I might be able to make the waiting step complete and let WFAgent move it on?

Anyone any thoughts ... one branch kills the workflow or the other branch.