- Working With Dashboards and Charts
- Working With Process Graphs
- Showing or Hiding the Menu
- Context Information
- Root Cause Analysis
- Sending Automation Ideas to UiPath Automation Hub
- Filters
- Simulating Automation Potential
- Tags
- Due Dates
- Compare
- Export
- Triggering an automation from a process app
- Starting a Task Mining project from Process Mining
Deliverables
Introduction
A UiPath Process Mining Connector consists of the following deliverables. Each deliverable is described in more detail on the corresponding pages.
- Extractors to extract data from a source system, see Extractors.
- Transformations to transform the source data into a given data model, see Transformations.
- Datasets to make it easy to use and validate the connector, see Datasets.
- Documentation to explain how to use and customize the connector, see Documentation.
- Scripts to automate the extraction, transformation, and loading of data into an app, see Scripts .
- Tests to validate whether transformations are applied correctly, see Tests.
Repository
A Process Mining Connector is stored in a repository with a standardized directory structure. The UiPath/ProcessMining-devkit-connector
repository should be used as a template and already contains the correct structure and files. Below is an overview of the
structure of the UiPath/ProcessMining-devkit-connector
repository.
File/folder |
Description |
More information |
---|---|---|
|
Contains Visual Studio Code setting files. |
|
|
Connector & App Framework 0.8.1 Contains: • • Connector & App Framework 0.8. Contains:
|
|
|
Contains folders with descriptions of extraction methods for this connector. |
|
|
Contains a sample dataset. |
|
|
Contains the scripts necessary to automate running the connector. |
|
|
Contains a the dbt project that defines the transformations. |
|
|
The |
|
|
Contains an introduction to the connector. |
|
|
Contains the license information for the connector. |
|
|
Contains settings for this connector. |
|
|
Contains licenses for all third party tools used as part of the connector, directly or indirectly. |
* third-party_licenses.txt
is available from version 0.8.1.
Settings.json (Connector & App Framework 0.8.1)
The settings.json
file contains the following fields:
-
framework-version: the version of the Connector & App Framework that was used to create this connector.
Below is an example
settings.json
.{ "framework-version": "1.0" }
{ "framework-version": "1.0" }
Settings.json (Connector & App Framework 0.8)
The settings.json
file contains the following fields:
- **name:**the display name of the connector.
- app: a reference to the repository of the implemented app.
- framework-version: the version of the Connector & App Framework that was used to create this connector.
Below is an example settings.json
.
{
"name": "SAP connector for Purchase-to-Pay Discovery Accelerator",
"app": "P2P-app",
"framework-version": "1.0"
}
{
"name": "SAP connector for Purchase-to-Pay Discovery Accelerator",
"app": "P2P-app",
"framework-version": "1.0"
}