Configuring Task Augmentation
Task Augmentation connects Celonis data incidents directly to business users, providing them with a clear call to action and a proposed next best action. By linking Task data directly to your data model via PQL, you can track resolution efficiency and operational impact in real-time.
Before configuring Task Augmentation, ensure your Data Model meets the following criteria:
Row limit: The source table must have fewer than 150 million rows.
Scale: Support for up to 100 different Record types per Data Model.
Capacity: Maximum of 200,000 tasks per Record type.
When you use the Create Task action in Studio, you define how the user interacts with the incident.
Tasks have the following components:
Task Name: The title displayed in the user’s Task List.
Assignee: The specific user or group responsible for the task.
Description: Additional context (visible via tooltip) to help the user understand the "Why."
Task Attributes: Specific data points (e.g., Invoice Amount, Vendor Name) that characterize the record.
Actions: Buttons (e.g., "Remove Topping," "Approve Invoice") that trigger Skills directly from the Task List.
Task data is autogenerated in your Knowledge Model (KM) as <record_name>_CEL_TASK.
To use this data:
Enable Visibility: In the KM View, go to View - Autogenerated Data Model definitions.
Add KPI Columns: You can create PQL-based KPIs (like "Open Task Count") and add them as columns in your Action Views.
Filter by Attribute: Use the autogenerated
ASSIGNEE_NAMEorSTATUSto create dropdown filters for managers.
Tasks move through a specific status workflow to ensure nothing falls through the cracks:
Status | Behavior |
|---|---|
Open | Default state for new tasks; highlighted in Action Tables. |
In Progress | Set manually or via Skill action when a user begins work. |
Snoozed | Temporarily hidden; will automatically re-open on a specified date. |
Resolved | Automatically triggered when the source data no longer meets the sensor criteria (e.g., the error was fixed in the ERP). |
Archiving tasks
To keep the Inbox clean, Resolved tasks are archived nightly. These are moved to a _CEL_TASK_ARCHIVED table in your Data Pool, where they can be used for long-term performance analytics.