Tasks
Tasks allow for introducing a human element into workflows.
Overview
A Task is a user interface for humans to review (and modify) data in Accode.
Including a human element in your workflow may be useful for adding an element of manual quality control, to validate some critical type of data, and to improve the long-term robustness of your workflow by sampling a part of your data for manual review.
Basics
The Task action generates a task for each entity that enters it. The entity is blocked from exiting the action until the task has been completed. The action is found in the core actions package, and is included by default in all workspaces.
Tasks can be either approved or declined by the user. Once a task has been completed, the entity will continue to the next action.
Adding tasks to a workflow
You add a task to a workflow like any other action. Locate the intended place in the workflow, and add the Task action.
Viewing open tasks
In order to view open tasks, go to the task action and press “View tasks”. If you would like to just see the invoices without changing them, there is a number located inside the action, showing how many tasks there are open. However, if you would like to view the tasks and accept them, you have to press “View tasks”.
Completing tasks
The user can use the task to either accept or decline entities in the task, depending on the requirements of the task and entities passed. The user can also change the entities in the task. Tasks also allow you to add a specific time filter that automatically accepts or declines an invoice after a specific amount of time has passed, to always have a task up to date.
If you were to decline an entity in a task, it would result in the entity not continuing down the workflow.
Examples of tasks
The task user interface can be tailored to fit any kind of data. Depending on your needs, you can choose different views on the task. Many data models have a default task defined for them, which will be automatically selected to display those entities. For instance, in the image above, the default task for the Purchase invoice model is called, “Default purchase invoice”. Some tasks are generic, meaning that they can be used with any type of data model.
There are a few built-in tasks, which all work with any type of data:
Generic table: shows each entity as a header section and a table section for nested data.
Raw data: shows the data in JSON format.
