topology rendering differences between Dependency View and Service Mapping for tag based service map

[Sharad Srivast1]

Hello ServiceNow Community, 

I am implementing a tag-based Service Mapping use case and need guidance regarding topology rendering differences between Dependency View and Service Mapping. 

Configuration: 

Business Application: PRINT BIL 
Class: cmdb_ci_business_app 

Tag-Based Application Service: print bil prd::prd 
Class: cmdb_ci_service_by_tags 

Relationship: Depends on::Used by 
Connection strength: Always 
Relationship stored in: cmdb_rel_ci 

The tag-based service is populated successfully and displays VMware Virtual Machine and Windows Server CIs. 

Observed behavior: 

1. Dependency View shows the complete hierarchy from PRINT BIL to print bil prd::prd and the populated infrastructure CIs. 
   2. Service Mapping displays print bil prd::prd and its infrastructure topology. 
   3. The expected upstream Business Application or intermediate service layer is not rendered consistently in the Service Mapping topology, even though the relationship exists and is visible in Dependency View. 

Validation completed: 

- Confirmed both CI records and classes. 
- Confirmed the cmdb_rel_ci relationship. 
- Confirmed relationship direction and type. 
- Confirmed the Tag-Based Application Service is populated. 
- Confirmed the full path is visible in Dependency View. 
- Confirmed the infrastructure is visible in Service Mapping. 

Questions: 

1. Is this expected rendering behavior for Service Mapping when the relationship is between cmdb_ci_business_app and cmdb_ci_service_by_tags? 
   2. Which CI classes and relationship types are supported for upstream rendering in the Service Mapping topology? 
   3. Is there an out-of-box configuration, traversal rule, map property, or supported relationship model required to display the complete hierarchy? 
   4. If an intermediate Service Instance/Application Service is required, what is the supported CSDM relationship pattern? 
   5. Are there known defects or release-specific limitations for this scenario? 

Any official documentation, known error reference, or supported configuration guidance would be appreciated. 

Thanks

Sharad