WebFlow Tab Page
Here you add how an XML message has to be authenticated to the called process and which transfer format the XML message that is to start this workflow must have.
You therefore only need to define a workflow proxy and a routing class if this workflow is to be started by a Wf-XML document of the transfer format Wf-XML Version 1.1 or higher.
You need a workflow proxy if you want to send a notification to the calling process with a Web activity. The transfer format must be Wf-XML Version 1.1 or higher.
In the Web activity, you have to use the workflow proxy entered here as the address on the Call tab page. As a result, the number of functions that can be selected on Notification is restricted.
You also need the workflow proxy to process XML messages of the calling 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 calling process is to be processed in your workflow. If the transfer format Wf-XML Version 1.1 is used, the calling process can send a notification to your workflow. You must enter a routing class here so that this notification can be processed by 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.
Using a WebFlow rule, add how a message that is to be sent to the calling process is to be authenticated. For more information, see Definition of a WebFlow Rule.
Select the transfer format that the XML document must have to start this workflow.
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.
· IF_SWF_IFS_ROUTE_WFXML_BETA
· IF_SWF_IFS_ROUTE_WFXML_1_0
· IF_SWF_IFS_ROUTE_WFXML_1_1
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.
You can find an example for the use of the workflow proxy and the routing class in the verification workflow.