Tasks - Smart Sensor
Tasks can serve multiple purposes such as:
User guidance recommending next best action
Invoice assignment
(Issue) specific actioning directly from Celonis
By default, the app comes with three smart sensor skills that create a task for the following scenarios:
Skill Name | Filter(s) | Task | Action |
|---|---|---|---|
Sense Parked Invoices | FILTER_IncomingInvoice_Parked | Resolve issue and post invoice | / |
Sense Vendor Block | FILTER_Vendor_HasBlock | Resolve Vendor Block | / |
Sense Invoice Payment Block | FILTER_AccDocItem_HasBlock | Resolve Invoice Payment Block | / |
The default tasks are very basic and don’t offer any proper actioning. Depending on the desired purpose of the task, it does make sense to look into the customization options below.
For the assignment, the KM field “INVOICE_ASSIGNEE” is used which is by default NULL meaning that the tasks don’t have any assignee.
Customization Options
Add actions for the different types of tasks. It can be very simple such as creating an email action with different action templates for a vendor and an invoice block but it’s also possible to call any other kind of ActionFlow.
Add additional task attributes or descriptions that help the users understand the problem and guide them on how to resolve it.
If the action is very specific to an “issue detail”, it makes sense to create different types of tasks. For example, create one task for invoices with block R and another task for invoices with block A.
Note
With the current platform limitations, one smart sensor can only create 10,000 tasks at once. This means if you have more than 10,000 parked or blocked invoices, not all invoices will have tasks (see Celonis Smart Sensor).