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. See Working with the dashboard editor.

Important:

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

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

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.

Tip:

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

1. In Process Mining open the process app for which you want to enable automation integration in the Dashboard editor. See Working with the dashboard editor.

2. In the Dashboard editor, select the Automation manager option to open the Automation manager.

3. Select Build automation to open Studio.

   

   See Automation manager.

Building an automation

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

1. Select Build automation to open Studio.

Adding an automation

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

1. In Automation manager, click + Connect automation. The Add queue page is displayed, showing all Orchestrator queues that have Specific data JSON schema. See also Setting up Automation integration.

2. Select the queue you want to use for the automation. The required input fields for the queue are displayed in the Properties panel. See the illustration below.

   

3. 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 Custom text option for a text input field. This enables business users to enter a free text when triggering an automation. For example a description or an email address.
   
4. Click Save.

Editing an automation

Follow these steps to edit an automation.

1. In Automation manager, locate the automation you want to edit on the list of automations and click .

2. Change the input field mappings if desired.

3. Edit the Maximum number of cases sent at once if desired.

   Note:

   By default, the maximum number of cases that can be sent at once from an automation is 50, but you can change the number. The maximum number of cases can be set to a number between 1 and 1000.

4. Click 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.

1. Locate the automation for which you want to refresh the queue and click .

2. Click the Refresh button at the top of the properties panel. See the illustration below.

   

3. Click Save.

Removing an automation

Follow these steps to remove an automation.

1. Locate the record access policy you want to remove from the Record access policies list and click .

The automation is removed from the list of automations.