- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- Getting Started with TemplateOne
- Steps to roll-out TemplateOne 1.0.0
- Input tables of TemplateOne 1.0.0
- Adding custom attributes
- Configuring the context bar
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Input tables of TemplateOne 1.0.0
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.
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.
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
date attribute and a time attribute containing event end data.
Optional attributes can be used to get more detailed views in TemplateOne.
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.
Event_log table.
|
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. |
|
|
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. |
|
|
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. |
Cases table.
|
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. |
Event_log table.
|
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. |
|
|
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. |
