Automated cache generation

Note: The information in this page is only applicable if you set up Actionable Insights in an app or Discovery Accelerator, or TemplateOne. If you are using a connector, these steps are not needed.

Introduction

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.

Step 1: Enable Live Data for the Actions and Queues Tables

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.

Step 2: Configure the 'Actionable Insights Integration Is Used' Expression

To prevent the app or Discovery Accelerator to sending the data immediately, the 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.

Note: The Actionable insights integration is used expression was created and set to true during Actionable Insights set up. See Enable Actionable Insights.

This can be achieved by using the 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.

When a user opens the app or Discovery Accelerator, or TemplateOne, 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.