Managing Configuration Items › Configuration Audit and Control Facility (CACF) › CACF Administration and Policy Definition › How Configuration Audit and Control Facility Works › Multiple Policies

Multiple Policies

As you introduce more verification policies into your environment and more attributes are managed, organizing the policies becomes increasingly complex as more overlap exists between policies. For example, you have one policy for Server CIs and another policy for CIs in NY. You must consider the appropriate policy for Server CIs in NY. Use the policy sequence number to force one policy to take precedence when multiple policies potentially could take control over a single attribute. As you manage more attributes, the possibility that more policies manage a single transaction can increase.

Consider the following information when you have multiple active policies for a single transaction:

• If any selected policy requests writing data to the TWA, data also writes to the TWA.
• If any selected policy requests to cancel the transaction, CACF cancels the entire transaction.

  Important! Facilities that use the createAsset web service (including GRLoader and CMDBf) break the transaction into three separate transactions, two inserts, and an update. Updates to ca_owned_resource may be allowed, while updates to the CI extension table are canceled. Updates to CI family-specific attributes in the extension table may not be detected as inserts, but rather as updates.