Questions about this new behaviour:
![]()
Does this apply to staged approvals? What if we require multiple people at the same level to approve?
- If any one of the approvers approve the Incident approval, the status of the Incident Request would be set to approved. Yet, the other approvers would have been able to register their recommendation on the approval. Now, once the Incident Request is approved by any one of the approver, the other approvers won’t be able to register their action or recommendation on it, since the Request is already approved.
I tested this in both a Incident and Service Request template and both behave the same:
Incident -- 2 approvers, same stage
- first person approves it
- second attempts to review and gets this helpful error :/
Service Request - 2 approvers, same stage
![]()
![]()
SD 9302 Enterprise
MS SQL
-------------------------
Ottawa - Canada
- first person approves it
- second attempts to review and gets this useful message
My question is how is this any different? Some of our processes involve have multiple sign-off/collaborate on requests before the tech can proceed. Do we now have to organize these reviewers into stages to accomplish our approvals?
Also the function that a request only requires one approval is flawed -- we'd like to have a request set in 'pending approval' until all Approvers have approved the request. I thought this was accomplished via a service request:
MS SQL
-------------------------
Ottawa - Canada