Dependent CI retirement with CMDB Data Manager

Amar_Be
Kilo Sage

Hi,

 

In the page related to Dependents CI management ( https://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/product/configuration-manageme...) ,  It is said that dependent CI to retire are added to the table cmdb_dependent_ci_ledger and "Those CIs are set as being ready to retire using the CMDB Data Manager upon approval."

 

But I can't find any documentation on how those CI are retired by the CMDB Data Manager. It is not possible to create a Retirement rule on that ledger table.

Does anyone have succesfully used this feature?

 

1 ACCEPTED SOLUTION

I got the point, in fact the policies are created but not directly visible in the list of policies as it is filtered :

Amar_Be_0-1711639534664.png

 

Once the filter removed, they appear.

For info the Dependent CI retirement is managed by 2 jobs :

- CMDB Cascade Retire Dependent CIs  (which fill in the ledger) 

- CMDB Data Manager Retire Policy Processor  (which process the ledger)

View solution in original post

16 REPLIES 16

bkprasanna
Tera Expert

I have the same issue.. When a CI "State" is set to retired as per the policy a task is generated and upon approval the "LIfe cycle stage" and "Life cycle stage cycle" will get updated to Retired and End of life respectively but the dependent related CIs "State/ Lifecycle stage/ Life Cycle stage cycle" will not be changed to "Retired/End of life"

 

I can see the related records in ledger table with the "state" as Ready and "Action" as Retire (to be retire) .but there is no process document which tells how to retire dependent CI status.

bkprasanna
Tera Expert

I have found the solution  ( No documentation from Servicenow)

 

Step 1: Follow all the steps provided for CI dependent management ( refer servicenow docs)

Step 2: Execute the scheduled job : CMDB Cascade Retire Dependent CIs]

 

You can see a task will be generated for "Retire or Archive or Delete" based on your previous policy

 

Step3 : Complete the generated task

 

Ref Screenshot :

bkprasanna_0-1720016074028.png

 

 

Good that you found the solution.

The important point to not forget  is that the hole process is asynchronous as based on scheduled jobs.

Thanks Amar_Be

Yes Its kind of Asynchronous as it is  based on the scheduled jobs.

Hi  @bkprasanna : Can you please provide detailed steps , how did you achieve this?

Because I am getting to see only one CI which is listed in CMDB CI end of life ledger table. And the same listed in cmdb data management task and how can we utilize this out of box policy how to activate this. Please help