User task allows you to assign a workflow task to a certain user.
For example, you can add filters and assign a task to the IT department. When the workflow reaches this user task, the task will appear in their inbox.
User task properties consist of the following sections:
2.1 General Section
Caption defines a title of the user task:
2.2 User Assignment Section
Assign user task using allows you to manage what users the task will be assigned to. You can filter users or implement a more complicated logic and add several checks using a microflow.
Possible options of this property are described in the table below:
|Filter||Allows you to filter users who should be assigned to the user task. For example, you can assign a certain task only to users with the Administrator user role. For more information on how to use filters, see Data Filters.|
|Microflow||Allows you to assign the user task to certain users. Using microflow you can check, for example, what users have the right to approve user tasks and are currently not on vacation and assign the task only to users who passed the check. For more information on microflows, see Microflows.|
2.3 Task Page Section
Page is an overview page where the allowed roles can track the progress of the user tasks and view its details, such as open tasks, comments to them or attachments:
2.4 Display Information Section
The Display Information section defines the user task name and its description that are displayed in the running (published) app.
The Display Information section properties are described in the table below:
|Task Name||Task Name is displayed in the running app. The Task Name can contain attributes of the Workflow entity, the value of which will be displayed to the end-users. For example, you can select a FullName attribute from the Employee Onboarding data to display the name of the new employee.|
|Task Description||Task Description is a description of the workflow displayed in the running app. The Task Description can contain attributes of the Workflow entity, the value of which will be displayed to the end-users. For example, you can add a PhoneModel attribute from the Employee Onboarding data to display what phone needs to be shipped for this employee.|
2.4 Due Date Section
The Due Date section allows you to set a deadline for the user task and keep track of it. However, this is not an automatic reminder but rather a deadline you reference when keeping track of the workflow.
The Due Date section properties are described in the table below:
|None||No due date is set.|
|Duration||You can set the deadline for the user task with the Due In option, which indicates the number of hours, days, or weeks the task is due in. Possible values of the property are the following ones:
|Expression||You can set a due date for the user task writing an expression. For example, to set a due date to tomorrow, you can use
2.6 Outcomes Section
The Outcomes property allows you to create new outcomes for the user task. These outcomes can be referred to by other elements, such as buttons. For example, you have a process when you need to approve or reject a request. One button on a task page can refer to the Approve outcome of the user task, while the other one can use the Reject outcome:
2.7 Events Section
On Create event allows you to select a microflow that is executed immediately after users have been determined for a newly created task instance. You can use this setting for a microflow that will send an email notification about the user task to the assigned users.
Possible options for this setting are the following:
- Microflow – a microflow that is executed when users have been determined for a newly created task
- Nothing – no event is executed
2.8 Permissions Section
Allowed roles defines the user role that can execute the user task.