All about Dependent CIs managementIssue This is KB is to answer following queries around Dependent CIs management; Why 'Dependent CIs management' is needed?How to enable 'Dependent CIs management'?Resolution 1) Why 'Dependent CIs management' is needed? When the CI that a dependent CI depends on is deleted, the dependent CI becomes orphan with no further use. To maintain the integrity and health of the CMDB, the system applies cascade-cleanup processes to dependent CIs that are affected by a life cycle update. Examples of dependent CIs needing cascade-cleanup: Tomcat application (T1) runs on a Linux Server (L1) and contains a WAR file (W1). When L1 is deleted, T1 and W1 become orphan dependent CIs.Network Adapters become orphan dependent CIs when the hardware itself is deleted.A Linux Server has retired and is set with end of life, the assumption is that if the server is no longer operational then applications which depend on it shouldn't be operational either. 2) How 'Dependent CIs management' is enabled? Setup environment for CMDB Data Managerhttps://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/configuration-management/concept/cmdb-data-management.htmlEnable system property 'cmdb.dependent.ci.cascade.op.enabled' 3) Once 'Dependent CIs management' is enabled, DependentCIProcessor flow runs below three operations. Cascade-retire dependent CIsCascade-archive of dependent CIsCascade-delete of dependent CIs As part of above three operations, depended CI's which are orphan are added to 'cmdb_dependent_ci_ledger' table. These records are nothing but such orphan depended CI's which are ready for actual delete, archive, or retire operation which can be later taken care by 'Cascade-cleanup' using either 'CMDB Data Manager' or 'Cleanup Orphan CIs' scheduled job which runs only one time.Refer below doc to learn more about these three operations;https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/configuration-management/concept/manage-dependent-ci.htmlBelow scheduled Job 'CMDB DependentCI Policy Processor' takes care of 'DependentCIProcessor' flow and performs above three operationshttps://instancen_name.service-now.com/sysauto_script.do?sys_id=7dbe9af077c630108043270bba1061cc&sysparm_record_target=sysauto&sysparm_record_row=1&sysparm_record_rows=1&sysparm_record_list=nameCONTAINScmdb+depe%5EORDERBYname In Tokyo or earlier release, below is the condition for this job(gs.getProperty('cmdb.dependent.ci.cascade.op.enabled', 'true') === 'true' && GlidePluginManager.isActive('com.snc.cmdb.csdm.activation'));Since Utah it changed to;(gs.getProperty('cmdb.dependent.ci.cascade.op.enabled', 'true') === 'true');Reason for this is, to use CMDB Data Manager, you no longer have to activate the CSDM Activation plugin (com.snc.cmdb.csdm.activation) or to map and migrate legacy life-cycle values into the CSDM standard values. For details about the CMDB Data Manager requirements, see CMDB Data Manager document.https://docs.servicenow.com/bundle/utah-release-notes/page/release-notes/now-platform-capabilities/cmdb-rn.html 3) You should use of CMDB Data Manager to apply cascade-cleanup operations on cmdb_dependent_ci_ledger More detail given in below document:https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/configuration-management/concept/manage-dependent-ci.html#d182917e296 4) Cascade-cleanup existing orphan dependent CIs When enabling the dependent CIs management feature, the cascade-cleanup operations apply only from when the feature is enabled. However, it might be necessary to apply a similar cascade-cleanup operation to orphan dependent CIs that already existed in the CMDB before the feature was enabled. Activate the Cleanup Orphan CIs scheduled job to perform a one-time cascade-cleanup of orphan dependent CIs across the CMDB.More detail given in below document:https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/configuration-management/concept/manage-dependent-ci.html#d182917e332Job for one time cleanup 'Cleanup Orphan CIs'https://instance_name.service-now.com/nav_to.do?uri=sysauto_script.do?sys_id=1fbfd45a73d1011026f6aa114df6a797