Yes, this should work if the "Deny" flow path does not skip the 3rd

You might want to double-check what happens when the first admin presses
"Deny" on the external interface and verify the APIs used.
Each approval step should have a unique work id.


On 04.05.2012 15:16, stavae wrote:
> I was thinking --- what if I modify my workflow, so that : after the
> "First" and "Second" Approvals, *_BOTH__* the _approve_ and _deny_
> flow-arrows will always continue to the next Approval ??
> In other words : after First Approval, whether or not the action is
> "Approved" or "Denied", the process moves forward to the Second
> Approval, etc, etc