Create an insight trigger

Insight triggers help you to check your processes for certain aspects, for example, when activities exceed a certain throughput time. You can define insight triggers to check activities or cases for insights. When you check activities for insights, an insight is created for each activity in a case that meets an insight condition. When you check cases for insights, an insight is created for each case in which at least one activity meets the condition. For every case or activity that meets the specified condition of an insight trigger, a defined workflow can be triggered automatically. For example, you can select a generic webhook/endpoint or Process Governance as a target system, and you can trigger e-mail notifications to inform users about insights.

Notes

The number of e-mails per tenant per day is limited to 1000.
The number of e-mails per insight trigger run is limited to 100. All additional e-mails will be skipped for that run.
External applications that are triggered as a target system must support an endpoint on port 443 with the HTTPS protocol.

Procedure. Procedure

Open the Insight actions section.
Create an insight trigger.
1. If you do not have an insight trigger, you can click Create insight trigger on the Overview page. The Condition dialog of the Create insight trigger wizard opens.
2. If you have insight triggers, click Insight triggers to open the Insight triggers page. The page displays the available insight triggers, including considered cases, type, and current status.
  Click Create. The Condition dialog of the Create insight trigger wizard opens.
Select whether you want to check cases or activities for insights.
Click Next. The Configuration dialog opens.
Specify a name, a unique identifier, and an optional description for the insight trigger. By default, the specified name is set as the identifier.
Click Next. The Workflow trigger dialog opens. Configure the trigger action if the trigger condition is met.
If the trigger is not supposed to execute a workflow, enable the Skip action trigger (log mode only) option and click Create. The option is disabled by default. When the option is selected, a workflow is not triggered and only the captured insights are displayed.
Select the workflow system to be triggered in the Target system drop-down menu. The Generic webhook/endpoint target system is selected by default.
1. If you select Generic webhook/endpoint as a target system, configure the connection to the relevant workflow system. Please ask your workflow system administrator for the required data.
  Specify the workflow webhook URL. The URL is used to trigger the workflow defined in the workflow system.
  If user credentials are required to log in to the workflow system, click Add credentials and specify a user name and password.
  Example
  Click Next.
2. If you select E-mail notification as a target system, specify the recipients of the e-mail and configure the content of the notification.
  Enter the recipients of the e-mails in the Send to field. You can specify multiple users and user groups. Please note that users without a specified e-mail address are marked with a red dot. Click Customize e-mail notification to configure the notification layout and content in the Mail builder. You can also configure the e-mail notifications later.
  Example
  Click Apply.
3. If you select ARIS Risk and Compliance as a target system, configure the settings of the relevant workflow system. Please ask your workflow system administrator for the required data.
  Make sure that the ARIS Risk and Compliance server is running.
  Specify the issue creator in the relevant input field. The issue creator is the user for whom the issue is automatically created in ARIS Risk and Compliance when an insight is triggered. Note that for each triggered insight, an issue is created in ARIS Risk and Compliance. Consider this when defining the insight trigger condition to avoid an issue overflow for the issue creator.
4. If you select Process Governance as a target system, configure the settings of the corresponding workflow system. Please ask your workflow system administrator for the required data.
  Check that the Process Governance server is running.
  Specify the assignee in the corresponding input field. The user specified in the Assignee field is passed on to the workflow as input. In the provided example mini workflow, a task will be created for this user when an insight is triggered. You can select any available user, but only a user with at least the ARIS Connect Viewer license privilege can process the assigned task.
  Note that for each triggered insight, a governance process instance is created in Process Governance. Consider this when defining the insight trigger condition to avoid a task overflow for the assignee. Process Governance only accepts 60 tasks per hour.
  In the corresponding drop-down menu, select a governance process to be created for the specified assignee. The menu offers only processes for which ARIS Process Mining is specified as a context in ARIS Architect. For details on configuring the context for executable processes, see the ARIS Architect online help.
  Process Governance provides a mini workflow for ARIS Process Mining insights. The mini workflow can be used as a starting point for creating your own ARIS Process Mining workflows. For details on creating a governance process see the ARIS online help.
  To run an APG workflow from ARIS Process Mining, the workflow must have the following inputs:
  {
  user: string,
  payload: string,
  Submit: boolean
  }
5. If you select web.Methods.io as a target system, configure the connection to the web.Methods.io workflow system. Please ask your workflow system administrator for the required data.
  Specify the workflow webhook URL. The URL is used to trigger the workflow defined in the workflow system.
  If the workflow system does not require login credentials, enable None. The option is enabled by default.
  If credentials are required to log in, enable the Tenant credentials option and specify a user name and password.
  If a secret key is required, enable the Secret key option and enter a secret key.
  Example
Click Next. The Notifications dialog opens. Configure an e-mail notification in addition to the specified target system for the insight trigger you selected.
Enable the Enable e-mail action trigger option and enter the recipients of the e-mails in the Send to field. You can specify multiple users and user groups. Click Customize e-mail notification to configure the notification layout and content in the Mail builder. You can configure the e-mail notifications later.
Click Create.