Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Workflow - Approve, Modify and Reject Dispositions

Status
Not open for further replies.

oscript

Programmer
Mar 25, 2003
63
GB
Hi,

I have a fairly straight forward workflow where a document is routed through a workflow approval process. The disposition is as above - Approve, Modify and Reject with Modify (return to user to modify) is the default. The approval process includes a parallel step to three user groups concerned with the approval process (all three have to approve for the document to be published). Any or all can reject or ask for modification of the document.

My question is how can I best achieve a situation where if one or more of the approval groups 'Reject' the document the task disappears from the assignments of the remaining two groups of users - and of course the document is moved to a rejected area ?

Grateful for any ideas
 
post your map just the problem you are trying to get help with.I assume you know how to create a simple map and export

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010
 
I will do that tomorrow AM when I can access the server :).

In essence if you imagine a simple step that has three parallel branches to group A, B and C where all three need to be completed before the next step is reached. What I would like to do is to move the step on if one branch is marked as 'Reject' with the other two remaining unanswered.

Start >
Group A Approvers - Approve, Reject or Modify
Group B Approvers - Approve, Reject or Modify
Group C Approvers - Approve, Reject or Modify
> End Step

If Group B rejects then I would like the step for Groups A and B (assuming not completed) to be auto completed and for the document to be rejected. The usual behaviour would be for the three steps to have to be completed with a disposition BEFORE the End Step is reached which I would like to avoid if possible.

Steven
 
Thinking loud about this with oscript in mind.When one of the 3 branch steps receives a action in "Step Done" would not you be able to key off that and render the other steps done?Otherwise if you have XMLWFExtensions think of attcahing a "timer event" with each of the 3 branches.I have not worked in that but the concept is the timer event is watching for what happens only in that branch,so it wakes up looks for an intersting event and if it does not find it goes to sleep.I think you may be able to "kludge" something with that.

Or you could with the 3 group parallel steps have a WFattribute of form attribute to be made mandatory.So if somebody says "Reject" then this flag is on.Then using an external process you could monitor this flag and do things like what you had in mind.I would probably look for a lapi/oscript/websvcs method to kill the other steps.

One thing is that assignments sitting in the other two groups are duds but don't think they can be pulled back after all email notifications would have gone out and if they click it they will get "this workflow step is no longer active" something like that.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top