CMDB Data Manager provides policy-driven lifecycle governance for configuration items. The organization should configure Life Cycle Stage automation in Data Manager so that a qualifying lifecycle change on a parent CI is propagated consistently to the relevant child CIs.
This approach creates a controlled and auditable lifecycle process. It avoids relying on custom scripts or disconnected import logic and ensures that lifecycle transitions are applied according to defined conditions and CI relationships.
A Transform Map is intended to transform and import source data. It is not the appropriate mechanism for continuously cascading lifecycle changes between related CIs. Creating a new CI class would also be incorrect because lifecycle management is a behaviour applied to existing CI classes rather than a separate CI type.
CMDB Data Manager is specifically designed to automate CI lifecycle activities such as retirement, archival, deletion, certification, and attestation. Therefore, Data Manager lifecycle automation is the governed solution.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit