Worth knowing about the process flow

Since ProProcess processes are mapped by means of SAP workflow, there is a corresponding SAP workflow for each process, which runs in parallel and informs/synchronizes ProProcess at dedicated points in time. ProProcess then runs the corresponding objects (gates, gateways, etc.) in parallel.

Since a dedicated background user is responsible for processing the steps in the workflow environment, this workflow user is often displayed in the status information, since this user also drove the process. This also (and especially) applies to started, completed, or canceled for processes, since this status is updated by the SAP workflow.

The exception are processes with synchronous status update, which set (or could set) an object status at the start or at the end of the process (possibly also sub-process or activity). Since this object status update is to take place synchronously, it must already be executed, although the corresponding workflow has not yet reached the corresponding point. This ensures that in the event of an error during the status change, the process is not continued unexpectedly and thus ends in an inconsistent state.

For processes with status update in the background, the status change is generated as a separate background task in the workflow. If an error occurs during the status change, the workflow is set to the status "Incorrect" and must be manually corrected and continued by a responsible person.