|
Reuse the Event Log Template to Define Your Event Log |
Scroll Previous Topic Top Next Topic More |
In the script tab 1C. Load EventLog a table EventLog is defined. The fields in this table are divided in two categories ProcessAnalyzer information and Event information.
Process analyzer information |
event informaton |
|---|---|
Is needed to be able to apply Process Mining on an event log - fields as Case ID, activity description, and at least one timestamp are required. |
Optional context information for single event. |
How to reuse these fields in the event log template is described in the section below. |
How to reuse these fields in the event log template please refer to Reuse the Context Information Template. |
ProcessAnalyzer information
This part of the EventLog table needs to be filled with CaseID and activity-related information. Rename the fields before the "as", this represents the field name (column name) of the event log that is read in.
|
Do never change the field names CaseID, ActivityType, ActivityTypeID, ActivityStartTimestamp and ActivityEndTimestamp after the "as". |
1.Change the field names before "as" to match the names of your data.
If your data fields (as in the Helpdesk example) are already named like CaseID, ActivityType, ActivityTypeID, ActivityStartTimestamp and ActivityEndTimestamp, you can keep them unchanged.
2.If you don't have an ActivityTypeID, you don't need to do anything. The script recognizes automatically the necessary fields. In the case this field is not in your table, it will be created automatically. Otherwise, include it in your EventLog table.
3.If there are timestamps in your data, format them as your data is structured. The syntax is:
Timestamp(Timestamp#("DataTimestampFieldName", 'YYYY-MM-DD hh:mm:ss')) as ActivityStartTimestamp
In this example, the value in the field DataTimestampFieldName looks like this: 2019-11-26 15:20:04. For this reason, the formatting in the ActivityStartTimestamp line is 'YYYY-MM-DD hh:mm:ss'.
If the timestamp in your data is structured like 26/11/2019 15:25, use 'DD/MM/YYYY hh:mm'.
Another example could be 26.Nov.19 16:22:11:000, which is formatted as 'DD.MMM.YY hh:mm:ss:fff'. If you want to display the milliseconds in the app, then delete the square brackets surrounding the .fff in the variable timestamp format (Simple_Init tab). See the Qlik help for more information.
4.If for the activities exists a specific sorting criteria apart from their timestamp, add it as SortingColumn. If not, define the column as Null() as SortingColumn.
|
The sorting criteria must consist of numeric values between 0 and 99999998 with lower numbers beeing sorted first. |
SortingField as SortingColumn
In the Helpdesk example, the timestamps are already formatted. For this reason, it was not necessary to add the clause timestamp#().
For further information on timestamp conversion, please see Qlik's help.
EventLog: //Log table name: "EventLog"
LOAD
//ProcessAnalyzer information
CaseID,
"ActivityName" as ActivityType,
Timestamp(ActivityStartTimestamp) as ActivityStartTimestamp,
Timestamp(ActivityEndTimestamp) as ActivityEndTimestamp
Helpdesk example:
EventLog: //Log table name: "EventLog"
LOAD
//ProcessAnalyzer information
CaseID,
ActivityType,
Timestamp(ActivityStartTimestamp) as ActivityStartTimestamp,
Timestamp(ActivityEndTimestamp) as ActivityEndTimestamp
Tutorial
Start the video below to see a short tutorial about how to use the sheet.
