Involve business users with Tasks
Bridge the gap between process analytics and operational action by assigning tasks to the right users at the right time. Tasks bridge the gap between high-level process analytics and day-to-day operations. Instead of just identifying bottlenecks, you can assign specific, actionable items to the right users at the right time.
This procedure covers the initial setup within Studio, from creating the Skill to defining the automated trigger and the task details.
Create and Trigger the Skill: In your package, create a new Skill and add a sensor. Use a Smart Sensor to automatically detect data incidents (Signals) based on your Knowledge Model filters, or use a Manual Sensor if you want users to trigger tasks ad-hoc.
Define the Task & Actions: Add a Create Task step. Configure the Task name, Assignee, and Attributes that will appear in the user's inbox. Then, create Task Actions to allow business users to push updates back to source systems or internal apps directly from the task.
This procedure covers moving the task into production and making it visible to the end users.
Validate and Publish: Run a Test to check the execution logs for errors. Once verified, Publish the Skill; the Smart Sensor will now continuously monitor for new incidents and generate tasks automatically.
Enable User Visualization: To make tasks accessible, create an Action Table in a View. Link this table to a Profile View containing a Task List component, allowing users to see and manage their assigned work in context with the process data.
Note
If you are using the Smart Sensor, tasks will automatically move to "Resolved" once the underlying data incident is fixed in your source system. If using Manual Sensors, users must manually update the status.
This process explains how to enable users to trigger tasks ad-hoc and how these differ from automated Smart Sensor tasks.
Configure the Manual Trigger: Follow the standard Skill setup, but select a Manual Sensor as the trigger. In the Create Task action, leave the Name, Description, and Assignee fields open; this allows the "Creator" (User A) to define these details at runtime for the "Assignee" (User B).
Deploy for User Input: Publish the Skill and add it to an Action Table or as a Default Action. Users can then manually trigger the task by selecting rows in a table. Unlike Smart Sensor tasks, these must be manually marked as resolved by a user once the work is complete.
Key differences:
Feature | Smart sensor tasks | Manual tasks |
|---|---|---|
Trigger | Automatic (based on data incidents). | Manual (User-initiated). |
Resolution | Auto-resolved when data is fixed. | Manually resolved by a user. |
Identification | Standard task icon. | Highlighted with a "User Created" icon. |
Tip
You can combine these by making the creation of a Manual Task a "Task Action" within a Smart Sensor Task. This allows an automated alert to act as the parent for several sub-tasks assigned to different team members.