- Release notes
- Before you begin
- Getting started
- Managing access
- Working with process apps
- Creating process apps
- Loading data
- Customizing process apps
- Data transformations
- TemplateOne app template
- Purchase to Pay app template
- Order to Cash app template
- Basic troubleshooting guide
TemplateOne-MultiFiles input fields
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.
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.
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`.
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.
NULL
values.
Below is an overview of the input tables for TemplateOne-MultiFiles.
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
table contains the detailed information for the status, type, value and description for the related case.
Name |
Data type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the case the event belongs to. |
|
text |
N |
A user-friendly name to identify the case. |
|
text |
N |
The status of the case in the process. For example, open, closed, pending, approved, etc. |
|
text |
N |
The categorization of the cases. |
|
double |
N |
A monetary value related to the case. |
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
table contains information on the activities executed in the process.
Name |
Data type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The name of the event. This describes the step in the process. |
|
text |
Y |
The unique identifier of the case the event belongs to. |
|
datetime |
Y |
The timestamp associated with the end of executing the event. |
|
boolean |
N |
Indicates whether the event is manually executed or automated. |
|
double |
N |
The costs for executing the event. |
|
text |
N |
Information related to the event. |
|
datetime |
N |
The timestamp associated with the start of executing the event. |
|
text |
N |
The team that executed the event. |
|
text |
N |
The user who executed the event. |
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.
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_event_text_{1...30} |
text |
N |
custom_event_number_{1...10} |
double |
N |
custom_event_datetime_{1...10} |
datetime |
N |
custom_event_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.
Tags
table contains fields for tags that are defined in your process. If you upload tags in TemplateOne-MultiFiles, the Tags dashboard will be enabled.
Name |
Data type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the case the tag belongs to. |
|
text |
Y |
A user-friendly name to identify the tag. |
|
text |
N |
The category to which the tag belongs to. |