We have a couple of circumstances where the approval for a Change, Service Request, etc... needs to shut down if any one person declines, but NOT require EVERYONE to approve to move forward.
For example, if we have an Emergency Change that requires the approval of the CTO or CIO, then it will be considered APPROVED if only the CTO approves, even if the CIO DECLINES. However, we don't want to set the Emergency change to Require they BOTH approve, to move it forward (they both may not be available).
So we would want something like this:
Approvers: All, 50%, or One
Decline if: All, 50% or One.
Another example. We may have a Change that could impact 8 departments, so we put all 8 up as approvers for visibility. All 8 personnel may not be available to APPROVE the change, so we can't set it for ALL Approvers. Setting it for 50% and DECLINE on 1, would be ideal.
|What problem will this feature solve?:|
Allow more flexibility with approvals. They are currently too constrictive and require so much OUT OF THE APPLICATION work to make sure they aren't missed, or that one doesn't proceed if any ONE party says it is an issue.