CMDB Data Manager and Delete Policy on referenced CI

[Jacques Clement]

Hi,

Based on some research I made on the CMDB Data Manager, it looks like the Delete policy only deletes CI that are not referenced by tasks and possibly other tables. From what I can see, only "independent" CIs will be removed.

I suppose the intent is to protect referential integrity, but can someone confirm this functions as designed, In that case I find it confusing that the policy preview does show CIs that ultimately will not be removed.

Am I missing something?

Thanks.

[Suggy]

@Jacques Clement Do you have any update on this? I have same question.

[Jacques Clement]

Hi @Suggy unfortunately no. It still puzzles me to be honest.

[Daniel Peel · Accepted solution]

The policy is showing the CIs that match whatever filters you've created for the policy.  You'll need to review the actions the flow will take to see if the CI will be deleted.  Think of that policy impact like this: IF everything is in order then these CIs will be impacted by the policy.  Once it runs things in your environment may have changed and not every CI listed will in fact be impacted. 

Looking at the subflow Delete Configuration Items, we see an action called Delete CIs for Task... looking at that Action we find reference to the SI CMDBDataManagerHelper and it's method getFilteredCIs which does in fact remove CIs from those that are in the tables listed.

So yes, if that CI is used on one of the ITSM main tables, incident, problem, change, as configured OOB... the CI will not be removed.