Automation manager

Introduction

Automation manager enables you to manage automations connected to Process Mining. With Automation manager you can select Orchestrator queues to be used for automations triggered by business users from the process app.

Automation manager is integrated in the dashboard editor. Refer toWorking with the dashboard editor for details.

Important:

Publish your process app after adding or editing an automation to make the automation available to business users. Refer to Publishing process apps.

Also make sure that business users have the proper access rights in Orchestrator to access the queue. Refer to Default roles for details.

Manually triggered automations and automatically triggered automations

There are two different types of automations that can be triggered from a process app.

Manually triggered automations are initiated by business users from the process app dashboards.
Automatically triggered automations are initiated when predefined conditions, determined by tags, are met during data ingestion for the process app.

Note:

Manual triggers can be done from both the development and published app. Automatic triggers are only applied when running ingestions on a published app.

Manually triggered automations

When you select the Manual trigger type for the automation, business users can trigger the automation from the published process app. The Trigger an automation option is available on most dashboards and charts. Check the illustration below for an example.

When the user has selected cases that are candidate for automation ,the Trigger an automation option can be selected to enter the input data for the automation. Check the illustration below for an example.

For every case that is selected, a Queue item is created in the Orchestrator queue that will trigger the automation defined in Studio.

Refer to Triggering an automation from a process app for details on how to trigger an automation from a published process app.

Automatically triggered automations

Automated triggers can trigger automations when specific events occur within the process. This allows for immediate attention to a case for enhanced efficiency and streamlined workflows.

When you select the Automatic trigger type for the automation, the automation is triggered automatically when the trigger conditions have met. The trigger conditions are determined by tags that are evaluated any time data for the process app is ingested. Each case that meets the conditions creates a Queue item in the Orchestrator queue, which initiates the automation defined in Studio.

Opening Automation manager

Select the Automation manager button in the upper right corner of the dashboard editor to open Automation Manager. The Automation manager page is displayed, showing the automations defined for your process app.

Building an automation

You can start building an automation in Studio directly from Automation manager.

In Process Mining open the process app for which you want to enable automation integration in the Dashboard editor. Refer to Working with the dashboard editor for details.
In the Dashboard editor, select the Automation manager option to open the Automation manager.
Select Build automation to open Studio. Refer to Automation manager for details.

Adding an automation

Follow these steps to add an automation for your process app:

In Automation manager, select + Connect automation. The Add queue page is displayed, showing all Orchestrator queues that have Specific data JSON schema. Refer toSetting up Automation integration.
Select the queue you want to use for the automation. The required input fields for the queue are displayed in the Properties panel.
Select the type of trigger for the automation from the Trigger list box.
Map the queue input fields to the appropriate data fields of your process app.

Important:
Check out the data type of the queue input fields defined in the Specific data JSON schema and make sure to map the input fields to a Process Mining data field with the correct input type. See App Templates.

Instead of mapping to a specific data field, you can select the Busines user input option for a text input field. This enables business users to enter a free text when triggering an automation.
Note: The Business user input option is only applicable to Manual triggers.
Enter the Maximum number of cases sent at once to limit the number of cases that can be sent to Orchestrator.

Note:
As an analyst, it is important to consider limiting the number of cases a business user can send to Orchestrator based on the specific use case. By default, the system allows 50 cases to be sent to the queue, but the range can be adjusted from 1 to 1000, providing flexibility for different scenarios.
Select the type of the trigger for the automation from the Trigger list box.
- If you want to configure an Automatic trigger for an automation, add the tags to define the trigger conditions. A case that meets a condition when the filter is evaluated will be sent to Orchestrator.
  
  Note:
  Each trigger condition is evaluated separately. For example, Case 001 has tags A and B. When you have set the trigger conditions for both A and B, this case will be sent to Orchestrator twice (one based on condition A, and one based on condition B).
Select Save.

Editing an automation

Follow these steps to edit an automation.

In Automation manager, locate the automation you want to edit on the list of automations and select .
Change the settings as desired.
Select Save.

Refreshing the queue

Important:

If any changes are made to the Orchestrator queue, you need to refresh the queue in Process Mining. For example, when the Specific data JSON schema has changed, or when the name or description of the queue was edited in Orchestrator. To refresh the queue in Process Mining, you edit the automation in Automation manager.

Follow these steps to refresh the queue for an automation.

Locate the automation for which you want to refresh the queue and select .
Select the Refresh button at the top of the properties panel. See the illustration below.
Select Save.