Dependent Ci management is not working

[Deepak61]

I'm having trouble understanding and getting to make the Dependency CI management work. I've enabled the property  "cmdb.dependent.ci.cascade.op.enabled" mentioned in the documentation https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-manag...
and also I have enabled the  life-cycle rules . Still, whenever I retire a Linux CI using the cmdb data manager policy to retire.  it is hosting a apache web server, but the web server is not getting retired, nor can I see the web server in the ledger cmdb_dependent_ci_ledger as mentioned in the documentation.
I have also ran the following scheduled jobs after retiring the Linux.

1. CMDB DependentCI Policy Processor
2. CMDB Cascade Retire Dependent CIs

There still no records in the cmdb_dependent_ci_ledger table even after the linux server is retired. 
Can someone help me with this? 

[Kieran Anson]

I think the discrepancy in your understanding is that by having a relationship does not mean a 'dependency'. Dependencies are defined at the class level using the metadata editor. SN will use this data to them determine if a CI is dependent on another (e.g a server is hosted in a rack) whether to retire the server CI if the rack is retired (because one can't exist without the other).

Product Documentation | ServiceNow

[spollock]

Deepak61 Were you able to get this to work ?

We are having a similar issue,  we retire the CI, run CMDB Cascade Retire Dependent CIs which puts the dependent CI's in the cmdb_dependent_ci_ledger table and creates a data manager task for approval.  We approve that task and run CMDB DependentCI Policy Processor which removes them from the cmdb_dependent_ci_ledger table but does not retire them.

[Deepak61]

No, @spollock . In my case, the dependent CIs are not even showing up in the cmdb_dependent_ci_ledger table. For the time being, I have set this issue aside and will revisit it later. I'm unsure about the approach of creating class-level dependencies using the metadata editor and not clear of how to set it up.

As an alternative, I am planning to add a Business Rule (BR) on the hardware table. This rule will, upon retirement of a CI, query the cmdb_rel_ci table to find the dependent applications and set their status to "retired." I know this isn't the best solution; ideally, I would like to resolve this using the OOB CMDB Data Manager. This would not only address the issue of retirement but also help us set up archiving in the future.

However, using a BR is my last resort.

@spollock , are you able to get all the dependent CIs in the cmdb_dependent_ci_ledger table? If so, could you please explain how you achieved it?

[Eric148]

Hello - did you ever resolve this?  I am having the same results as you.

[bkprasanna]

Hi Eric,

I have posted the solution . please let me know if any specific question.. also please refer the below link

Solved: Dependent CI retirement with CMDB Data Manager - ServiceNow Community