Information on Functionality for ProProcess Version 4.0 onward

The instructions described here apply to processes generated with the Workflow Generator V2, which is used as standard starting with BPF 4.0.

With automatic start and start by process, any modelled status changes are always executed in the background and without user interaction. In the case of an automatically started process, the status change is also executed with a delay to ensure that any subsequent activities (V2 updates, customer-specific adjustments) are executed before the status change is executed.

A process is always ended by the SAP workflow user when the associated SAP workflow is ended. Accordingly, the ‘COMPLETED_BY’ field is always the SAP workflow user.

If the process is set to status processing in the foreground (‘Update status in background’ option is deactivated), only the first modelled status change is executed directly online and with the option of user interaction. However, all subsequent modelled status changes are executed in the background by the current user. This applies both at the start of a process and when activities are ended. It should be noted that a modelled status change action is always executed, even if the object is already in the target status.

If temporary errors (e.g. blocking errors) occur during the processing of a modelled status change, the next attempt is carried out by the user with whom the ProProcess job ‘Actions’ is scheduled (normally the SAP workflow user).

Modelled status changes in the background are always executed by the SAP workflow user.

Both synchronous and asynchronous sub-processes are started by the workflow system via a background activity. This means that no GUI interactions such as pop-ups etc. are possible when starting sub-processes. If errors occur during the start of a sub-process so that the process cannot be started, the starting process is set to error status.

Modelled status changes, which are to be executed when the initiated process is started, are always executed by the workflow user and in the background.

The initiator of the started (sub)process is (currently) always the initiator of the starting process.

Sub-processes are always terminated by the SAP workflow user. This means that all modelled status changes that were modelled in the starting (higher-level) process - after the modelling of the sub-process - are always executed by the SAP workflow user until the process is continued by another user.

If processes that were started as a sub-process are administratively cancelled, the starting sub-process element is terminated and the starting process is continued.