How can an CMDB Health Orphan Rule be used when the CI is part of a Dynamic Group?

[Bob Mullineaux]

We generally use an CMDB Health Orphan Rule which determines if a CI has a missing relationship to a Service (Application or Technical).   It works as expected and flagged in CMDB Correctness when there is not a relationship in cmdb_rel_ci between the CI and any Service, but we have recently configured Dynamic CI Groups to align CIs to Services and thus no explicit relationships created in cmdb_rel_ci...rather the CI to Service relations are stored in svc_ci_assoc, thus the CIs that are part of the Dynamic Group are still being flagged as Orphaned even though they do have a Service Relationship.

Does anyone know of a way to develop an Orphan rule around svc_ci_assoc?  

I was thinking of scripting something to automatically create entries in cmdb_rel_ci based upon the entries in the svc_ci_assoc table, but it sort of defeats the purpose of having a Dynamic Group.  

[CMDB Whisperer]

Good luck with the feature request.  I would agree with you that the orphan rule is a blunt tool that has several gaps.  I wouldn't recommend holding my breath on the outcome of the HI ticket or the feature request.  This is how it has worked for many releases, and the solution I have described is one that was, in the past, demonstrated in a ServiceNow blog.  Your question was: Does anyone know of a way to develop an Orphan rule around svc_ci_assoc?  My response provided you the best/only way to develop an Orphan rule around svc_ci_assoc given the platform as it stands today.  While I agree there could be enhancements made to the platform, that is not the question that was posed in your post.  If my solution was helpful in answering the question that was posted, please mark it as correct/helpful.

[Barry Kant]

Hi Bob, 
as alternative you might use the Instance Scan capability. 
In this capability you can define your own checks which run by schedule. Meaning you can check eg on the svc_ci_assoc table as well for these validations. As an outcome you can create a corrective task for eg a record owner, or use the outcome to make a report. 

Instance Scan is not intended for data quality checks, but the flexibility of adding checks makes it usable for these validations as well.

BR,

Barry