CMDB Data Manager Policy

VShine
Mega Guru

Hello Experts,

I am seeking advise on CMDB Data Manager functionality in Washington DC release.

We are using CMDB Data Manager policy to retire Stale/ orphan CIs in our CMDB. We have defined policy and its retiring CI as expected. Issue is, we are not able to tie back the retired Ci to the CMDBTask. We like to have reporting capability which task is retiring what for future audit purpose. Would love to know how other people/organization are using CMDB data manager.

 

As once approved, the data manager task is closed & then related list doesn't have any information about which CIs. 

Please advise.

6 REPLIES 6

The comments should be added prior to the retire, can you review the order?

if my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.



Best regards

Surya Prakash Garg

Connect me on Linked In

https://www.linkedin.com/in/spgarg/

There are three jobs that Data manager uses to move the CI's through the process:

CMDB Data Manager Retire Policy Processor

  • The server appears in the table cmdb_ci_end_of_life_ledger

CMDB Cascade Retire Dependent Cis

  • The server CI gets removed from the cmdb_ci_end_of_life_ledger table and the dependent CI's appear on the cmdb_dependent_ci_ledger

CMDB DependentCI Policy Processor

  • All dependent CI's are removed from the cmdb_dependent_ci_ledger table

 

The table cmdb_ci_state_management_task_to_ci is not one of these and is referred to in a related list on the cmdb_data_management_task default form, but is configured to "omit if empty" which gives that it will not show if there are no matches.
The table cmdb_ci_state_management_task_to_ci is however empty in my customers instances which leads me to believe that this is either a bug or functionality yet to be implemented.
Irritating nonetheless..