Page History
...
The process module does not function as a stand-alone module to create a complete application. There is a need for at least three other modules to create a complete application: a Process Control Application (PCA), a configuration module and at least one implementation module.
The process module is intended to only do process related activities, and does not support flows, pages and services. these items must be implemented in the implementation module connected to a task.
There are special elements inside a process module , which you cannot find in other modules in Blueriq. These special elements are:
(process, task, process event, message event). They can be found in the menu, on top of your screen.
| Children Display |
|---|
In the dashboard module and other implementation modules it is possible to make use of services specially made for the use with the process engine.
- Service call type: AQ_NextTasksForCase, to make it possible to start a task directly if only one is available.
- Service call type: AQ_ExecuteTask, to start a task.
- Service call type: AQ_GetTaskInfo, to retrieve the default information for the active task
- Service call type: AQ_TaskStatus, to retrieve the status of the active task.
- Service call type: AQ_ThrowMessageEvent, to throw a message event to the process engine.
A special container is available for the creation of a worklist. This container works together with the process engine database to show the tasks which are available for a user.
...
Two types of mappings are used in the context of the process engine, data mappings and task mappings.
- A data mapping is used for transferring data from the implementation modules to the process module and back.
- A task mapping is used to connect a task to a flow in an implementation. It defines which process event in the process engine corresponds to which flow event in the implementation module.
For more information: Configuration module
Overview
Content Tools