CMDB Dependent CI Deletion notification for a CI that does not appear to be orphaned

Karen16
Giga Guru

‎10-25-2023 08:41 AM

Hi,

We upgraded to Utah and a CMDBTask was created for the Dependent CI Deletion Policy.  I've reviewed the CI that is listed in the task and it does not appear to be orphaned.  It has many dependencies.  How can I determine why this particular CI was tagged in this task and whether we should act on this task. 

Thanks,

Karen

0 Helpfuls
  • 1,568 Views
1 REPLY 1

Churchie73
Tera Contributor

‎01-11-2024 09:00 AM

Hi @Karen16 

This tasks showed up for me in some instances recently and I had to review the CMDB Data Manager Dependent CI management documentation. You can find it for Vancouver here. 
From the documentation, it does mention the following:

Enable management of dependent CIs

To enable management of dependent CIs:
 
Configure your environment for CMDB Data Manager. For details about how to configure the environment for CMDB Data Manager and the CMDB Data Manager own prerequisites, see CMDB Data Manager.
Ensure that the cmdb.dependent.ci.cascade.op.enabled system property is set to true (default). This property doesn't exist in the base system and to view or modify the property value, you must first add it to the System Properties [sys_properties] table.

In my case, I've been disabling the needs review flag so they take care of themselves. You can decide if that's a route you want to go.

Please mark this correct if this answers your question.

Best-

Darren

0 Helpfuls