Performers
The Performers menu allows you to specify which person is responsible for the selected task or process.
The performers menu only applies to the Task, Sub-Process and Event Sub-Process shapes, but is primarily used with User tasks.
Selecting Attributes/Performers from the context menu will open a window where you will be able to define the performers.
Send Notificaton
The Send Notificaton option allows to configure the automation behavior of this task when it becomes available:
Never
Selecting Never will not send a notification to the performers to notify them that the task is available to be performed.
Always
Selecting Always will send a notification to all performers to notify them that the task is available to be performed.
Only if the performer of the previous activity can’t perform this activity
Selecting Only if the performer of the previous activity can’t perform this activity will send a notification to all performers to notify them that the task is available to be performed only if the user that performed the previous task is not part of the performers of this task.
Email Notification Channel
A notification is sent to all performers through email. Note that the email channel needs to have been configured by an administrator in the administration application if the suite is not hosted by Trisotech.
Email Template
A default template can be used for the email but it can also be customized for this task.
When using a custom template, it allows to enter FEEL expressions using the {;} icon. These FEEL expressions have access to the process context (can use data objects values) but also additional variables:
| Variable Name | Description |
|---|---|
processName |
process name that task belongs to |
nodeName |
task name |
user |
first and last name of the person being notified |
formUrl |
form url to access this task |
Microsoft Teams Notification Channel
A notification is sent through a Microsoft Teams channel. Note that the Microsoft Teams notification channel needs to have been configured by an administrator in the administration application.
| The linked team channel needs to be configured with the same performers as the task. Otherwise, the action will not be visible to all performers and could be seen by performers that should not have access. |
Microsoft Teams channel configuration
A Microsoft Teams channel needs to be configured to receive the tasks notifications. To do that, an Incoming Webhook will need to be created for the target channel.
The https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=urljsonpayload%2Cdotnet:"Microsoft documentation" can guide you through all the details but this is a simplified step by step:
-
Right-click on the Microsoft Teams channel and select Connectors.
-
Find Incoming Webhook (it it is not in the available connectors, your Teams administrator will need to enable it) and click configure.
-
Name your connector with a name of your liking and optionally create an icon.
-
You will get the webhook URL required for the configuration.
| The webhook URL is considered sensitive and should not be shared publicly in clear text. |
With the webhook URL, you can now create your channel by selecting _New channel_ from the Channel drop-down list.
Microsoft Teams Template
A default template (task description) can be used for the notification but it can also be customized for this task.
When using a custom template, you enter a FEEL expression that composes your message. These FEEL expressions have access to the process context (can use data objects values) but also additional variables:
| Variable Name | Description |
|---|---|
processName |
process name that task belongs to |
nodeName |
task name |
formUrl |
form url to access this task |
Include form
Choosing to include the form in the notification includes the capability to complete the user task from Teams without having to launch the browser.
| Please note that forms in Microsoft Teams are limited to simple data types and will be automatically disabled for complex types such as collections, etc. It is advised to always test the form rendering in Teams before releasing to production to avoid forms not be displayed properly. |