Dependent CI retirement with CMDB Data Manager

[Amar_Be]

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?

[Harsh Vardhan]

@Amar_Be  You have to build Policy type rule and define filter condition based on your requirement , also to perform action you can select ootb retire subflow on policy rule. 

I would recommend to check below YouTube session. It will help you. 

CMDB Data Manager feature Walkthrough 

Doc Link : Create a CMDB Data Manager policy 

Thanks,

Harsh

[Amar_Be]

Thanks for you answer Harsh.

But in the same page, it is said that the system will generate those policies. But I can't see them, it there something to do to trigger this generation?

"The system generates 'Dependent CI - Deletion', 'Dependent CI - Archive', and 'Dependent CI - Retire' Data Manager policies, for the set of CIs that are ready to be deleted, archived, or retired. "

[Harsh Vardhan]

@Amar_Be  I think you have to create policy manually . 

After you publish a policy:

• A daily scheduled job processes the published policy and policy tasks are assigned as set in the policy. If the policy is associated with a subflow, then policy tasks trigger the policy subflow. Policy execution issues are recorded in an error log with notifications sent to the CMDB Data Manager Administrator.

  If the policy is configured to require an approval for its tasks, then email notifications are sent to members of the assignment group in the Managed by Group attribute of the CI. If the policy is associated with a subflow, then a policy task triggers the policy subflow only after the task is approved.

• If the policy is associated with a subflow, then after a policy task is complete, the policy subflow closes the task. For an Attestation policy (which is not associated with a subflow), a user must process all CIs in the task and submit the task to close it.
• For Attestation policies, attestation tasks are assigned to users as specified, and those tasks appear in the CMDB Workspace when those users log in.
• For some policy types, such as Delete, the list of the target CIs is rolled up in a CSV file that is then attached to the task for tracking purposes.
• Stale tasks are set to Closed Cancelled by a daily scheduled job. A task becomes stale when it is still open and not approved after at least 90 days. The number of days after which a task is considered stale is determined by the cmdb.data.manager.stale.task.life.in.days system property.

Have you checked the YouTube session which i attached on my last response. that will help you a lot. 

Thanks,

Harsh

[Amar_Be · 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 :

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)