# Input tables of TemplateOne 2021.4.0

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

## 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](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/templateone-compliance-due-dates#compliance---due-dates) dashboard, `Event ID` is mandatory. In this case, you also must load the required attributes in the [Due dates](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/input-tables-of-templateone-10#input-tables-of-templateone-202140) - Due dates table.

`**` If you want to use the [Efficiency - Automation](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/templateone-efficiency-automation#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

:::note
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](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/templateone-compliance-tags#compliance---tags) dashboard, the attributes for the `Tags` table must be loaded in **TemplateOne**. In this case, the attributes are mandatory.

### Due Dates

:::note
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](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/templateone-compliance-due-dates#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](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/input-tables-of-templateone-10#events) table is also mandatory for using due dates.

See also [Steps to roll-out TemplateOne](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/steps-to-roll-out-templateone#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:mm[:ss[[.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.

  ![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-54296-a5bb2c7b-210713af.webp)

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

  ![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-53447-7ceb9f7d-05fe2c41.webp)

In a similar way, you can change the decimal separator or thousand separator for specific attributes.

For more information see [Display Format](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/display-format#display-format).