Configuring the Network Explorer
Celonis Academy course available
There's a Celonis Academy course that guides you through setting up the Network Explorer, see: Celonis Academy - Set up the Network Explorer.
Network Explorer (formerly Object Link) component allows you to examine how objects are related across your business. By choosing different node dimensions, you can explorer your object-to-object relationships by country, plant, material, or distribution and the KPI to display for each object.
You can configure the Network Explorer in two ways:
Network Explorer provides the visualization for the End-To-End Lead Times App for object-centric process mining, and supports advanced use cases such as material margins or carbon footprint calculations.
 |
Configuring the Network Explorer in views
You can configure the Network Explorer for your view by dragging and dropping the Network Explorer component into your view:
 |
With the Network Explorer component in your view, you can then use the component settings menu to configure it.
You have the following options here:
Node dimensions: In the Network Explorer, Objects are synonymous with nodes (a graph term), which are the data points you’d want visualized.
Default dimension: Allows you to define which of the dimensions/ breadcrumbs is selected by default. If none is defined, the first one is taken.
Edge labels: An edge label added to the visual from a Knowledge Model KPI. You can configure more edge labels, but only the first one will be shown.
Node labels: A node label added to the visual from a Knowledge Model KPI. You can configure more nodeLabels, but only the first one will show on the node. The others will appear in the context menu.
Layout: Select how the Network Explorer is visually displayed in your view.
The following layout options are available:
Hierarchical layouts: top to bottom, bottom to top, left to right, right to left
Based on spring force algorithms. Use for larger networks, use for smaller networks.
Circular
Exclude from user filtering: When a user is filtering the whole view, this component will remain unfiltered.
Can't be used to set filters: While the user can interact with this component, their selections can't then be used to filter the whole view.
 |
This YAML definition illustrates the main elements:
type: signal-link-explorer
settings:
defaultNodes: CASE_TABLE.PLANT
nodes:
- attribute: CASE_TABLE.COUNTRY
order: 0
- attribute: CASE_TABLE.PLANT
order: 1
- attribute: CASE_TABLE.MATERIAL_GROUP
order: 2
layout: SPRING_FDP
edgeLabels:
- field: KPI_DUMMY
nodeLabels:
- field: KPI_DUMMYThe following elements are used:
defaultNodes: Allows you to define which of the dimensions/ breadcrumbs is selected by default. If none is defined, the first one is taken.
nodes: Allows you to define multiple nodes (which will appear in the breadcrumbs).
order: Defines the order of the breadcrumbs. If no order is given, it defaults to 0. If there are multiple orders with the same number, the order of the attribute in this list is respected.
layout: Chooses the layout of the graph.
edgeLabels: An edge label added to the visual from a Knowledge Model KPI. You can configure more edge labels, but only the first one will be shown.
nodeLabels: A node label added to the visual from a Knowledge Model KPI. You can configure more nodeLabels, but only the first one will show on the node. The others will appear in the context menu.
Understanding network explorer layouts
The layout: element in the YAML has a one-to-one correspondence with the values in the Layout dropdown in the visual editor.
What you see in the Layout dropdown in the YAML | What you see in the Graph Layout dropdown in the visual editor | Description |
|---|---|---|
Top to Bottom Hierarchy | HIERARCHY | Hierarchical layout: top to bottom. |
Bottom to Top Hierarchy | HIERARCHY_BT | Hierarchical layout: bottom to top. |
Right to Left Hierarchy | HIERARCHY_RL | Hierarchical layout: right to left. |
Left to Right Hierarchy | HIERARCHY_LR | Hierarchical layout: left to right. |
Edges with Minimum Crossing | SPRING_FDP | Based on spring force algorithms. Use for larger networks. |
Edges with Equal Length | SPRING_NEATO | Based on spring force algorithms. Use for smaller networks. |
Circular | CIRCLE | Circular layout. |