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.
...
The functionality and the distribution of the objects is described in chapter Object List https://pronovia.atlassian.net/wiki/pages/resumedraft.action?draftId=584188263 of the Process.
Person responsible
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 Sub object/ Members.
Dates
The maintenance and function of appointments is described in the chapter Sub object/ Dates .
Notifications
The maintenance and functionality of the notifications is described in the chapter Sub object/ Notifications .
Activities
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.
...
The containers are described in the chapter Containers and Items . The most important containers and items are described below:
Container/Item | Description |
|---|---|
HEADER | Header data |
ITERATION | Number of iterations |
RUNTIME_STATUS | Current status at runtime |
RESPONSIBLES | Responsible Person |
ALL | 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. Activities that have already been completed no longer have a current agent. The data is suitable, for example, for informing all agents who have not yet completed their activities and who are automatically skipped when a part process is terminated prematurely. |
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. The data is used, for example, in a decision-making process to inform the other group of the outcome. If the part process is rejected, all agents who have regularly completed the activity can be informed again. |
ALL_REJECT_AGENTS | Like ALL_COMPLETE_AGENTS, but agents who rejected an activity. |