What to do: |
|
![]() |
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! |
![]() |
As a prerequisite for the following example you must have created a process with at least two activities. |
![]() |
How to Add and Connect Components |
In the example the process is 863 -Order. | |
Activities can be automated to avoid the delay of processes, e.g. due to the absence of resources. To automate activities, the following is needed:
|
|
![]() |
Click The mask is opened. |
![]() |
Activities can also be automated in process templates. In this case click |
![]() |
Search for the process 863-Order. |
|
Click ![]() The Workflow Editor is opened, displaying the Order process in the window. ![]() |
In the process depicted above, the activity Delivery is to be automated. | |
![]() |
Double-click Delivery. The window is opened. |
![]() |
In the | field enter the name of the userexit (LogiView procedure).
![]() |
To confirm click . |
In this example the Userexit (LogiView procedure) will check if the resource assigned to the activity (user DEMOEP_M) is available in order to execute the action. If DEMOEP_M is not available, the Userexit will check the table and determine representatives of user DEMOEP_M who will then perform the action. | |
Further information about resources and userexits are displayed in the
|
|
![]() |
The userexit (LogiView procedure) entered in the | mask will be displayed in the column of the tab.
![]() |
Please note that for a background activity the resource type "Automatic" must be assigned. There won't be an entry in the | column since no resource (user) can be assigned to the resource type "automatic"!
![]() |
The userexit in the field is executed synchronously with the EDM process, and is completed before the next activitiy is started! The userexit in the field is executed asynchronously with a separate EDM process, and allows the parallel execution of other functions! |
![]() |
When assigning an automatic resource to an activity, it is also required to assign a LogiView procedure with a userexit in the background of this activity! |
![]() |
It is not possible to edit the fields | and at the same time!