Unified Map provides inconsistent behavior for Application services if service mapping returns empty set - Known Error

Unified Map provides inconsistent behavior for Application services if service mapping returns empty set Description Unified Map provides inconsistent behavior for Application services when Service Mapping plugin is not installed/active for downstream CIs.

If the application service is the home node, the map does not show any downstream relationships. However, if the home node is a parent, then the downstream relationships are shown.

Steps to Reproduce

Identify an application service with downstream relationships and at least one upstream relationship in available OOB data or create as needed Without service mapping installed: View the application service in unified map as home node Note there are 0 downstream relationships present Now open the app service's parent in unified map and make sure depth is set to at least 2 hops Observe that the relationships downstream of the app service are shown

If customers don't have service mapping installed/active, the dependency on service mapping data for downstream only when app service is the home node causes inconsistent display and can imply the relationships are missing.

If customers do have service mapping installed, service mapping needs to populate the data, in order for downstream CIs to appear.

If service mapping is correctly mapping CIs to the parent service and it is still not showing up in the unified map, check the lifecycle status values of the SM-mapped CIs to the lifecycle inclusion filter applied on sn_cmdb_ws_operational_lifecycle_for_unified_map - make sure they match. Otherwise such CIs will get filtered from unified map.

Workaround No workaround available at this time.