Manual task

Manual tasks are used when you need human input in the workflow process (e.g. - you need to manually fill out the information about the customer/vehicle so it can be processed by other nodes). There are the following settings:

Here you can describe the nature of the task, what should be done, etc. (You can enter it for each available language).

Here you can the deadline for the task. It will be displayed on the dashboard. You can also set the deadline permissions for the task by clicking on the 'cog' icon near the deadline settings.

In this menu, you can set which users or groups can see or/and edit the deadline of the task.

Here you can set the priority of the task. The priority of the task decides where it will be placed on the dashboard (e.g. - urgent tasks are displayed at the top of the list.)

You can choose the required fields from the process properties. The person who is working on the task wouldn`t be able to finish it without filling in those fields. You can choose entity-type properties or their child properties as required fields.

The required child properties will be displayed in the tooltip in the task window.

The optional fields function is similar to the required fields, except the task can be completed if these fields are empty.

Optional fields are displayed in their section on the task window

The entity ID of the user(contact) that completed the task is displayed in the task output under $json.executor.entityId. You can use this info to get the contact with the "get process" values node if you place it right after the manual task



The manual task can also be autocompleted. You can read about it here.

Here you can see how the manual tasks are displayed on the process page.

Workflow processes have the ability to "override create/edit permissions" for manual task/activity settings.

Tasks can give a user overwrite permissions for specific objects and properties, letting them access and edit data they normally may not create or modify.