The Zurich release has arrived! Interested in new features and functionalities? Click here for more

Change Model Condition Types in ServiceNow

Varshini_Kasula
Tera Contributor

ServiceNow provides Change Model Condition Types, which are used within Change Models to control state transitions based on specific criteria. This ensures that changes follow proper governance and only move forward when predefined conditions are satisfied.

 

Purpose of Condition Types

Change Model Condition Types are applied to state transitions in a Change Model. They help enforce rules, such as preventing a change from moving to the next state until certain conditions are met.

For example:

  • A change cannot move from ScheduledImplement unless it is not On Hold.
  • A change cannot move from Authorized → Scheduled (Emergency)  unless Unauthorized is false

This approach reduces the need for scripting and allows administrators to manage conditions through configuration.

 

Navigating to Condition Types

You can find the OOB (Out-of-the-Box) condition types in ServiceNow by navigating to:

Change > Administration > Change Model Condition Types

 

            Varshini_Kasula_1-1758289633853.png

 

OOB Condition Types

By default, ServiceNow provides two condition types:

  1. Authorized
  2. Not On Hold

 

           Varshini_Kasula_2-1758289660022.png

 

For example, if you open the Not On Hold condition type, you will see how it ensures that state transitions are blocked whenever the change is on hold.

 

         Varshini_Kasula_3-1758289936254.png

 

Example Scenarios

There are situations where additional conditions may be required. For instance:

  • In Scheduled → Implement and Implement → Review transitions, you might want the On Hold status to be checked.
  • This can be achieved by adding condition types that validate the On Hold field before allowing the transition.

Instead of writing custom scripts, administrators can configure these conditions directly through Change Model Condition Types.

 

Key Benefits

  • Reduces scripting by leveraging configuration.
  • Improves governance by ensuring consistent rules across change processes.
  • Flexible – allows both condition-based and script-based validation if needed.

👉 You can also add the condition type either by defining conditions or by using a script, depending on your requirement.

 

With this, you can easily extend or customize Change Models by defining new condition types as per your business requirements.

0 REPLIES 0