Maintenance of Tab Page Extended Communication
Use
This tab page is only available if you execute the function Start workflow with the Web activity.
You can then define a
workflow proxy and a routing class here.Features
You need a workflow proxy if you want to influence the started process with a Web activity in the subsequent steps of the workflow. You can call various functions depending on the transfer format used. For more information on the functions that can be called, see
Maintenance of the Tab Page Direct Format Entry.In the subsequent Web activity, you have to use the workflow proxy entered here as the address on the tab page Call. This restricts the quantity of selectable functions to those that can communicate with the started process.
You also need the workflow proxy to process XML messages of the called process with a wait step. In the wait step, you have to wait for an event that is defined for the ABAP class of the workflow proxy.
You need a routing class if a message of the called process is to be processed in your workflow. If the transfer format Wf-XML Version 1.1 is used, the called process can send a notification to the calling process. You must enter a routing class here so that this notification can be processed in your workflow. As a result, an event of the workflow proxy is triggered by the SAP System for the inbound XML message. The data part of the message is part of the event. Your workflow must contain a wait step that waits for this event of the workflow proxy. If the event occurs, the data part of the message can be transferred from the event parameters to the workflow container using a binding.
If you use Wf-XML as the transfer format, the process started always generates an XML response document. This XML message states whether the process was completed as intended or was canceled. A corresponding event that contains the data of the XML message as the parameter is also generated for this XML message by the routing class. Your workflow must contain a wait step that waits for this event of the workflow proxy. If the event occurs, the data part of the message can be transferred from the event parameters to the workflow container using a binding.
Activities
Enter a workflow proxy. This is a container element that is derived from the ABAP class
CL_SWF_IFS_WEB_PROCESS_PROXY. The workflow proxy must contain events that can be triggered by the routing class due to inbound XML messages.Enter a routing class. This is an ABAP class that supports the following interfaces depending on the transfer format used.
The relevant event must be triggered by the routing class for an inbound XML message and the data contained must be transferred as the event parameter.
Example
You can find an example for the use of the workflow proxy and the routing class in the verification workflow.