Part processes can be used as grouping elements for activities. This allows parts of processes to be logically structured and at the same time certain settings to be maintained at an intermediate level to avoid redundancies in the activities.
A special feature of part processes is that the activities contained in them can be processed either serially or in parallel and an early termination of the part process can be set up.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
The following settings are maintained in the basic data:
...
Parallel subprocesses - synchronizing the relationship between subprocess threshold, status threshold and threshold.
In principle, the target status is determined on the basis of a threshold that is independent of the subprocess control. This makes it possible to define separately the circumstances under which the subprocess should be terminated prematurely and how the target status of the subprocess should be determined. In this case, the threshold for the status refers exclusively to the completed activities. If the status of the sub-process is to be derived from the % threshold of the sub-process itself, this can be achieved using the "Synchronize threshold" option, which always determines the status from the % threshold of the control as well as the mode.
The difference between "Consider all statuses" and "Consider all statuses, optimistic" lies in the determination of the target status in borderline cases. If the option "Consider all statuses" is set, the subprocess is terminated when the number of rejected activities has reached the threshold, with "Consider all statuses, optimistic" the number of rejected activities must exceed the threshold. | |
Use the status settings (Status setting and % threshold) if you want to determine the status of the sub-process independently of the sub-process completion status. | |
Using the status threshold will not cause the subprocess to terminate prematurely. | |
Using a %-threshold smaller than 100% for the subprocess control as well as a status threshold smaller than 100% may lead to undesired behavior, especially when using a control mode. |
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
The functionality and the distribution of the objects is described in chapter Object List of the Process.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Those responsible for part processes have special rights to make changes to running part processes. Further information can be found in the user manual of ProProcess. The persons responsible for the part process are determined (via existing formulas, if applicable) and saved at the start of the part process .
The maintenance of the responsible persons is described in the chapter Members.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
The maintenance and function of appointments is described in the chapter Sub object, section Dates.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
The maintenance and functionality of the notifications is described in the chapter Notifications
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Any number of activities can be created for a process. For serial sub-processes the order of the activities can be changed by Drag'n'Drop.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
The containers are described in the chapter Containers.
The most important containers and items are described below:
Container/Item | Description |
|---|---|
HEADER | Header data |
| Number of iterations |
| Current status at runtime |
RESPONSIBLES | Responsible Person |
| List of all part process owners. Can be used, for example, for Members or Notifications. |
In addition, various containers are available which contain information about the agents. These can be used, for example, for Notifications.
Container/Item | Description |
|---|---|
ALL_AGENTS | List of all agents |
ALL_CURRENT_AGENTS | List of all current agents. The current agents are those who have accepted the activity or work item. This can be done explicitly or by an executed action. |
ALL_FINISHED_AGENTS | List of all agents who have completed an activity. The status of the activity is not relevant. |
ALL_COMPLETE_AGENTS | List of all agents who have completed (and not rejected) an activity. |
ALL_REJECT_AGENTS | Like ALL_COMPLETE_AGENTS, but agents who rejected an activity. |
...