Action Center user guide

Actionable notifications

link

• Agents: via escalations
• Maestro: via user tasks
• RPA: via the Create App Task activity

1. Open the Properties panel of the Create App Task activity.
2. Select Show additional options.
3. Expand the Actionable Notification section.
4. Enable the toggle for Actionable Notification.
5. Select your preferred channel:
   • Outlook
   • Slack
   • Microsoft Teams
6. Configure the contents of the notification:
   1. Add or modify Task Fields as required.
   2. Add Actionable Buttons to define outcomes (for example: Approve, Reject, Review).

Notification channels​

Integration Service setup​

1. Set up Integration Service connections for the respective connectors under one of your tenant's folder (for example, under the Shared folder):
   • Microsoft Teams connector
     Important:

     For the Microsoft Teams connector, consider taking these additional steps:

     • To receive notifications, set Include Bot to Yes when creating the connection.
     • Ensure your Teams admin has already added the UiPath Notifications app to your Microsoft Teams workspace.
   • Slack connector
2. Ensure these connections are active and shared across the organization.

Personal notification settings​

Action App Requirements​

• Number
• String
• Date
• Boolean

1. The task assignee receives an actionable message in their selected channel: Outlook, Slack, or Teams.
2. The message includes the form fields and action buttons defined in the Action schema of the Action app.
3. The reviewer can complete the task directly from the message. For additional context, use the link in the message to open the full task in Action Center.
   Note:

   The Slack or Teams user account must use the same email address as their UiPath account to receive the notification.

Known limitations​

• Actionable notifications are available only for App tasks, created using the Create App Task activity.
• The supported field types in actionable notifications are: Number, String, Date, Boolean.
• Attachments are not supported in actionable notifications.
• Each field in an actionable notification has a 14,000 character limit.
• You can include a maximum of 10 task fields in the Action schema of the Action app used for sending the actionable notification. If the Action App contains more than 10 fields, the notification only displays a link to the Action Center task.

Example use case​

1. An RPA workflow creates an Action App task for an approval request.
2. The Action App Action schema contains two fields:
   • Boolean for the Approve or Reject outcomes.
   • String for a Comment option.
3. The reviewer receives an actionable email containing the two fields and outcome buttons: Approve or Reject, and Comment.
4. The reviewer completes the task directly in Outlook.
5. The automation proceeds automatically based on the reviewer’s input.

Troubleshooting​

• If you do not receive a notification:
  1. Verify that your channels are enabled in Manage Notifications.
  2. Confirm that Action Assigned is enabled under My Notifications.
  3. Check that Slack/Teams Integration Service connections are active and shared.
  4. Ensure the same email is used in UiPath, Slack, and Teams.
• If fields do not display in the actionable notification sent to the reviewer:
  1. Ensure the Action App contains only primitive fields.
  2. Limit the number of fields to 10 or fewer.
  3. Recheck bindings after modifying the Action App schema.
• If the reviewer cannot edit the fields in the actionable notification: Confirm that the field type is set to Input/Output or Output in the Action schema, as only these field types are editable, and Input is read-only.