Table of Contents
Workflow object: Task
The task object is used in a workflow to represent a work step or an activity that is saved in the activity list of the process after execution. Such a work step usually consists of filling out a for…
Table of Contents
The task object is used in a workflow to represent a work step or an activity that is saved in the activity list of the process after execution. Such a work step usually consists of filling out a form.
Task form
The form is designed with the form designer, which can be opened directly with the icon above the task or via a button in the task.
A task is later displayed in a task as a work step above the task details. The form is opened by clicking on the link.
Workflow Engine for furthr settings
 |  |
Workflow hint
A processing note can be added for each task, which is displayed in the case under the task to be carried out and can serve as an explanation. This is a freely formatable text field so that images can also be embedded, for example.
Task request
Instead of forwarding the entire task with the Forward object, this option can be used to request the task from another person or office only. In this way, the task remains in the “My tasks” list with the last person responsible, while the recipient receives the task. Tasks requested in this way are marked in the model:
The options for recipient selection described in the article Forwarding apply with an addition:
Option | Description |
Suppress email notification | Requesting a task always automatically triggers a system-generated email that is sent to inform the recipient(s) that the task has been received. If this e-mail is not to be sent, this option can be used. No individual text module can then be used. |
Individual email notification | If an individual task receipt notification is to be sent to the recipient(s), this option can be activated. After activation, a selection window appears in which the text module can be newly created or, if it already exists, selected. |
Suppress email notification on completion | When the task is finally processed and then sent back, an e-mail is automatically generated by the system to inform the person responsible for the overall case that the task has been completed. If this email is not to be sent, this option can be used. |
Execute automatically | The task is automatically requested from the configured recipient. If this option is not activated, the task request must be triggered manually by clicking in the process. |
Workflow is not continued directly after requesting the activity. The creation of the activity is waited for. | If activated, the process remains at this point until the task has been completed by the recipient. If deactivated, the next step is triggered immediately. If you do not want to wait at this point, but at a later point, a decision object can be used to check the progress. |
Save activity immediately | The task and form are created directly and saved empty or with the selected default values. It is therefore available in the activity list and can be edited afterwards. |
We recommend using the default settings.
Enable timer
This option makes it possible to link the task to a due date without modeling it separately in the model. It can be set in the same way as a timer and behaves in a similar way: Overdue tasks are highlighted in the activity list. In the workflow model, requested tasks with an active timer are displayed in this way:
Activity is skipped in the workflow and therefore not executed
A task marked in this way is not taken into account in the workflow process. Such tasks, which are not relevant for process control, can be added to the process model for better visualization, e.g. if the model is used for teaching purposes.
Catalog for activity generation
If catalog fields are used in a task form, it can be set here that the selected catalog is automatically called up via the task link in the task instead of the activity. An activity or task is then created for each selected item in the catalog.
How did we do?
Workflow object: Decision
