Change models

[joshmorris]

Hi all,

Currently we don't use change models and wondering what the benefits are of migrating over. We have a change approval lookup table and assign approvers based on the sub category of the change. How would this change with change models and would we still need it?

[Dr Atul G- LNG · Accepted solution]

Hi @joshmorris 

Yes, there are many benefits to using the Change Model. We have been using Change Models for a long time now, and the best part is that they are fit for purpose and fit for use. This approach allows you to build a Change Model for any type of change, such as application or infrastructure changes.

Change Model

ServiceNow introduced Change Models to enable a fit-for-purpose and fit-for-use approach to change management.

Previously, all changes of the same type followed identical approval paths and processes, regardless of what was being changed—whether an application, network, or server.

Change Models introduce flexibility by allowing:

• Different approval workflows

• Different task structures

• Different automation

These variations can be defined based on the CI, CI class, or business context.

[Dr Atul G- LNG]

https://youtu.be/UV_Tac-AVDw

[Dr Atul G- LNG]

Hi @joshmorris 

With Change Models, you may need to adjust the approval workflow. However, if required, you can simply add conditions to the approval rules—for example, if the model is X and the category is Y, then those specific approvals must be applied.

[its_SumitNow]

Hi @joshmorris 

Change Model is the OOTB functionality for controlling change workflow

Majorly Transitions are being controlled via change model,

Proceeding further we have Change Approval policies, for generating requests,

It get's very simple for us to control the change flow 

 Best practice is to prefer Configuration over High Customization

if any help needed in any use case you can ask your doubt

if my response helps ,kindly mark it helpful & accept as solution 🙂

Warm Regards

Sumit

Technical Consultant