The whole objective of emergency approvals is to bypass the ASSESS state (peer review) and go straight to the AUTHORIZE one. This is why the first activity says "change moves to Authorize". I can see you modified that.
For what you are trying to do you are much better off to copy the "change request - normal" workflow that has the assess and authorize approvals. Then you go into the properties of that workflow, change the name and conditions to make it trigger when you create an emergency change. You will also have to change the two change approval policy activities to point to the right change approval policy and definitions.
The answer will depend if you are using the legacy change TYPE or the new change MODEL.
Change TYPE (normal, standard and emergency) does use an out of box workflow that you mostly want to keep that way (not customized). Change MODEL does not use a workflow anymore.
But in general terms you should handle these requirements through change approval policies. Step 1 and 3 are already happening through change policies.
In order to figure it out, go to workflow editor and type "change". Then open the "change request - normal" and double click on "change approval policy - Risk approvals". You will see the code below where they are trying to figure out if the manager of the current assignment group already approved the change. If that happens then the variable (policy input) manager_approved = true. Then they use that input on the "normal change policy" (screens below).
In your case, you have to go to the "change request - emergency" workflow, check it out, double click on the "change approval policy - CAB approval" activity and configure the necessary logic for your inputs that you will use later on the "Emergency change policy".
Hi @Sebas Di Loreto ,
I have used the Emergency workflow here and the requirement is
1) Fill all the fields in a form and click on save, it is in new state. Once clicked on request approval button it should move to Assess state. (Till here it is working as per expectations)
2) When state changes from New to Assess, it should show approver group "configuration_item.support group."
I have created "Change approval policies" and "change approval definitions" and added this condition in the decisions and all but currently this is the issue that is happening.
Please check the image below:
Thank you!!!
The whole objective of emergency approvals is to bypass the ASSESS state (peer review) and go straight to the AUTHORIZE one. This is why the first activity says "change moves to Authorize". I can see you modified that.
For what you are trying to do you are much better off to copy the "change request - normal" workflow that has the assess and authorize approvals. Then you go into the properties of that workflow, change the name and conditions to make it trigger when you create an emergency change. You will also have to change the two change approval policy activities to point to the right change approval policy and definitions.
