Task configuration
Tasks are actionable notifications triggered by specific data incidents. They bridge the gap between process analytics and business action by providing users with the context needed to resolve issues directly within the Celonis Platform.
When configuring a Create Task action in a Skill, you define several attributes that dictate how the task appears to the end-user:
Task Name: The primary title displayed in the Task List.
Assignee: The user or group responsible for the task.
Task Label: A tag used to group tasks by business meaning (e.g., "High Value" or "Overdue").
Description: Contextual information provided via a tooltip or detail view.
Task Attributes: Specific record data (e.g., Invoice ID, Vendor Name) that characterizes the object.
Assigning the right task to the right person is critical for efficiency. You can manage assignments through several methods:
Method | Description |
|---|---|
Static Assignment | All tasks of a specific type are assigned to a predefined user or group. |
Dynamic Assignment | Uses Assignment Rules to route tasks based on object attributes (e.g., Region or Department). |
Fallback Assignee | A safety net user who receives the task if the primary logic fails to find a match. |
Manual Re-assignment | Users can update the assignee directly from the Task List or Action Table. |
Tasks follow a specific lifecycle to help users track progress. A task can hold one of five statuses:
Open: Default state for new tasks.
In Progress: The user has acknowledged the task but not yet finished.
Snoozed: Temporarily hidden until a specific date (usually one week by default).
Closed: Manually moved out of the active queue.
Resolved: Automatically triggered when the underlying data incident is fixed in the source system.
And the Status Change Matrix:
From / To | Open | In Progress | Snoozed | Closed | Resolved |
|---|---|---|---|---|---|
Open | Manual/Skill | Manual/Auto | Manual | Auto Only | |
In Progress | Manual | Manual | Manual | Auto Only | |
Snoozed | Auto-reopen | Manual | Manual | Auto Only |
To make tasks easier to find, you can add specific columns to your Action Tables that filter tasks by their Task Label.
For example, to display a count of tasks labeled "Purchase" for an invoice, use the following ID format in your table configuration:
[RECORD_NAME]_TASK_[LABEL_NAME]_COUNT_GEN
With the YAML being:
data: columns: - id: "INVOICE.INVOICE_BELNR" - id: "INVOICE_TASK_Purchase_COUNT_GEN"