You define the event or condition for which the wait step waits on this tab page.
When waiting for an event, you can also use a correlation (see also: Correlation of Objects)
In this step, the workflow waits for an event created by a specific object. As this is not yet known at definition time, you specify a container element of the workflow container, which will contain an object reference at runtime. The workflow system uses this information to automatically define the Instance Linkage at runtime, and then activates it.
If you want to wait for an XML message that is specific to this workflow, you have to use the corresponding workflow proxy as the container element.
Here the workflow system automatically enters the type of the object referred to in the container element.
Choose the event to be waited for in this step. The event must be defined for the object type in the Business Object Repository, or for the ABAP class.
You enter how many times the same event must occur for execution of the workflow to be continued. This field is predefined with 0001 if a condition for the condition of execution is entered on the Conditionstab page.
Process the binding definition from the event container to the workflow container if you want to use information supplied with the event in the workflow. Choose Binding. If the event for which the workflow waits occurs more than once, the binding is also executed more than once (each time the event occurs). A binding definition is not generally required.
Define the condition required using the condition editor
Select the event for which the wait step is to wait via the workflow. You must define the event in the version-dependent basic data of the workflow.
When waiting for an event via the workflow you can also use a correlation (see also: Correlation of Objects)
Select the local event required. You define the local event in the version-dependent basic data of the workflow. You can use an event creator or an event that you define in the version-specific basic data for the workflow to trigger the local event.
The following information is dependent on the type of event:
Enter the ID of the outcome of the wait step, with which processing is to be continued after the event occurs.