Set up of a Multi-Event Log Analysis
Configure Process Visualization
Once the Data Model is loaded, the analysis can be set up to discover all processes (event logs) in context with each other. This refers to Use Case 1 mentioned here.
Within the analysis, all process-related components like the Process Explorer, Variant Explorer or Case Explorer refer to the Activity table marked as the Default Activity table in the Data Model (see the previous topic). However, the Variant Explorer, as well as the Process Explorer, allow dynamically choosing the Event Log that is visualized by selecting in the settings a “Custom dimension”. This dimension refers by default to the specified activity column of the default activity table. By ticking the “Custom dimension” option, it can be changed in the PQL Editor to any column of any Activity table in the Data Model.
 |
In the example below, the two Process Explorers have custom dimensions, one referencing the activity column of the Order-To-Cash activity table and one referencing the activity column of the Purchase-To-Pay activity table.
 |
Furthermore, users can now even combine two Event Logs into one Event Log with the PQL Function MERGE_EVENTLOG. Users that split for example the Purchase Requisition activities from the Purchase Order activities into two Event Logs, to save time writing lengthy transformations per activity, can now combine the two activities into one Event Log by merging them together.