This page describes the necessary steps to roll out a customized version of TemplateOne to end-users. It starts with the input data and covers all the steps that are needed to provide the data in a meaningful way to end-users.
Step 1: Set up the TemplateOne for development
Step 2: Customize TemplateOne
Step 3: Release the customized version of TemplateOne
Step 4: Configure the database connection for TemplateOne
Step 5: Run the transformations and load the data
Follow these steps to set up TemplateOne for development.
Upload the TemplateOne release (.mvtag) to the Superadmin Releases Tab.
Create a new app and use the released TemplateOne app as the base app. See Creating Apps.
Go to the Git repository and create a local checkout of the TemplateOne branch. This enables you to work on the content outside of Process Mining.
The local checkout contains several files and folders. See the illustration below.
Below is an overview of the main contents of the release.
Folder containing the information of the build of the Process Mining software.
Workspace settings that are relevant when working in Visual Studio Code.
System and process specific documentation. For example, how to configure the specific SQL connector, an explanation of the process, and applicable design choices.
Instructions on extracting data and loading it in the database. By default, CData Sync is used to extract data. A load-from-file extraction is included, that enables you to load raw data files that fit with the input of the connector.
Folder containing translation files and dashboard settings.
Scripts to automatically extract, transform, and load the data, that you can schedule in your production environment.
The dbt project containing the SQL statements to transform the data.
Git specific file that lists the contents of the app which should be ignored in version control.
Info on the connector and dashboard part that were combined to create this app.
Standard license file of the UiPath Process Mining product.
Release notes of the app.
Internal settings for the app. The contents of this file do not have to be updated.
See the illustration below for an overview of the setup.
Follow these steps to make the customized version of TemplateOne available to end-users.
These steps must be performed on the Process Mining server.
To load data from the SQL Server database for use in TemplateOne you must configure the connection to the SQL Server database. You can do this by specifying the Configuration Settings in an external configuration file in
.csv format. The
TemplateOne.settings.csv file is included in TemplateOne release.
All SQL Server databases that have a 64-bit version can be accessed using an ODBC connection. The required 64-bit ODBC driver must be installed on the UiPath Process Mining server, and the server must be able to access that specific system.
Follow these steps to configure TemplateOne.
Go to the Superadmin Workspaces tab, and locate the Dashboards folder. See the illustration below.
Go to the Superadmin Server data tab and upload the
Important: Make sure you use the exact name of the file (
;as delimiter and
“as quotation character.
- must contain two lines: a header line with predetermined field names, and a line containing all values.
Below is a list of the fields in the
TemplateOne.settings.csv that can be used to configure TemplateOne, with a description and expected or example values.
The name of the ODBC driver used for the SQL Server database connection.
The name of the server on which the SQL Server database is installed.
The name of the SQL Server database that is used for TemplateOne.
The name of the schema in the SQL Server database that is used for TemplateOne.
The user account that is used to log in to the SQL Server database.
Use credential store
Define whether the credential store is used.
Password of the account that is used to log in to the SQL Server database, or the password identifier from the credential store. In case the credential store is used, Use credential store should be set to true.
A credential store allows you to use passwords without showing the actual password. For the ODBC connection from the SAP Connector to the SAP database, it is also possible to use a Credential store to store the actual password of the SAP account in a secured way. For more information, seeUse a Credential Store](doc:using-the-credential-store).
Perform the following steps on the production server to run the transformations and load the data into the SQL Server database.
Configure the dbt project and the profiles. See Running a dbt project.
Run the SQL Connector:
Updated about a month ago