- Hardware and Software Requirements
- Server Installation
- Updating the License
- Deploying the UiPath Process Mining Profiler
- Deploying a Connector (.mvp)
- Updating UiPath Process Mining
- Updating a Customized Version of an App or Discovery Accelerator
- Installing a Training Environment
- Set up Single Sign-on Through Azure Active Directory
- Set up Single Sign-on Through Integrated Windows Authentication
- Adding Superadmin AD Groups
- Adding End-user AD Groups
- Two-Factor Authentication
- Introduction to AppOne
- Analyzing Data in AppOne
- Overview of Menus and Dashboards in AppOne
- Introduction to Purchase-to-Pay Discovery Accelerator
- Analyzing Data With Purchase-to-Pay Discovery Accelerator
- Overview of Menus and Dashboards
- Menu Compliance
- Deploying the Basic Connector
- Introduction to Basic Connector
- Input Tables of the Basic Connector
- Adding Tags
- Adding Automation Estimates
- Adding Due Dates
- Adding Reference Models
- Setting up Actionable Insights
- Setting Collapsible Charts
- Using the Output Dataset in AppOne
- Output Tables of the Basic Connector
- Introduction to SAP Connector
- SAP Input
- Checking the Data in the SAP Connector
- Adding Process Specific Tags to the SAP Connector for AppOne
- Adding Process Specific Due Dates to the SAP Connector for AppOne
- Adding Automation Estimates to the SAP Connector for AppOne
- Adding Attributes to the SAP Connector for AppOne
- Adding Activities to the SAP Connector for AppOne
- Adding Entities to the SAP Connector for AppOne
- HTML Panels
- Migrating Legacy Charts to New Charts
- Join Tables
- Global Tables
- Introduction to Table Items
- Display Format
- Rebrand and Restyle Apps and Discovery Accelerators
- Use Sharding in Your Applications
- Create an Anonymized Dataset
- Set up Automated Data Refreshes
- Use an Access Matrix to Enable Role-Based Access to Data
- Introduction to SQL Connectors
- Setting up a SQL Connector
- CData Sync Extractions
- Running a SQL Connector
- Editing Transformations
- Releasing a SQL Connector
- Scheduling Data Extraction
- Structure of Transformations
- Using SQL Connectors for Released Apps
- Generating a Cache With Scripts
- Setting up a Local Test Environment
- Separate Development and Production Environments
How to Use AppOne Connectors With TemplateOne
It is possible to use an existing AppOne connector to create an output dataset that can be loaded into TemplateOne. Since the data model of TemplateOne differs from the data model of AppOne you must either:
- rename the input tables of TemplateOne according to the names of output tables in the connector, or
- rename the output tables in the connector to fit the exact names of the input tables of TemplateOne.
For a clean state, you should disable outputting the
Global settings and
Reference models tables, as well as other tables that are not part of the TemplateOne data model.
Follow these steps to disable the output of a table.
Open the connector in your development environment and go to the Data tab.
Right-click on the table you want to exclude from the output.
Select Advanced - Options... from the context menu.
Unselect the Output in dataserver update option and click on OK.
See the illustration below for an example.
AppOne uses other attributes than TemplateOne. For example, attributes as
Case department and
Customer are not part of the data model of TemplateOne, but can easily be added. See Adding new attributes to an app or discovery accelerator. If desired, you can also add additional attributes to TemplateOne in the same way.
Another option is to map an TemplateOne attribute to an AppOne attribute. For example, you can map
Case value to
Amount. See Mapping Attributes.
You can also rename
Case value to
Case status attribute is part of the data model of TemplateOne, it is expected as an input attribute for TemplateOne. In AppOne
Case status is calculated in the app and not in the connector. This implies that if you want to use
Case status in TemplateOne, you must configure this in the connector and make sure that it is included in the output dataset.
Event Processing Time
Event processing time attribute is in TemplateOne expected as an Integer, representing the amount of time actually spent working for the event given in milliseconds. If you want to use the
Event processing time in TemplateOne, you must configure this in the connector and make sure that it is included in the output dataset.
Settings in TemplateOne
The only setting in TemplateOne is the
Default period on the
Globals table. The default value is using the maximum
Case start date, but you can change it to a different value according to your needs.
If you have configured this in an existing connector, you must now configure this directly in TemplateOne.
By default, TemplateOne does not provide a welcome screen. If you want to show a welcome screen to end-users, you must build this in TemplateOne.
By default, all charts are expanded in TemplateOne.TemplateOne does not provide collapsible charts. If needed, you can configure this in TemplateOne.