---
sourceDocument: Xanadu ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/servicenow-platform

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Define a non-allowed operational transition

# Define a non-allowed operational transition {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Define a restriction for CI Lifecycle Management in which a specified CI cannot
transition from one operational state to another.

## Before you begin

Role required: none

## About this task

By default, CI Lifecycle Management has no restrictions for transitioning CIs from
one operational state to another. You can restrict this behavior by defining
transitions that are not allowed for a specified CI. For example, you can define a
restriction on transitioning a Linux server from non-operational state to repair in
progress state.

## Procedure

1. Navigate to AllConfigurationCI Lifecycle ManagementNot Allowed Operational Transitions.
2. On the Not Allowed Operational Transitions page, click New and fill out the form.  
   {#not-allowed-oprtionl-trnston__table_pbm_w3j_kw__entry__2}

   | Field | Description |
   |-|-|
   | CI Type | The CI type for which the restriction applies. |
   | Not Allowed Transition | The CI state into which transitioning is restricted. |
   | Operational State | The operational state that the CI must be in for the restriction to apply. |
   [ ]

   {#not-allowed-oprtionl-trnston__table_pbm_w3j_kw}

## Result

If an API attempts to transition a CI that is in the specified operational state to a state that is not allowed, the operation fails and an error is logged.

*[\>]: and then