---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Define a not-allowed CI action

# Define a not-allowed CI action {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Define a restriction for CI Lifecycle Management in which a specified action is not
allowed for a CI that is in a specified operational state.

## Vorbereitungen

Role required: none

## Warum und wann dieser Vorgang ausgeführt wird

By default, there are no restrictions in the CMDB CI Lifecycle Management on applying
CI actions. You can restrict this behavior by not allowing a specified action to be
applied to a CI when it is in a specified operational state. For example, you can
define a restriction in which the provisioning action cannot be applied to a Linux
Server that is in a non-operational state.

## Prozedur

1. Navigate to AllConfigurationCI Lifecycle ManagementNot Allowed CI Actions.
2. Click New on the Not Allowed CI Actions page, and fill out the form.  
   {#non-allowed-cmdb-ci-action__table_x1h_zgj_kw__entry__2}

   | Field | Description |
   |-|-|
   | Not Allowed Action | The action that is being restricted. |
   | CI Type | The CI type for which the restriction applies to. To apply a rule to all CIs, select Configuration Item. |
   | Operational State | The operational state that the CI must be at in order to apply the restriction. |
   [ ]

   {#non-allowed-cmdb-ci-action__table_x1h_zgj_kw}
3. Click Submit.

## Ergebnisse

If an API attempts to apply the specified action to the specified CIs, while it is in the specified operational state, the operation fails and an error is logged.