CI Automation Rules

Configuration item automation rules codify CMDB hygiene: default field values on creation, status transitions, and team-assignment logic that would otherwise be manual. In the workspace, this is the CI Rules tab.

How a rule works

A rule watches for a condition on a configuration item and takes an action when it is met. Common starting rules:

• Set a default value on a field when a configuration item is created.
• Transition status when a signal changes, for example flagging a configuration item whose discovery check-in has gone stale.
• Assign a support team based on the configuration item's attributes.

Each rule has an Enabled or Disabled toggle, and you create rules with the + button on the tab.

Getting started

Start with one or two rules, watch the Reports tab for their effect, then expand. Where you need a field to be required by status rather than defaulted, use a UI extension instead of an automation rule.

How this differs from reconciliation rules

The two rule types operate at different points and are easy to confuse:

• CI automation rules act on configuration items that are already in the CMDB.
• Reconciliation rules act on incoming data before it lands, deciding how a record from a source is matched and whether it resolves automatically. See Reconciliation Rules.

If your goal is to control how a discovery or integration source creates and updates configuration items, that is reconciliation, not CI automation rules.