So I am facing some weird behavior with creating CMDB Data Manager Policies. My understanding is that if I chose "Retire
as the policy type, the filters should automatically include basically the opposite of the retirement definition for CMDB records, in addition to whatever other filters I chose on the policy creation page. And that appears to be how it is working at least in our test instance of SNOW.
Retirement definition in Test:
And this is what the filters in the CMDB data manager policy creator look like when the definition is inactive, as expected it shows zero results:
This is the filters when the retirement definition is set to active, as expected I see basically every record in our CMDB that isn't "retired":
But in our prod instance I am seeing these filters regardless of whether the same retirement definition is set to inactive or active:
We using the old core UI data manager, not the new CMDB workspace one. Any ideas on where to start investigating? It's like there's some sort of default policy in our prod instance but none of the entries in the custom retirement definition table are set to active but the filter is still including that "Lifecycle status is not end of life" regardless.
