The block diagram is a very generic view to display any kind of graph data. The view follows your current context and depending on how you have managed the view modifiers options and perspectives, the components it is connected to.
This view is great to use when you are looking to create process diagrams, deployment diagrams, organization charts, or any view where you expect more structure in the flow. This view does not specifically take sequence into account.
Table of Contents
Pro Tips:
Use groups (group by parent, workspace or reference) to clarify what you are looking at
Remember direction matters! (IT often thinks "bottom up" while the business users think "left right" or "top down".)
The configuration options to manage the degrees of relationships and reference filtering are in the first drop down:
Read about Graph Traversal to get more details about using the degrees of relationships and advanced settings.
Another configuration option is the drop-down to configure the layout direction:
And there is a toggle to exclude unconnected components:
Also Grouping is a very powerful feature to tailor a view.
Image Icons can be Dragged and Dropped onto Components in Block Diagram
The use of icons enhances engagement by making your content visually appealing, engaging, and easy to understand.
In your storytelling, icons are important visuals
A visual icon conveys information in an easy-to-remember and recognizable way
Icons help people consume information more quickly
Simply follow these steps:
Drag your image icon onto your Block Diagram visualization
There will be a Drop Zone (dashed lines) around components where you can drop your image icon
Select the component you want to use and drop your image icon there
A copy of the image icon will be automatically uploaded to the workspace's document archive
---
To dig more into Block Diagram, check out these related articles:
FAQ:
1. When opting for a "Top to Bottom" layout, can we affirm that components positioned at the top will generally have either no incoming references or the least, while those at the bottom will typically have the most incoming references? Could you shed light on the criteria or logic employed in determining the layering of components?
The layering strategy places each node in the optimal layer to minimize the layer distances. The layer distance of an edge is the absolute difference between the layer numbers of its source and target node. The layer assignment will minimize the overall sum of the layer distances of all edges in the layout.