Managing Configuration Items › Configuration Audit and Control Facility (CACF) › CACF Administration and Policy Definition › How Configuration Audit and Control Facility Works › Verification Policy Filter Syntax

Verification Policy Filter Syntax

To help with establishing generic policies, the Change Order Alignment, Transaction Filter, and CI Filter accept an asterisk as a final pattern character as a wildcard. Use an exclamation point at the beginning of these filters to indicate negation.

Important! Policy pattern rules differ from change specification planned value rules. For policy filters, you cannot use embedded asterisks (*) or the greater than (>) and less than (<) special characters.

Policy filters are case-sensitive for verification policy selection patterns, such as CI Name or CI Class, even if you define those attributes as case insensitive.

Note: A blank "" (no value specified in the field) policy filter matches only the blank value, but a policy filter that uses an asterisk matches all values.

Consider the following information with the following example verification policies:

• Policy1 selects CIs name(prod*) attribute(IP Address) where a matching change specification exists.
• Policy2 selects CIs name(prod*) attribute(IP Address) where there is a rogue update.
• Policy3 selects CIs name(test*) attribute(Memory Installed) from mdr(Cohesion).
• Policy4 selects CIs name(“”) attribute(Memory Installed).

The following list describes the possible outcomes of these policies:

• When an update to CI(test2) attribute(Memory Installed) occurs, Policy3 manages the update. CACF ignores Policy1 and Policy2.
• When an update to CI(prod3) attribute(Memory Installed) occurs, and a matching change specification exists, Policy1 manages the update.
• When an update to CI(development4) attribute(IP Address) occurs, CACF updates the CI with the new ip address because no matching policy exists.
• When an update to CI(prod1) attribute(Disk Capacity) occurs, no policies for attribute(Disk Capacity) exist, and CACF updates the CI with the new value. In this example, CACF does not manage the Disk Capacity attribute.
• Policy4 only matches CIs with blank names. Because blank CI names are invalid, the change never executes.