CMDB Data Manager Retirement definition and Retirement policies

[anthonyokoth]

I would like to set up retirement for CIs that have not been discovered for at least 3 months using the CMDB Data Manager. When i attempt to create a Retirement definition, it is not allowing me to use the the filter

Filters = Operational status = Operational AND Discovery source = SG-SCCM AND Most recent discovery < javascript&colon;gs.monthsAgo(3)

Here is the screenshot:

Is this how it is supposed to work? If so, then how are we otherwise supposed to define retirement criteria for our CIs?

Also, the Retirement policy also contains a data filter. What is the use for this if we are already filtering in the Retirement definition? Can someone explain to me how the retirement definition and retirement policy work with each other?

[anthonyokoth · Accepted solution]

I figured it out and it is embarrassingly straight forward:

A Retirement Definition is literally just that, a definition of which state your retired CI is in. For example, for me, a CI is retired if the Operational State = Retired. For others, it could be if End of Life has reached, or Install State = Retired etc. This is why the condition filters in the Retirement Definition only accepts simple conditions e.g. "Operational State IS Retired".

In the Retirement Policy, you use the Data Filter to create conditions that filter for records which the policy will act on. The policy ignores all the records that fit the filter in your Retirement Policy (Enforced Conditions).