Input Tables of TemplateOne

Introduction

If you want to create a custom SQL connector for TemplateOne you must make sure that the output data of your connector meets the required input format for TemplateOne.

This page contains an overview of the attributes for each of the input tables of TemplateOne. 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 Fields

Your input data file can have different fields or different field names. However, there are some fields 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 fields 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 field and a time field containing event end data.

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

In the Event log tables in TemplateOne, the fields are grouped by mandatory and optional fields.

Tables

Below is an overview of the tables of the TemplateOne data model.

Table	Mandatory Y/N
Cases_base	Y
Event_log_base	Y
Tags_base	N
Due_dates_base	N

Cases_base

Below is an overview of the fields of the Cases-base table.

Name	Data type	Mandatory Y/N	Description
Case_ID	Text	Y	The unique identifier of the case.
Case	Text	N	A user-friendly name to identify the case.
Case_type	Text	N	The categorization of the cases.
Case_status	Text	N	The status of the case in the process. For example, ‘open’, ‘closed’, ‘pending’, ‘approved’, etc.
Case_value	Double	N	A monetary value related to the case.

Event_log_base

Below is an overview of the fields of the Event_log_base table.

Name	Data type	Mandatory Y/N	Description
Case_ID	Text	Y	The unique identifier of the case the event belongs to.
Activity	Text	Y	The name of the event. This describes the step in the process.
Event_end	Date + time	Y	The timestamp associated with the end of executing the event.
Event_ID	Integer	Y	A unique identifier of the event.
Event_start	Date + time	N	The timestamp associated with the start of executing the event.
Activity_order	Integer	N	If activities take place on the same time (in parallel), you can define their order here.
Team	Text	N	The team that executed the event.
User	Text	N	The user who executed the event.
Automated	Boolean	N	Indicates whether the event is manually executed or automated.
Event_detail	Text	N	Information related to the event.
Event_cost	Double	N	The costs for executing the event.

Note: Also if you want to set up integration with Automation Hub to enable business users to submit automation ideas, Event cost is mandatory.

Tags_base

Note: The Tags_base table must contain a unique entry for each combination of Case_ID and Tag.

Below is an overview of the fields of the Tags_base table.

Name	Type	Mandatory Y/N	Description
Case_ID	Text	N*	A unique identifier of the case.
Tag_ID	Integer	N*	A unique identifier of the tag.
Tag	Text	N*	A user-friendly name to identify the tag.
Tag_type	Text	N	The type of the tag.

* If you want to use tags in TemplateOne, which can be analyzed using the Tags dashboard, the fields for the Tags_base table must be loaded in TemplateOne. In this case, the attributes are mandatory.

Due_dates_base

Note: The Due_dates_base table must contain a unique entry for each combination of Event_ID and Due_date.

Below is an overview of the fields of the Due_dates_base table.

Name	Type	Mandatory Y/N	Description
Due_date	Text	N*	The name of the due date.
Actual_date	Date + Time	N*	The timestamp associated with the execution of an event.
Expected_date	Date + Time	N*	The timestamp associated with the expected execution of an event.
Event_ID	Integer	N*	A unique identifier of the event.

*If you want to use due dates in TemplateOne, which can be analyzed using the Due dates dashboard, the fields for the Due_dates_base table must be loaded in TemplateOne. In this case, the fields are mandatory.