|
|
|
A Change Order contains change specifications that define the specific CI changes that are requested for a CI. CACF uses these change specifications when the Change Order enters a verification state to validate and confirm that the actual changes to the CI completed correctly. Create change specifications from a Change Order, CI, or the Configuration Control, Change Specifications node the CA CMDB section of the Administration tab.
The change specification contains the following main sections:
Specifies the Change Order that requests the change.
Contains the name of the CI that you want to update.
You can leave the CI Name field blank to imply that the change specification applies to all CIs defined for the Change Order. Use this option when all the CIs for a Change Order use the same managed attribute and planned value. The change specification applies to all CIs that are attached to the Change Order when the change order status moves to a managed change state with change verification active, referred to as expansion.
Specifies the name of the managed attribute that you want to update.
Selecting Any Managed Attribute indicates that any managed attribute can change during the verification of the Change Order. Because you can update multiple attributes in this case, you cannot specify the planned value.
Indicates the expected value of the attribute after executing the change. After the Change Order moves into a verification state, and the CI updates through the web interface, GRLoader, or Web Services, CACF compares the planned value with the inbound data to determine a match.
Special characters can be embedded in the planned value when the exact value is not known.
Specifies the status of the change specification, such as Verification Pending.
If you do not know the planned value in advance, but the value may change, you can set the status of the change specification to Use Discovered Value. This behavior requires discovery to update the CI before CACF considers the change specification as validated. You require this behavior for numeric fields and SRELs where an asterisk cannot be accepted as a planned value.
To help you with setting the planned value, the Discovered Attribute History tab lists all values that were recently discovered by an MDR, and whether were actually authorized, or loaded into the CMDB. This tab displays the format, case sensitivity, and other information about values so that you can determine an appropriate planned value pattern.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |