Process Explorer
The Process Explorer is an analysis tool to use when taking an exploratory approach. It starts with showing the most frequent activities and connections. You can add further additional activities to the graph and analyze their impact on the process. Any number of Event Logs can be visualized together to understand the relationships between multiple processes.
There are two main configuration options for the process explorer:
You might be using a deprecated configuration
In July 2021, we implemented several improvements on the Process Explorer. For these improvements to work properly, a new configuration format is required.
Check that your configuration matches the schema below.
Basic Configuration
To configure a basic process explorer, you must define the event logs you wish to visualize in the component. Ensure that prior to creating a process explorer component you have the event logs defined in the eventLogsMetadata section of the Knowledge Model.
Attribute | Required | Type | Description |
|---|---|---|---|
eventLog | true | References Event Log ID’s defined in the eventLogsMetadata section of the Knowledge Model | |
id | true | String | Defines a unique identifier for the field. When not defined, an id is automatically generated. |
order | true | Integer | Defines the order in which the event logs are visualized. When not defined, the order is automatically generated. |
Single Event Log
The following diagram is an example of a single event log for the process explorer:
 |
Single Event Log - Component Configuration
Visual Editor View
 |
YAML Configuration
id: process-explorer-e6834feb-5710-4c8f-a74f-01b18d13b195
type: process-explorer
settings:
eventLogs:
- eventLog: O2C_EVENTLOG
id: 714ddb62-9753-4380-8d0d-b2ef59501124
order: 100Single Event Log - Knowledge Model Configuration
Visual Editor View
 |
YAML Configuration
eventLogsMetadata:
eventLogs:
- id: EL_ACTIVITY_TABLE__ACTIVITY_EN
displayName: Order Management
pql: "ACTIVITY_TABLE"."ACTIVITY_EN" Multiple Event Logs
Multiple processes can be visualized together in the Process Explorer. The event logs appear next to each other with transition lines that connect the processes.
Note
Event logs in the process explorer are visualized as independent processes with transition lines if the underlying data model is a Case-Centric data model.
The following diagram is an example of multiple event logs for the Process Explorer:
 |
Transitions for Multiple Event Logs
Connections between two processes are known as 'transitions'.
Transitions can be automatically added, based on the select event logs displayed above, or manually customized.
To manually customize transitions, use the following widget configurations.
Attribute | Required | Type | Description |
|---|---|---|---|
Transition | false | String | References Transition IDs defined in the eventLogsMetadata section of the Knowledge Model |
id | true | String | Defines a unique identifier for the field. If not defined, this is automatically generated. |
Multiple Event Logs - Component Configuration
Visual Editor View
 |
YAML Configuration
id: process-explorer-e6834feb-5710-4c8f-a74f-01b18d13b195
type: process-explorer
settings:
eventLogs:
- eventLog: O2C_EVENTLOG
id: O2C1
order: 100
- eventLog: P2P_EVENTLOG
id: P2P2
order: 200
transitions:
- transition: Transition_1
id: 6b8b47c5-747d-4215-b5cf-bcc4b28d82b7
order: 100
- transition: Transition_2
id: fb8a9d6b-6fdc-4300-9075-d033bf2cd890
order: 200Multiple Event Logs - Knowledge Model Configuration
Visual Editor View
 |
YAML Configuration
eventLogsMetadata:
eventLogs:
- id: O2C_EVENTLOG
displayName: Order To Case
pql: '"_CEL_O2C_ACTIVITIES"."ACTIVITY_EN"'
- id: P2P_EVENTLOG
displayName: Procure to Pay
pql: '"_MEL_EKPO_ACTIVITIES"."ACTIVITY_EN"'
transitions:
- id: Transition_1
displayName: O2C to P2P
firstEventLogId: O2C_EVENTLOG
secondEventLogId: P2P_EVENTLOG
type: INTERLEAVED
- id: Transition_2
displayName: P2P to O2O
firstEventLogId: P2P_EVENTLOG
secondEventLogId: O2C_EVENTLOG
type: INTERLEAVEDMulti-object Process Explorer
In the multi-object Process Explorer, the process is visualized as objects and their corresponding activities. An activity impacting multiple objects is shown only once and the objects intersect at these common activities.
Note
A multi object process explorer can only be used if the underlying data model is an Object-Centric data model.
Process Explorer automatically turns into the multi-object mode, once the View is built on an object-centric data model.
As in the Multi-Event-Log (MEL) case, several event logs can be configured to be available in Process Explorer.
Activities that are shared between different event logs are merged in the graph - they show up only once. A transition definition (as in a case centric data model) is not required.
The activity popup shows which event logs flow through the activity, and allows for filtering on each of them.
The activity count shown on the activity nodes is the distinct count of activities that happened.
The following diagram is an example of a multi-object Process Explorer:
Multi-object Process Explorer - component configuration
Visual Editor View
Event logs for multiple objects can be configured in Process Explorer. Transitions are not applicable for multi-object Process Explorer.
Advanced Configurations
For more advanced configuration options, please use the following:
Attribute | Required | Type | Options | Description |
|---|---|---|---|---|
name | false | String | Free text | The title for the component |
Infotext title content | false | String | Free text | Provides additional information about the component  |
selectedKpiViewId | false | String | Standard KPI Views STANDARD_KPI_CASE_COUNT (default) STANDARD_KPI_AVG_THROUGHPUT_TIME STANDARD_KPI_MEDIAN_THROUGHPUT_TIME STANDARD_KPI_TRIMMED_MEAN_THROUGHPUT_TIME STANDARD_KPI_ACTIVITY_COUNT Custom KPI View KPI Views Defined in the Event Logs section of the Knowledge Model. | Defines the default KPI View for the component when the user first visits the View. If nothing is defined for this attribute the Case Count KPI View is shown. Example: selectedKpiViewId: STANDARD_KPI_MEDIAN_THROUGHPUT_TIME  |
hideKpiSwitcher | false | Boolean | true | false (default) | Defines if the KPI Switcher is visible to the end user or not. If false the KPI switcher will be visible  If true the KPI switcher will be hidden  |
graphControls | false | string | panel | sliders (default) | Defines the interaction mechanism with the graph. In sliders mode all the activities from the eventlog are considered for visualizing the graph. In panel mode, the deselected activities are not considered to visualize the graph. Due to this, the KPIs on connections between any 2 activities can be different in the 2 modes. If ‘sliders’  If ‘panel’  |
YAML
id: process-explorer-e6834feb-5710-4c8f-a74f-01b18d13b195 type: process-explorer settings: eventLogs: - eventLog: P2P_EVENTLOG id: 9a51c727-f8c4-4908-9fd1-445598135171 order: 100 - eventLog: O2C_EVENTLOG id: O2C1 order: 200 graphControls: panel selectedKpiViewId: STANDARD_KPI_MEDIAN_THROUGHPUT_TIME hideKpiSwitcher: true name: Process Explorer infoText: content: This is the process explorer title: PE Description transitions: - transition: Transition_1 id: 780c7147-21a2-4459-beeb-85ce057600f9 order: 100 - transition: Transition_2 id: a71008f7-e4a1-4486-90fb-acc2b2b4b663 order: 200