Force completion of parallell review task by manager
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2012 05:04 AM
How can you give authority to a manager to say that the parallell review task should be considered complete?
Flow is something like
The "Manager Task" is not there yet, but to illustrate what I need to achieve. At some point the Manager can decide that the parallell reviews performed so far is enough, and those reviewers that are slacking missed there chance.
So how can I do this? Is it a separate manager task, that somehow signals to the review task that it is all complete? But then preferably if Review is 100% complete, then Manager task should complete itself (there is nothing to decide about, since review task is complete by all reviewers).
Any other way to do this?
Flow is something like
Start—Pre-Task—Parallell Review—Completion Task—End | | —ManagerTask—–
In the parallell review task I have reviewers that all (as in 100%) have to complete the review task to move to completion task (performed by one assigned individual).The "Manager Task" is not there yet, but to illustrate what I need to achieve. At some point the Manager can decide that the parallell reviews performed so far is enough, and those reviewers that are slacking missed there chance.
So how can I do this? Is it a separate manager task, that somehow signals to the review task that it is all complete? But then preferably if Review is 100% complete, then Manager task should complete itself (there is nothing to decide about, since review task is complete by all reviewers).
Any other way to do this?
Labels:
- Labels:
-
Archive
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2012 05:46 AM
Well in this case I see two ways to do that.
1) you can have two parallel tasks one which go as the parallel review which assign to all the group users.
other is manager review task.
If any one of the task gets completed first it will move workflow to the next stage.
The pending one should get cancelled in that case.
2) the other way is just in each approve it will go though the decision node where it will check the current user if it a manager then it should move to final review other wise continue the normal process.
1) you can have two parallel tasks one which go as the parallel review which assign to all the group users.
other is manager review task.
If any one of the task gets completed first it will move workflow to the next stage.
The pending one should get cancelled in that case.
2) the other way is just in each approve it will go though the decision node where it will check the current user if it a manager then it should move to final review other wise continue the normal process.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2012 06:04 AM
Well in this case I see two ways to do that.
2) the other way is just in each approve it will go though the decision node where it will check the current user if it a manager then it should move to final review other wise continue the normal process.
Thanks, number 2 can be the way to do it. Right now I have
<completionCondition>${wf_approveCount == wf_reviewerCount}</completionCondition>
If I add the manager as reviewer, and change the completeCondition to be wf_reviewerCount -1, that way if all the standard reviewers complete the reviews it will continue without the manager needs to take action. On the other hand, if the user that is in the manager role completes his/her review task before all the reviews are finished, I can just upp the number for wf_approveCount, and the wf will continue to next task.Implementation details has to be thought of, but in this way it is solvable I think.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2012 02:58 AM
The other way around is you can add Decision manager class in the workflow.
So that class will be called in your decision node.
There will be three possible conditions.
1) Approved by all approvers.
2) Not Approved by all the approver.
3) Current Approvee is manager.
For 1st and 3rd condition it will return flag1 as true
For second condition it will return flag2 as true.
Then in decision node if flag1=true. move to approved.
If flag2=true continue the approval cycle.
This looks like the best approach.
So that class will be called in your decision node.
There will be three possible conditions.
1) Approved by all approvers.
2) Not Approved by all the approver.
3) Current Approvee is manager.
For 1st and 3rd condition it will return flag1 as true
For second condition it will return flag2 as true.
Then in decision node if flag1=true. move to approved.
If flag2=true continue the approval cycle.
This looks like the best approach.
