Process level pyramid and breadcrumb panel¶
The process level pyramid and the breadcrumb panel provide an overview of a diagram’s place within the overall process landscape.
The process level pyramid is displaying the hierarchy level of the current diagram:
Clicking a higher pyramid level will navigate you to the corresponding diagram level.
The breadcrumb panel displays the diagram hierarchy path from a top level diagram to the current diagram.
Clicking one of the bread crumbs (hierarchy levels) leads you to the corresponding diagram:
The process level pyramid is available for BPMN 2.0 and value chain diagrams. You can deactivate it in the attribute visibility configuration settings for Collaboration Hub.
Calculation of hierarchies/paths¶
The process level/diagram path calculation algorithm works as follows:
- The shortest path from the current diagram to any top level diagram (a diagram that is not referenced as a sub process) is calculated. Cycles are excluded (e.g. when two diagrams are referencing each other as sub processes).
- In case there are several shortest paths, a random choice will be made among them.
- All diagrams that are on the shortest path will be displayed in the breadcrumb panel as the diagram path.
Possible issues and troubleshooting:¶
In some cases, you might wonder why the process level pyramid is showing the diagram in a higher level then you expect. Then, your diagram path in the bread crumbs panel will always be shorter than you regard as correct.
In such cases, you typically have hierarchy structure similar to the example below. In the example, each process element stands for a diagram (either value chain or process) in the process hierarchy that is documented in Signavio Process Manager:
As you can see, the one process map seems to be located below the top level diagram. However, this process map technically has no parent diagram. Thus, the hierarchy/path calculation algorithm regards this diagram as top level and its child diagrams as second level, accordingly.
To address the issue, we recommend to integrate all process landscapes diagrams, which might e.g. provide department-specific overviews, properly in the hierarchy. In our example, this means to create a reference from the top level value chain to the supposedly second level value chain diagram:
Another but not so elegant alternative is not to publish the supposedly second level value chain diagram, if this makes sense for your use case: The calculation algorithm is considering only published diagrams, so the value chain will be ignored.