- Release notes
- Before you begin
- Managing access
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Process simulation
- Root cause analysis
- Simulating automation potential
- Starting a Task Mining project from Process Mining
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Transforming data
- Autopilot™ for SQL (preview)
- Structure of transformations
- Tips for writing SQL
- Exporting and importing transformations
- Viewing the data run logs
- Merging event logs
- Configuring Tags
- Configuring Due dates
- Configuring fields for Automation potential
- Activity Configuration: Defining activity order
- Making the transformations available in dashboards
- Data models
- Adding and editing processes
- Customizing process apps
- Publishing process apps
- App templates
- Notifications
- Additional resources

Process Mining
For the selected table, the required input fields for the table are displayed in the Required fields section on the Fields page.
The source fields detected in the input table are automatically mapped to the corresponding fields in the target table.
-
Make sure each field is mapped to the correct target field. If required, select a different field from the Target fields list to correct the mapping.
-
Select Next to continue.
The settings for the target input fields are automatically detected and you just need to check them.
Follow these steps to edit the settings for an input field.
-
Locate the field you want to configure and select the Edit field icon to open the Edit field panel for the selected field.
-
Edit the settings as desired and select Save.
The following table describes the table settings.
|
Setting |
Description |
|
Name |
The name of the field. Note:
Name is a mandatory field. |
|
Type |
The data type of the field.
Note:
Depending on field type you must specify parse settings to configure the field. |
|
Mandatory |
Option to define the field as mandatory. If selected, the field is required when publishing or importing the process app. An error is thrown then if the field is missing. If not selected, the field is considered optional. When it is missing, the field will be added with NULL values, such that subsequent SQL queries will not fail. |
|
Unique |
Option to define the field value have a distinct or unique value for each record. |
|
Not NULL |
Option to define that the field must have a value for each record. The field cannot be left empty or filled with a NULL value. |
The following table describes the available parse settings for the different field types.
|
Field type |
Parse settings |
|
Integer |
Thousand separator
|
|
Decimal |
|
|
Boolean |
Note:
True value and False value are mandatory settings and must be different. |
|
Date |
Date format (Check out Example parse settings for Date formats). |
|
Datetime | Date time format Date format (Check out Example parse settings for Datetime formats.) |
| Format | Example |
|---|---|
yyyy-mm-dd hh:mm:ss |
|
yyyy-mm-dd hh:mm:ss[.nnn] |
|
yyyy-mm-ddThh:mm:ss[.nnn] |
|
mm/dd/yy hh:mm:ss AM/PM |
|
mm-dd-yyyy hh:mm:ss[.nnn] |
|
dd-mm-yyyy hh:mm:ss[.nnn] |
|
yyyy-mm-ddThh:mm:ss[.nnn]+00:00* |
|
yyyy-mm-ddThh:mm:ss+00:00* |
|
dd/mm/yyyy hh:mm:ss[.nnn] |
|