CMDB Data Manager Advanced Policy Rules / Conditions

[PG2]

When creating a data manager policy we can select CI attributes to build a condition that identifies CIs in scope for auto retirement. However, is there a way to build a policy using more complex conditions?

For example, lets say we want to identify a server not discovered in the last X days, related to a VM in a 'terminated' state. Can we configure a policy to use the relationship? I understand that other functionality might be better suited to this (e.g. I can see there are OOTB business rules that cascade status from VM to server).

But this is just one example of an "advanced" condition.

[PG2]

For anyone else's reference. The OOTB dependent CI retire policy may help address some of the complex requirements. 

There is also the ability to attach custom sub flows to your retire policies to include more advanced logic before auto-retiring a CI. Just tread carefully considering the CIs associated with the data management tasks may not be retired if they are skipped by any customised logic.

[Amar_Be]

Hi,

Could you tell me where I can find this OOTB dependent CI retire policy ?

I'm on Washington and Vancouver and can't find it.

Thank

[bryanabhay]

Hi Amer, 

While you add filter on Retire policy you may be selecting Class is condition where as select Class - is a

which will consider Child Classes as well. ( as per ServiceNow ) 

Thanks

[Brian Bouchard]

Realize this question about the OOTB dependent CI retirement policy is old, but for anyone that may be looking for this still, you can go into CMDB Data Manager and click on "View Policies" to see all the non "On Demand" policies.  In the filter on the existing page, if you remove the "On Demand = False" section of the filter, you can see the default policies "Dependent CI - Retire", "Dependent CI Archival", "Dependent CI Deletion"