Managing Configuration Items › Configuration Audit and Control Facility (CACF) › CACF Administration and Policy Definition › How Configuration Audit and Control Facility Works › Change Order Alignment

Change Order Alignment

Policies filter on how closely a CI attribute update matches a change specification. After a CI update, CACF searches for a change specification that matches both the CI and the attribute name. This search can verify the change specification. This Change Order Alignment can occur as follows:

• Change specifications exist for this attribute and CI.
• Change Orders exist for this CI, and those Change Orders do not contain change specifications.
• A rogue insert transaction occurs which indicates and new CI. A Change Order does not exist with this CI attached to it.
• A rogue update transaction occurs which indicates an existing CI. A Change Order does not exist with this CI attached to it.

Only Change Orders in a change state where change verification is active are considered when looking for a matching Change Order. Closed, unapproved, unscheduled, or otherwise nonexecuted Change Orders are not considered when searching for a matching Change Order.

After CACF determines the Change Order alignment of a transaction, it performs a search for a corresponding policy. A policy can manage one or more Change Order alignment types:

Change Order with Specifications

Indicates that a Change Order with a change specification which specifies the updating CI and attribute name exists.

Change Orders Without Specifications

Indicates Change Orders that specify this updating CI, and those Change Orders do not have any change specifications.

Rogue Insert

Indicates an inserted CI, by definition, the CI does not have any matching Change Order in a verification state.

Important! Policies which prevent rogue inserts must specify a managed attribute of Name or All Managed Attributes, where Name specifies an active managed attribute).

CACF always allows rogue inserts and updates when a transaction only has unmanaged attributes.

Rogue Update

Indicates an updated CI that has no matching Change Orders in a verification state.

More information:

Example: Allow Change Orders Created Without Specifications

Prevent Rogue Changes to the Attribute