The Change Manager manages change specifications in your CACF environment. Change Analysts create Change Specifications when they create Change Orders. The Change Analyst defines the change in terms of the specific CI and CI attribute being changed.
The Change Specifications list shows all verified and outstanding change specification verifications in your environment. The ability to modify a change specification depends on the status of the Change Order. By default, you can only modify change specifications in Change Orders with the RFC status. After CACF verifies this change, it considers all subsequent changes as rogue inserts or updates
Important! If multiple discoveries occur during change specification verification, discovery data can invalidate a previously verified change. At the end of verification, the CI is in the state that all the change specifications desire. For example, a variance occurs for a CI with a change specification in the Verified state, but the status changes to Failed Verification.
A single CI can have many outstanding change specification verifications pending from many Change Orders. CACF evaluates each verification independently, and a single MDR update can update multiple pending change verifications.
Note: The Final field on the Change Specification List indicates whether a change has been completed. The Change Order is eligible for to move to the next default state when all change specifications are final and the Promote Change Order After Verification option is enabled for the managed change state.
The following fields require explanation:
Specifies the status of the change specification, such as Verification Pending.
Note: For more information about change specification statuses, see the Administration Guide.
Specifies the status of the Change Order.
Specifies the Incident that the verification policy creates optionally for an incorrectly implemented Change Order.
If the Configuration Administrator specified the policy option to create Incidents, the Incident documents the expected and discovered values. If all discoveries result in failed verifications, the Incident receives log comments indicating that the incident represents multiple failures.
Specifies the CI that you want to define the change specification.
Note: When you make several identical changes to a set of CIs, you can leave the CI Name field blank in the Change Specification. In this case, the Managed Attribute and Planned Value apply to all CIs attached to the Change Order. Change specifications for each CI are created when the Change Order moves to a status with Change Verification Active enabled for the managed change state.
Specifies the value of the attribute at the time a user created change specification.
The original value field shows the current attribute value for the CI when defining the change specification value for the first time.
Specifies the last value that was discovered for the attribute during the implementation and verification active process. This field updates each time CACF discovers a new value for the attribute.
Specifies the verification policy that was in effect during the last change verification for this change specification.
Shows the message associated with the last verification action such as the reason why a verification failed.
Link to the TWA record associated with this change specification and policy.
| Copyright © 2013 CA.
|
Tell Technical Publications how we can improve this information |