This example above shows a basic implementation of the Process Control flow. The main part is the page which contains the AQ_worklist container which is used to create a list with tasks.
- This worklist will contains buttons to start tasks (connectionpoint 1), clicking the button will start the AQ_ExecuteTask service (StartCurrentTask) which will start a flow in a implementation module.
- The page will also contain the buttons to start a case, these will be connected (connectionpoint 2) with the service to start a case by which a case in the Process module will be started.
- The AQ_startCaseProcess (NewCreditCardApplication) service is connected to the AQ_NextTasksForCase (DetermineNextTask) service which analyses the amount of tasks with the status open for a given case. Three possible results are available; One, None, Multiple. The none and the multiple do not offer the possibility to start a task so theses exits (connectionpoint 3) lead back to the worklist. If only one task is available, this task can be started directly by flowing (connectionpoint 4)to the AQ_ExecuteTask (StartCurrentTask) service to start a task.
- The AQ_ExecuteTask service (StartCurrentTask) has four exits (connectionpoint 5) these are; completed, abborted, denied and locked. All these exits should lead back to the worklist.
A process element has the following general fields:
| Name | Description |
|---|---|
| Name | The name of this process element. |
| Functional name | The name which will be shown in the generated documentation. |
| Persistency name | |
| Process type | The type of the process. Default this is 'Process'. |
| Diplay name | The name which will be shown. |
| Description | The description of this process. |