Workflow

On Complete or in Background

The system variables EP_WFL_PRC_ID, EP_WFL_ACT_ID are only filled for batch processes/activities to enable the separate started server to access the right objects. All other processes/activities are running synchronously with the server, i.e. a widget is accessible with fields, which also include the C_ID fields of the referenced processes/activities. Thus, the system variables EP_WFL_PRC_ID, EP_WFL_ACT_ID are empty!

 

Userexits assigned to activities can be executed synchronous when completing an activity or asynchronous in the background. The userexits are assigned in the Activity properties in the field On Complete and In Background. This follows the process below:

 

Execute userexits at completion

 

A userexit is entered in the field On Complete. The user confirms the execution of an activity in the Activity mask with the button Execute and clicks OK. The userexit is executed synchronous. At completion, the Workflow Executor checks if a userexit is entered in the field In Background in the activity properties.

 

Execute userexits in the background

Only after the userexit in the field On Complete was executed, the Workflow Executor checks the fields In Background, if a userexits is to be executed asynchronous in the background. The userexit is then executed.