Define a not-allowed CI action

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • 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.

    Before you begin

    Role required: none

    About this task

    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.

    Procedure

    1. Navigate to All > Configuration > CI Lifecycle Management > Not Allowed CI Actions.
    2. Click New on the Not Allowed CI Actions page, and fill out the form.
      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.
    3. Click Submit.

    Result

    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.