Subscribe

UiPath Process Mining

The UiPath Process Mining Guide

Loading data into TemplateOne

Introduction

Always make sure that your input data is formatted according to the TemplateOne data model. See Input tables of TemplateOne.

To use the TemplateOne you must load your data into TemplateOne. By default, TemplateOne is configured to load datafiles that have been exported from a connector, but it is also possible to directly load files into TemplateOne without using a connector. See Directly loading data in TemplateOne.

You can also use a connector to create an output dataset that can be used as input data for TemplateOne. In this case the steps to roll out TemplateOne to end-users are similar to AppOne. See From Data to Dashboard for a complete overview.

Using an existing AppOne connector

It is possible to use an existing AppOne connector to create an output dataset that can be used as input data for TemplateOne This can for example be the Basic Connector for AppOne, the SAP Order-to-Cash Connector for AppOne, or the SAP Purchase-to-Pay Connector for AppOne. See How to use AppOne connectors with TemplateOne.

Building a connector from scratch

Instead of using an existing AppOne connector, you can also build your own connector for use with TemplateOne. In general, any technology can be used to build a connector. However, you must make sure that the output data of the connector matches the input data of TemplateOne. See Input tables of TemplateOne.

When building you own connector you can use the Basic Connector as a template and modify it to use it for TemplateOne. See How to use AppOne connectors with TemplateOne.

📘

Note

If you want to add business data to TemplateOne, for example, tags, due dates, or automation estimates, you must provide a proper dataset for use with TemplateOne. See Adding Tags, Due dates, or Automation estimates to TemplateOne.

Updated 4 months ago

Loading data into TemplateOne


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.