Hierarchy Management Facet Settings

You can use the UI Modeler application to set preferences for the Hierarchy Management facet.

Switching between Classic and New Modes

You can view the Hierarchy Management facet either in Classic or New mode. To switch between these modes, you can use the UI Modeler application of Console. The following image shows the option to enable the Classic mode:

Note: Reltio plans to deprecate the older version (Classic mode) of Hierarchy facet. For more information, see the Deprecation Notices. When the older version is deprecated, the option to switch between the modes will be removed.

Sort Options for the Hierarchy View

In the New mode of the Hierarchy Management facet, you can select the Sort Order and Sort By preferences. You can sort the hierarchical data by Relationship type label or Entity label.

Displaying Secondary Labels

In the New mode of the Hierarchy Management facet, you can display the secondary labels for the entities. Click the Display secondary label option to view the secondary labels in your facet.

Note: Hub remembers your preference for this setting and on your next log in, the secondary labels are displayed in the Hierarchy Management facet based on your last settings.

Classic View of the Hierarchy Management facet

You can add the Hierarchy Management facet to the Profile. It can show the roots of the current node as a hierarchical tree.

Using a tree view, it can display multiple roots on the current node and self-referencing roots. It also can show only the parents (not including the peers) of the selected entity. The following cases are depicted:

  • Multiple Roots - Some entities may come from more than one parent category that has no association with one other.
  • Only Display Parents - In complicated hierarchies, some records have many uncles and cousins that confuse the issue. This option removes that information from the graph.
  • Root Displayed in Self Referencing - When a root is self referencing, the root needs to be displayed.

If a node has a plus sign to the left of its name, you can expand the node by clicking. Note that the node "RP-32722" is expanded in the screen shot below.

Alternatively, click the hierarchy icon in the header to expand the node.

Hierarchy Reverse Traversal

While working with hierarchies, sometimes the start and end objects defined in a standard data model need to be visualized in the reversed direction. Consider a scenario where the UI Profile screen contains a Hierarchy facet which shows the hierarchy of departments and hospitals across all patient product platforms such as MDM and CRM. Standard data model has a start object as a Department (child) and an end object as the Hospital (parent). But the department to hospital hierarchy requires data in the reverse order.

Altering the data model can have a major impact on several systems. In such a scenario, you may need the flexibility to store relationships in a standard format but access hierarchies (through UI and API) in a manner that’s most relevant to the end user.

Starting from 2020.1, you can change the the start and end objects of graph traversal, to render hierarchy trees in reverse order. With this capability, without having to change the data model and ETL, you have the flexibility to render and request the hierarchies in any order.

To see the hierarchy tree in the reverse view, you can set the Reverse relations option ON in the Hierarchy Tree properties in UI Modeler.

You can also view the graphs based on normal order (Start object, end object) of relation or reversed order of relation (end object, start object) by using the new optional parameter "reverseRelations" in the GET {TenantURL}/{entity object uri}/_tree API.

Example of a hierarchy tree with its reversed tree view in the Classic view

In the image shown above, the first facet Legal Entities Hierarchy shows the hierarchy flow from HCOTest2 (parent) to test212121 (child). The second facet Legal Entities Hierarchy Reverse shows the reverse of the hierarchy shown in the first section. Here, the test212121 (child) has become the root node and the former parent node HCOTest2 has become the child. Interestingly, the last section Parent Hierarchy shows hierarchial pairs for multi-root/multi-parent which wasn't directly visible in the first facet.