Managing Configuration Items › Versioning › Sources of Versioning Data

Sources of Versioning Data

Versioning data generates whenever you create or modify an object by any component that supports the Audit Log facility. Snapshots generated from multiple sources are indistinguishable from one another. When the environment is properly configured, snapshots appear automatically whenever changes are made to CIs and their relationships.

All CA CMDB families are enabled for versioning. CIs in CA Service Desk base families must be converted to CA CMDB families to take advantage of versioning.

Versioning data includes the following sources:

• CA CMDB CI updates—Updates to common CI attributes and family-specific CI attributes by using the user interface.
• CA CMDB relationship updates—Updates to relationships on the Relationships tab and the CI Relationship List by using the Edit and Edit In List feature.
• GRLoader—CI insert and attribute updates, relationship updates, Standard CI assignments, and Milestones imported by using GRLoader. When updates from an MDR are sent using GRLoader, the MDR source is also recorded, enabling you to track attribute changes directly to their source.

  Note: For more information, see the Technical Reference Guide.

• CA SDM Change History—A snapshot is automatically created for all CIs associated with a change ticket. Up to four snapshots are taken when the CI is opened, closed, active or resolved.
• CA Asset Portfolio Management (CA APM) CI changes—Changes made by CA APM to CIs with logging enabled.
• Change Verification—Updates to change specifications, verification policies, managed change states, and managed attributes.

Note: CIs created in CA SDM or previous CA CMDB releases only contain modification changes. Initial attribute values such as name, family and class were not logged and do not appear in snapshots. In addition, Relationships created with CA Service Desk or previous versions of CA CMDB do not have audit history information.