You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
Process Tasks
A process consists of a number of tasks. Each task is a placeholder in the process engine that should be executed by the user. The actual execution of task is done in an implementation module, where it is possible to use pages and flows.
For more detailed information on how to use tasks see our Design guide for case management and the use of tasks.
| Property | Description |
|---|---|
| Display name | This is the name of the task how it is displayed to the user. |
| Due date | This is the date by which the task should be done. It is set at the moment when the task get the 'open' status. It can be used to display in the worklist or as basis of a priority algorithm. |
Due date reevaluation event | There are two possible values: “On creation only” and “On domain change”. The “On creation only” is the default value which means the due date will not be updated. If “On domain change” is set, it will update the due date once the condition expression evaluates to a different value. |
| Is automated | A boolean to indicate if this task can be run automatically. A task can be run automatically if there are no pages, and can be run without user interaction. |
| Apply case locking | If you start a task for a certain case, then you might want that your case gets locked. This means that another user cannot start a different task for the same case while you are busy with your task. When this checkbox is set to true, then your case will lock as soon as a task is started. |
| Authorization algorithm | An Authorization algorithm can be selected to connect the right algorithm to the task. The Algorithm will result in one or more roles which may perform the task. |
| Routing algorithm | A routing algorithm can be selected to connect the right algorithm to the task. The Algorithm will result in one or more roles, teams and/or users which are assigned for a task. |
| Priority algorithm | A priority algorithm can be selected to connect the right algorithm to the task. The Algorithm will result in an integer value which can be used to sort the worklist. |
| Roles | Some tasks cannot be performed by certain users. To enable this we need to set role privileges on a task. These are roles which a user needs before he/she can start a task. You only need one role of the defined set in order to be able to start the task. Our advice is to use the authorization algorithm instead of the roles. Using the algorithm makes managing roles and rights easier. Adding a new role means that you only have to update the algorithm instead of applying a new role for each task. |
Process events
Process events are similar to flow events on a page. For every process event, you will get an exit node for this tasks in you process flow.
| Property | Description |
|---|---|
| Process event | Selection of the process event for which you will get an exit node in the process. |
| Type | Can be either 'Plain' or 'Cancel' Both types 'Plain' and 'Cancel' trigger the data mapping from the interaction module to the process module. |
Custom fields
These custom fields are task specific information, and not case specific information. This information can be used in work lists.
Custom fields are stored in the database as plain strings for performance reasons. You should format them at the moment of storing.
Timer exit
A timer exit can be modeled on a process task in the process editor. When the expression modeled at the exit is TRUE the process will follow the path connected to this exit. The timer condition will be used as the expire date in the process engine.
Overview
Content Tools
1 Comment
Jurgen Jansen
Dear colleague,
Are there any benefits to using an Authorization Algorithm instead of Roles on a process task, if the 2-man-rule is not used, the External Source is not used, and the Authorization Algorithm is specific to just one process task (so no need to re-use).
In am really curious, since in my current project the vast majority of the Authorization Algoritms created only contain some roles and are specific for one task. Therefore I do not see any benefit in using the Authorization Algoritm. Yet maybe there are benefits not stated in the current documentation.
Kr,
Jurgen