Inactive fields that are mandatory are still being marked as required by CMDB Health Dashboard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hi everyone,
Our instance has a custom field that was set to Mandatory = true, but has since been deprecated and have been deactivated. We noticed that in the CMDB Health Dashboard, it's still marking that field as required.
Is this a bug? or does the Health Scans for mandatory/required fields still check for inactive fields? Anyone else experiencing this behavior?
- Labels:
-
Data Health Tools
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
15m ago
Hi @JohnChristi,
This is expected behaviour, not a bug in the scan itself. The CMDB Health Dashboard does not decide 'required' purely from the live form at run time:
1. Completeness / Required is driven by the required-fields configuration held for the CI class (CI Class Manager > open the class > Health > Completeness > Required fields), and by the dictionary entry still having Mandatory = true. Setting the dictionary entry Active = false deprecates the field, but it does not clear Mandatory, and it does not remove the field from the class health configuration, so the health audit still tests CIs for a value in it.
2. To retire it properly, in this order:
a. Open the dictionary entry for the field and set Mandatory = false first, then set Active = false. Check for the same field on child classes / inherited entries and for any Data Policy that still makes it mandatory.
b. In CI Class Manager, open the affected class(es), go to the health / Completeness configuration and remove the field from the Required fields list, then Save.
c. Re-run the health processing instead of waiting for the next scheduled run - run the CMDB Health Dashboard scheduled jobs (the Generate Scores / completeness jobs for that dashboard) so old results are recalculated. Existing failures already stored as health results will not disappear until that recalculation runs.
3. Verify on one CI of that class: after the rescore, the field should no longer appear in the Required / Completeness failures on the CMDB Health Dashboard, while genuinely mandatory fields still do.
If it still appears after steps a-c and a rescore, check that no other class in the hierarchy still lists it as required - a parent-class entry will continue to flag child-class CIs.
Hope this helps.
