CMDB Dashboard Completeness

Brad Kallmeyer1 · ‎04-14-2017

Trying to understand how the "Completeness" works with the Dashboard. We have 5 fields that are mandatory on the base configuration table (cmdb). However some of our classes these fields are not a required item and have a dictionary override on them. When we run everything with the dashboard these items are showing up as missing mandatory fields.

Question is when the jobs run at what table level are they running against? Anyway to get these items to not show up as failures in Completeness, it appears the dictionary override isn't the answer.

VivekSattanatha · ‎04-18-2017

Hi Bradley,

Yes, you are right... Next-hop routing rule is one table which is extended is from CMDB base table only. When you give mandatory fields for CMDB base table it will inherit to all the tables extended from it. But you do not need to have Managed By, Owned By & Support Group fields has to be mandatory for the routing table.

If I have to select Managed By, Owned By & Support Group these fields as mandatory then I would select Hardware table.

Regards,

Vivek

Based on the impact hit like, helpful or correct

View solution in original post

VivekSattanatha · ‎06-16-2017

Hi Swapnil,

If you want to create Orphan rules for different classes do not create it in the base CMDB class. In CI Class Manager, create it like below for individual class.

Regards,

Vivek

Based on the impact hit like, helpful or correct