- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- 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
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- 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
- Useful resources
Connector Data Model Design
Your data model can be built in different ways. There is a trade-off between comprehensibility, effort, and performance for the user. Without restricting the data volume, there are trade-offs you can make to ensure the Connector does not become slow.
While a slow Connector may impact the performance experience of a developer, it will have no impact on the end-user, if the output file is the same. Sometimes it may be worthwhile to invest in the design phase and to accept a slower performance when developing a well-performing dataset or application for the end-users.
- Avoid unions where possible
- Set the availability of attributes that are not used in the output dataset of the Connector to private/hidden where possible.
For cached data, the startup time of the application is independent of the number of columns. When data is pre-calculated and cached, it can be loaded directly from the cache when it is requested.
Extracting data from source systems can be time-consuming. It is recommended to schedule the cache updates, for example outside production hours.
Besides the extraction of data, during cache generation, the data is also transformed into the UiPath Process Mining internal format and all calculations that do not depend on user input, are cached.
For calculations that depend on user input, the initial state is cached. When the user changes a control or filter that changes the calculation, the calculation is performed again. Keeping these recalculations to a minimum is very important in good application design.
