Why is the "Group Seperate CI's::undefined" relationship is displayed in Depedency view Map opened from CMDB Alert Grouping.SummaryWhen we click on the "Open Dependency View map for CMDB alert" link from the Group Alert, the system shows us the association between the grouped CI's. When opening one such map, we see below relationship type: In the above screenshot we can 2 types of relationships: Members::Members ofGroup Separate CI's::undefined Here, the first relationship is a relationship between 2 nodes that can be seen at the CI level and the specific relationship type can be seen in the Relationship Types table as well, however, we could not find any reference for the second relationship type. Below Logic is used to display the second relationship type while displaying the CI Grouping: Use Case 1: Relationship Deletion Post Grouping: When 2 alerts are grouped using a valid CMDB relationship and when we click Open Dependency View map for CMDB alert link, the map displays the correct relationship. if due to some reason the relationship between these CI's gets deleted post alert grouping then the Map shows relationship type as "Group Separate CI's::undefined".Use Case 2: When 2 CI's that are part of the group and are 2-3 hops away from each other then this type of relationship is seen. In the above use case, the CI 2[PSGN178] is having a Level 2 relationship with "CI XYZ" and the same "CI XYZ" is having an L1 relationship with CI 3 [PNGO352] thus the relationship between CI 2 and CI 3 is not direct and is displayed using "Group Separate CI's::undefined". This behavior is controlled using the "sa_analytics.agg.query_cmdb_graph_walk_nodes" property. So the result seen in the screenshot is not a bug and is expected behavior.