CMDB Data Manager Policy - Filter not showing records

gab7001
Tera Contributor

I am trying to implement a CMDB Data Manager Policy. Policy Type = Retire, Task Assignment Group = Support. For the Condition Filter I have Class is Computer. In my PDI I have 814 records for Class = Computer. I can see that when I filter directly in cmdb_ci table. However, in the Policy, the filter shows 0 records. I have tried different options, but not much I can change, the filter keeps showing 0 records. Why the filter doesn't show the same than when the filter is applied directly to the table?

1 ACCEPTED SOLUTION

rengala
Tera Contributor

Ok, for us it was a simple missing element.

We needed to go to cmdb_retirement_custom_definitions and set the active field for cmdb_ci to true. This fixed the retirement issue. From there, assuming you've set up your CSDM Life Cycle Mappings, you should be able to build policies for retirement, archival, and deletion.

View solution in original post

4 REPLIES 4

Shreya Jain2
Tera Contributor

I'm facing similar issue, did you find any solution for this?

 

Hi @Shreya Jain2 , no, not yet. Just reviewed and the same situation, no matter what condition I put on the filter. However for Attestation the filter works. But I can't understand why the other policy types don't allow the filter to work. Maybe for some  reason we cannot apply those policies to CIs? But that doesn't make sense. Hopefully somebody out there can explain.

Ryan122
Tera Expert

Haven't discovered a solution yet. We have the same issue, when we clicked on the show results link after running the filter we found the filter is looking for sys_class_name == empty before any of our queries run: 

RLQUERYcmdb_policy_ci_exclusion_list.ci,=0^policy_type=[sys_id]^ENDRLQUERY^sys_class_nameISEMPTY^sys_class_pathINSTANCEOFcmdb_ci

rengala
Tera Contributor

Ok, for us it was a simple missing element.

We needed to go to cmdb_retirement_custom_definitions and set the active field for cmdb_ci to true. This fixed the retirement issue. From there, assuming you've set up your CSDM Life Cycle Mappings, you should be able to build policies for retirement, archival, and deletion.