Input tables of TemplateOne 1.0.0

Introduction

The TemplateOne release includes a Basic SQL connector. To use the TemplateOne, your input data needs to meet a defined format.

This page describes the input data fields for the Basic SQL Connector for TemplateOne 1.0.0. If you want to use a custom SQL connector for TemplateOne 1.0.0 you must make sure that the output data of your connector meets the required input format for TemplateOne 1.0.0.

TemplateOne packages

There are two available TemplateOne packages.

• TemplateOne-Event-log;
• TemplateOne-Cases-Event-log.

If your data for cases and events is available in one input file, you use TemplateOne-Event-log. If your data for cases and events is split up into two different input files, you use TemplateOne-Cases-Event-log.

This page contains an overview of the attributes for the input tables of the different TemplateOne packages. For each attribute, the name and a data type are displayed. Apart from that, it is indicated whether the attribute is mandatory.

Mandatory and optional attributes

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

• activity
• case_id
• event_end

It is possible that this data is available otherwise in your input file. For example, Event end can be calculated by combining a date attribute and a time attribute containing event end data.

Optional attributes can be used to get more detailed views in TemplateOne.

Custom attributes

Additionally, custom case and event fields for both case and event properties are available for TemplateOne.

• 30 fields of type text;
• 10 fields of type double;
• 10 fields of type datetime;

Custom fields have generic names. Below is an overview of the custom attributes that are available for TemplateOne.

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_event_text_{1...30}	text	N
custom_event_number_{1...10}	double	N
custom_event_datetime_{1...10}	datetime	N

When you use a custom field, you should rename the field in the TemplateOne app to a name that matches the value. See Adding custom attributes to an app.

TemplateOne-Event-log input data

Below is an overview of the input attributes for the Event_log table.

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.
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.
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.

TemplateOne-Cases-Event-log input data

Cases

Below is an overview of the input attributes for the Cases table.

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.

Below is an overview of the input attributes for the Event_log table.

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_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.