Hierarchy Maps provide a management consumable format to visualize data. Typical Hierarchy Maps are Org Charts, Capability Maps, Service Maps etc.
Designer provides a flexible way to create Hierarchy Maps visualizations on any table. This feature processes the underlying data in the following way:
- Shows parent/child relationships (hierarchical data) as nested containers by hiding the connections visually.
- Includes elements connected via downstream m2m relationships (CI relationships) within the container by hiding the connections visually.
- Shows elements connected via upstream m2m relationships (CI relationships) by keeping the connections visually.
- Keeps flexibility to change shape styling and positioning.
- Supports any other feature e.g. Indicators.
In order to create a hierarchy map follow these instructions:
A – Click the INSERT ribbon.
B – Click the ‘Hierarchy Map’ Icon.
C – Select the number of levels the capability map should include. Maximum 10 levels are supported.
Based on the level depth and number of relationships the creation of the Hierarchy Map can take up to multiple minutes. Use the ‘Include Tables’ and ‘Include Relationships’ options to minimize the query time.
D – Select the ‘Target Table’ which indicates the starting point and basis of the hierarchy map. E.g. if you want to create a map where applications are grouped by capability, select Business Capabilities here. The capabilities will be shown hierarichal. If a hierarchy (parent/child relationships) does not exists, elements will be shown as single containers including related items within the container.
E – The ‘Include Table’ option provides the ability to exclude all other tables except the selected ones.
In the example above Business Capabilities will be shown together with Business Applications and Strategies—all other tables will be ignored.
Use this option to filter the view for specific tables (will consider only relationships to the selected Include Tables).
Leave this option empty to include all tables (will consider all relationships to any table).
Select the same table type as the ‘Target Table’ to terminate the view with a single table. E.g. selecting Business Capabilities as ‘Target Table’ and ‘Include Table’ will create a capability map showing only Business Capabilities and ignoring all other related items.
Combine this option with the ‘Include Relationships’ option to further restrict the query to selected relationship types.
F – The ‘Include Relationships’ option provides the ability to exclude all other suggested relationship types except the selected ones.
In the example above Business Capabilities connected to Business Applications and/or Strategies only connected via the suggested relationships ‘impacts::impacted by’ and ‘Provided by::Provides’ will be shown—all other relationship types will be ignored.
Use this option to filter the view for specific suggested relationship types.
Leave this option empty to include all relationship types.
Combine this option with the ‘Target Tables’ option to further restrict the query to selected target tables.
G – Turn on the ‘Use Repository Browser Filters’ option to include global and private Repository Browser Filters on top of the ‘Include Tables’ and ‘Include Relationships’ to e.g. exclude all Business Applications which are decommissioned.
H – Turn on the ‘Include Not Related Shapes’ option to show elements which do not have any upstream or downstream related items. Turn off this option to hide elements which not not have any upstream or downstream related items.
I – Click the ‘Apply’ button to start building the Hierarchy Map.
Updating Hierarchy Map
The Hierarchy Map will not be updated automatically by running this feature again. The Hierarchy Map will created on top of the previous Hierarchy Map!
Updated about a month ago