You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.

Task

A task is a units of work which will be performed by one person in one place in one run. Within the process editor only the conditions on when a task may be executed are modeled, the execution of the task is not. The screens and services to execute the task itselves are modeled within a flow in an implementation module.

For more detailed information see Process tasks

At runtime, is possible to trace task actions: Process Traceability

Timer exit

A timer exit can be modeled on a process task in the process editor. 

Selecting the edge (connection between nodes) will open the panel in which the condition can be modeled. When the condition 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.

Process

It is possible to include a sub-process in a process. This sub-process acts as a collection of process components, so a sub-process will be used to organise process drawing more clearly. A sub-process can be used for the reuse of a collection of components as well.

When using more than one process type, the process type of a sub-process must be 'allowed'. If not, a validation error that the process is a 'restricted process' will be generated by the runtime. Which (sub)process types can be added to a process of a given type, can be edited in the process type's properties. Under parameters choose 'selected' and add the allowed process types for (sub) processes.

  • No labels