What's the official "best practice" guidance when it comes mixing approval policies with user and group approval blocks in a workflow? Should a customer strive towards converting everything to an approval policy, or is it acceptable to convert some and leave some in the existing user/group approval form?
Also, is it "best practice" to have a single approval policy stand for a single change type, or can you have multiple approval policies for a single change type.
In Madrid, I have a requirement where I'm trying to do three approvals for a Normal Change Request:
First Level Approval (Assess state) Assignment group's Manager can approve or reject Required for all Risk levels
Second Level Approval (Authorize state) Applications CAB can approve (single vote) or reject (single vote) Required if Risk is 1 to 4 AND Configuration Item is an Application
Third Level Approval (Authorize state) Enterprise CAB can approve (single vote) or reject (single vote) Required if (Risk is 1 to 2) OR if (Risk is 3 and CAB Required is true)
I can see the value of using Approval policies for the first approval as there is a state change of "Assess" to key off of to fire the first approval. For the second and third approvals, they are spawned together because I have no state change between the second and third approvals. If I want second level approval to be completed before the third level approval is fired, then I don't see a way to accomplish this without splitting up my approval policy into two elements.
