VaranAwesomenow
Mega Sage

 

This article is to implement two levels of approval sequentially during authorize phase for a change request as part of change management process.

Code : anilvaranasi/Custom-CHG-Approval

 

Normal change management process flow as per ServiceNow best practices provided in nowcreate process guide. I have added some now create content screenshots to set the context and background on what is offered OOB and how to implement this requirement of multiple sequential approvals. Actual solution details are covered as we navigate along the article.

 

VaranAwesomenow_0-1745305911950.png

VaranAwesomenow_6-1745305911968.png

 

 

Implement Business owner and IT owner approval as sequential approvals 

Change requests should go through two levels of approval sequentially during Authorize state, first level will be IT application owner, and second level will be application platform owner. 

VaranAwesomenow_37-1745305965770.png

 

Customization needed: Create following objects meet this requirement 

  1. Deactivate OOB flow -> Change - Normal – Authorize 
  1. Create new flow -> Change - Normal - Authorize Two Level Approval 
  1. Deactivate OOB approval policy , policy decision -> Requires CAB Approval 
  1. Create two new answers 
  1. Change Approval Definition: Authorize Platform owner Approval 
  1. VaranAwesomenow_38-1745305965772.png

     

     
  1. Change Approval Definition: Authorize Application owner Approval 
  1. VaranAwesomenow_39-1745305965773.png

     

     
  1. Create two new policy decisions 
  1. Requires Application Owner Approval and associate answer as Change Approval Definition: Authorize Application owner Approval 
  1. VaranAwesomenow_40-1745305965774.png

     

     
  1. Requires Platform Owner Approval and associate answer as Change Approval Definition: Authorize Platform owner Approval 
  1. VaranAwesomenow_41-1745305965776.png

     

     

Once above setup is complete on a given change request when the state is in authorize, two levels of approval will get triggered sequentially, first level approval will be application owner and second level approval will be platform owner. 

Testing 

Test Service AMEA Customer Portal, where Level1 -> IT application owner -> Managed by -> Abraham Lincoln and Level2 -> Platform owner -> owned by -> Abel Tuter 

VaranAwesomenow_42-1745305965777.png

 

 

Create new change with service as test service 

VaranAwesomenow_43-1745305965777.png

 

 

Request approval on assess state approvals get set to assignment group (this is OOB no change is done) 

VaranAwesomenow_44-1745305965778.png

 

 

Approve the change request. 

Once change moves to authorize then level1 (IT application owner , Abraham Lincoln approval will be triggered) 

VaranAwesomenow_45-1745305965780.png

 

 

Once approved as Abraham Lincoln, second level approval Platform owner -> owned by -> Abel Tuter is triggered 

VaranAwesomenow_46-1745305965781.png

 

Once approved change moves to scheduled state 

VaranAwesomenow_53-1745306039830.png

 

 

Below is the flow execution for above change 

VaranAwesomenow_54-1745306039832.png

 

 

Comments
David Nottingha
Kilo Sage
Kilo Sage

This is nice but there are no details on the Flow Designer flow - Can you share what you changed in the flow to enable to two stage approval?

VaranAwesomenow
Mega Sage

ty @David Nottingha  for the feedback I will update the relevant details, but if you would like to look at the code, i have added link to the scoped app anilvaranasi/Custom-CHG-Approval

 

 

 

Version history
Last update:
‎04-22-2025 02:09 AM
Updated by:
Contributors