- 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
Automated cache generation
When sending Actions and Queue items from Process Mining to Orchestrator, most likely you want to send the Actions and Queue items from live data. In this case, you can set up automated cache generation for your dataset. This page describes the additional steps needed when you want to automate cache generation for an app or Discovery Accelerator when using Actionable Insights.
Follow these steps to enable Live data for the Actions and Queues tables.
|
Step |
Action |
|---|---|
|
1 |
Open the app or Discovery Accelerator in your development environment and go to the Data tab. |
|
2 |
Locate the Actions table. |
|
3 |
Right-click and select Edit... from the context menu. |
|
4 |
Enable the Live data option and click on OK. |
|
5 |
Repeat step 3 and 4 for the Queues table. |
When using live data, the data will be sent to Orchestrator immediately after the user opens the app or Discovery Accelerator, or TemplateOne. However, preferably the data should be refreshed first, which means that the cache should be regenerated.
Actionable insights integration is used expression in the Actionable insights group must be false when the user opens the app or Discovery Accelerator, or TemplateOne.
Actionable insights integration is used expression was created and set to true during Actionable Insights set up. See Enable Actionable Insights.
Name field from a System table. Follow these steps to configure the 'Actionable insights integration is used' expression.
|
Step |
Action |
|---|---|
|
1 |
Right-click on the Actionable Insights table group and select New table - System table.... |
|
2 |
Rename New_table to, for example, User_info. |
|
3 |
Right-click on User_info and select Edit.... |
|
4 |
Make sure the Table scope is set to Current user and click on OK. |
|
5 |
In the table items list, right-click on the Name attribute and select Availability - Public. |
|
6 |
Right-click on the
Actionable insights integration is used expression and select Edit...
|
|
7 |
Click Yes to import the attributes. |
|
8 |
Replace
true with the boolean condition User_info.Name = null and click on OK. See the illustration below for an example.
|
Name will be filled and the boolean will be false and the data will not be sent to Orchestrator. When the cache generation is triggered, Name is empty/null, the boolean becomes true and the data will be sent to Orchestrator.
