Change Specification Considerations

Consider the following information about change specifications:

The CI name can be left blank which implies the change specification applies to all CIs defined for the change order. This option is useful when all of the CIs for Change Order are using the same planned value. The change specification applies to all CIs that are attached to the Change Order when the managed change state moves to a state with change verification active.
You can create a Change Specification that requires manual verification. This action lets you verify managed attributes manually.
Change Specification planned values for Lookup field managed attributes must be unique.
For example, if you want to create a planned value for the Primary Contact (primary_contact), the contact specified in the planned value must be unique.
You set case sensitivity only for comparisons made for change specification managed attribute planned values using the Case Sensitive option in the managed attribute. Specifying case-sensitive managed attributes do not affect the policy selection patterns.
When the exact value is not known for the planned value, you can use wildcard (*), range (> or <) or negation (!) values.