1 of 1 people found this helpful
There is no support for parallel approvals with the current version of Process Designer. You would need to define a branching condition so that only one of the approvals is assigned.
Thank you for the answer!
This is too sad. And there is no group approval as well, isn't it?
So I need an advice in what should I do if I need a group approval or a parallel approval in my process?
Alexander, Sorry but you cannot use Process Designer for group or parallel approvals with the current release but we have raised an enhancement request to address these limitations.
So - this post means that you can only have ONE approval process per PD Process??
If you have an approval in a sub-process, can you have a secondary one?? As the first approval is not, technically, in the parent process.
.. but I imagine, when it builds, the sub-process is embedded??
What I am getting is:
1) Create a task to call the sub-process (which includes an approval)
2) If that sub-task approval is "approved", follow a defined flow. Alternately, follow a secondary flow if the approval (from the sub-process) is rejected.
Note that in the "Approved" flow - there is another request for a secondary approval.
What I am getting is - no matter what the approval result is in the sub-process, both flows are being fired. AND - the secondary approval is just being "completed" but not actually built/run (no secondary approval is actually being created).
PS> We are using Remedy 7.6.04 and PD 8
Tamara – I think what you have described should be ok – the limitation is on running two approval actions in parallel (at the same time). There is no limitation on the number of approval actions in the process so long as they are not running in parallel. Mark
Thanks for your quick reply Mark! So - sequenctial approvals should be ok?
Ours isnt working - no log errors in Process Designer or DB. Whenever I save the process, it strips out the decision conditions:
See how the conditions were stripped?
Note: I built this sample to test the multiple approval theory - as our other process that I described above is a little more complex. Here is what the snippet of the actual process I am building:
Based on what you are suggesting - this should work??
Tamara – the only possible outcomes from an Approval step are Approved or Rejected. These are automatically set based on the Assignment Rule on the Details tab of the task immediately following the Approval task. So in your process you should check the Assignment rules on the tasks called Notify of Rejection and Create INC. If these are set correctly then the dependency lines will automatically be set to approved or Rejected accordingly. Mark
Lightbulb!! Ok - this makes sense.
If an approval is set into "More Information" status, will the process wait until the final outcome of the approval is approved or rejected?
Tamara – yes it will wait until that step is either Approved or Rejected. Mark