What are the Advanced CMDB Data Manager Policy options?
I’m digging more into the archive, and destroy rules of the archival processes. That is until I found the CMDB Data Manager and their policies.
I’m not sure if this is possible, but is there a way to have the retirement or archival step only execute when the CI is not referenced by a number of other tables? Specifically tasks, and kb tables.
I’m going to link what I found so far but nothing quiet does it this way yet.;
CMDB Data Manager Advanced Policy Rules / Conditio… - ServiceNow Community talks about using the “Dependent CI - Retire” Policy to retire child records to a CI, which is not quiet what I need.
Over your storage limit? Archiving may not be you… - ServiceNow Community talks about the nuances about archiving and deleting and storage concerns
ServiceNow DEMO: CMDB Data Manager (youtube.com) shows how to use this thing in a Utah Instance which was very helpful.
I looked on nowlearning and everything i found was more about understanding the deduplication process cmdb data manager LXP Search - Now Learning (servicenow.com)
The official docs CMDB Data Manager (servicenow.com)
I can think of a few ways to handle this but this seems so close without having to customize things. A few options I can think of off the top of my head include, running some scheduled job/flow to set some value “Ready to retire” when the conditions are met then use the CMDB Data manager policies but, I’d love to hear if anyone has any other thoughts on this or if there’s another better way.
Thank you!
Community post https://www.servicenow.com/community/cmdb-forum/advanced-cmdb-data-manager-policy-options/m-p/2768444#M8215
