- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2024 07:45 AM
When I am looking at Emergency change's the process flow is going from New when I save it to when I click Request approval it's skipping Assess and marking it complete and then going directly to Authorize. We don't want this to go to Authorize until after assess has been looked at.
Does anyone know how to fix this so it doesn't jump forward?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2024 07:50 AM
@Community Alums The change model for Emergency change follows ITIL and hence from the new state it moves directly to authorise and skips Assess phase.
Here is the OOTB change model in ServiceNow.
Here is the URL for your reference https://docs.servicenow.com/bundle/vancouver-it-service-management/page/product/change-management/concept/c_ChangeStateModel.html
If you wish to make your change go through Assess phase, then you should create a Normal change instead of the emergency change.
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2024 07:51 AM
Hi @Community Alums
As per ITIL and OOTB ServiceNow configuration, emergency changes did not go for Assess .. It goes to Authorize state directly, bcz If it go for assess the change may delayed due to multiple approvals , which cant be a good case. So as per best practice Emergency change also goto the Authorize state.
Please
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2024 07:50 AM
@Community Alums The change model for Emergency change follows ITIL and hence from the new state it moves directly to authorise and skips Assess phase.
Here is the OOTB change model in ServiceNow.
Here is the URL for your reference https://docs.servicenow.com/bundle/vancouver-it-service-management/page/product/change-management/concept/c_ChangeStateModel.html
If you wish to make your change go through Assess phase, then you should create a Normal change instead of the emergency change.
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2024 07:51 AM
Hi @Community Alums
As per ITIL and OOTB ServiceNow configuration, emergency changes did not go for Assess .. It goes to Authorize state directly, bcz If it go for assess the change may delayed due to multiple approvals , which cant be a good case. So as per best practice Emergency change also goto the Authorize state.
Please
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2024 07:54 AM
Hi Stephen,
That is an expected behavior for Emergency change type. Refer doc link.
In case you wish to edit then you might need to update Script Include ChangeRequestStateModel_emergency to be bit inline with ChangeRequestStateModel_normal.
