TemplateOne-MultiFiles input fields

Introduction

If your data for cases and events is split up into different input files, you use the TemplateOne-MultiFiles app template.

If you want to create a new TemplateOne process app, you must upload a dataset that contains the data to be used in the TemplateOne.

For each table, this must be a tsv (tab-separated) file or .csv (comma-separated) file that contains a column for each input field.

This section contains an overview of the input tables for TemplateOne-MultiFiles. For each field, the name, the data type, and a short description are displayed. Apart from that, it is indicated whether the field is mandatory.

Important: Table names and field names are case-sensitive. Always make sure that the field names (column headers) in your dataset match the field names in the table below and that the file names match the table names.

If you are extracting the data using CData Sync, `_raw` has to be added to the table names listed below, e.g. `Event_log_raw`.

Mandatory and optional fields

Your input data file can have different fields or different field names. However, there are some fields mandatory for TemplateOne, which means that the data must be available in your input data file for a correct working of TemplateOne.

Note: When a field is mandatory, it should not contain NULL values.

Below is an overview of the input tables for TemplateOne-MultiFiles.

Field types

Below is an overview of the different field types and their default format settings.

Field type	Format
boolean	`true`, `false`, `1`, `0`
datetime	`yyyy-mm-dd hh:mm:ss[.ms]`, where `[.ms]` is optional.
double	Decimal separator: `.` (dot) Thousand separator: none
text	N/A
integer	Thousand separator: none

Cases

The Cases table contains the detailed information for the status, type, value and description for the related case.

Name	Data type	Mandatory Y/N	Description
`case_id`	text	Y	The unique identifier of the case the event belongs to.
`case`	text	N	A user-friendly name to identify the case.
`case_status`	text	N	The status of the case in the process. For example, open, closed, pending, approved, etc.
`case_type`	text	N	The categorization of the cases.
`case_value`	double	N	A monetary value related to the case.

Custom Case fields

Additionally, custom case fields are available for TemplateOne.

30 fields of type text;
10 fields of type double;
10 fields of type datetime;
10 fields of type boolean;
10 fields of type duration.

Custom fields have generic names. Below is an overview of the custom fields that can be used in a process app.

Name	Data type	Mandatory Y/N
custom_case_text_{1...30}	text	N
custom_case_number_{1...10}	double	N
custom_case_datetime_{1...10}	datetime	N
custom_case_boolean_{1...10}	boolean	N
custom_case_duration_{1...10}	integer	N

When you use a custom field, you should rename the field in using Data manager to a name that matches the value. See Fields.

Custom fields that are empty in your dataset, are not displayed in Process Mining.

Event_log

The Event_log table contains information on the activities executed in the process.

Name	Data type	Mandatory Y/N	Description
`activity`	text	Y	The name of the event. This describes the step in the process.
`case_id`	text	Y	The unique identifier of the case the event belongs to.
`event_end`	datetime	Y	The timestamp associated with the end of executing the event.
`automated`	boolean	N	Indicates whether the event is manually executed or automated.
`event_cost`	double	N	The costs for executing the event.
`event_detail`	text	N	Information related to the event.
`event_start`	datetime	N	The timestamp associated with the start of executing the event.
`team`	text	N	The team that executed the event.
`user`	text	N	The user who executed the event.

Custom Event fields

Additionally, custom event fields are available for TemplateOne.

30 fields of type text;
10 fields of type double;
10 fields of type datetime.
10 fields of type boolean;
5 fields of type duration.