- 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
- TemplateOne menus and dashboards
- 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
Process Mining user guide
Input tables of TemplateOne 2021.4.0
Introduction
This section 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 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.
In the Event log tables in TemplateOne, the attributes are grouped by mandatory and optional attributes.
Tables
Below is an overview of the tables of the TemplateOne data model.
| Table | Mandatory Y/N |
|---|---|
| Cases | Y |
| Events | Y |
| Tags | N |
| Due dates | N |
Cases
Below is an overview of the attributes of the Cases 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. |
Events
Below is an overview of the attributes of the Events 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 | Text | N * | 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. |
Event processing time | Integer | N ** | The amount of time actually spent working for the event given in milliseconds. |
* If you want to use the Compliance - Due dates dashboard, Event ID is mandatory. In this case, you also must load the required attributes in the Due dates - Due dates table.
** If you want to use the Efficiency - Automation dashboard the attributes Event cost and Event processing time are mandatory.
Also if you want to set up integration with Automation Hub to enable business users to submit automation ideas, Event cost and Event processing time are mandatory.
Tags
The Tags table must contain a unique entry for each combination of Case ID and Tag.
Below is an overview of the attributes of the Tags table.
| Name | Type | Mandatory Y/N | Description |
|---|---|---|---|
Case ID | Text | N* | A unique identifier of the case. |
Tag | Text | N* | A user-friendly name to identify the tag. |
* If you want to use tags in TemplateOne, which can be analyzed using the Compliance - Tags dashboard, the attributes for the Tags table must be loaded in TemplateOne. In this case, the attributes are mandatory.
Due Dates
The Due dates table must contain a unique entry for each combination of Event ID and Due date.
Below is an overview of the attributes of the Due dates 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 | Text | N* | A unique identifier of the event. |
*If you want to use due dates in TemplateOne, which can be analyzed using the Compliance - Due dates dashboard, the attributes for the Due dates table must be loaded in TemplateOne. In this case, the attributes are mandatory.
The Event ID in the Events table is also mandatory for using due dates.
See also Steps to roll-out TemplateOne.
Attribute type
Below is an overview of the different attribute types and their default format settings.
| Attribute type | Specification |
|---|---|
| Boolean | N/A |
| Date | Format: YYYY-M-D |
| DateTime | Date format: YYYY-M-D Time format: h [.zzz] |
| Double | Decimal separator:. (dot) Thousand separator: none |
| Integer | Thousand separator: none |
| Text | N/A |
Input format
Some of the attribute types of the input attributes can have multiple format settings which can differ. For example, two attributes can be both of type Date, but they can each have a specific format.
If your input data is of a different format than the default format in TemplateOne, you can edit the format settings for all the input attributes of that type in the Edit Datasource Attribute dialog in TemplateOne to match the format of your input data. See the illustration below for an example.
Changing the display format
If you want to use different display formats in TemplateOne than the default format that is set for the attribute type, you can change the display format settings in TemplateOne. For example, if you want to use a different currency string you can change the settings in the Display Format dialog.
Follow these steps to open the Display Format dialog.
| Step | Action |
|---|---|
| 1 | Click on Home button and select Settings.... |
| 2 | Click on DISPLAY FORMAT.... |
See the illustration below.
In a similar way, you can change the decimal separator or thousand separator for specific attributes.
For more information see Display Format.