Wait Step 
A wait step (
) can wait for:
An event
A condition
A local event
An event that is initially received by the workflow.
At runtime, a wait step is represented by a wait step work item. Wait step work items are not displayed in the Business Workplace. You can, however, locate these using work item selection.
You can use a correlation when waiting for an event and when waiting for an event by using workflow. A correlation enables you to identify objects that belong together, for example an invoice and the corresponding order.
When waiting for an event, the wait step is terminated when the event specifies occurs. This event terminates all wait steps waiting for this event.
You can use this type of wait step for the following purposes:
To suspend the workflow until a defined event has occurred.
Example
A workflow is to wait until documents requested have been provided for an applicant activity. Once the requested documents are received, the transaction used for inbound processing and archiving creates an event which the wait step waits as a receiver.
To wait for an event in a parallel processing branch, which renders processing in the other branches unnecessary.
Note
The event for which the wait step waits should not be created in the other branches of the fork.
Wait for the result or a message from another workflow that was started in another system by the WebFlow function.
Wait for a message of the process that the workflow started using a Wf-XML message.
When waiting for an event, the wait step is terminated when the corresponding condition returns the value true.
When waiting for a local event, the wait step is terminated when this event occurs.
When waiting for an event via the workflow, the event is initially received and temporarily saved by the workflow. Once the wait step has been activated, the event is forwarded to the wait step. When waiting using Workflow, an event can complete a maximum of one wait step. If more than one wait step is active, the event completes the oldest wait step.