Call Tab Page

Use

With the specifications you make on this tab page, you define the following:

Which transfer format is used
What is executed
Which interface task is used
How an XML document is to be sent
How XML response documents are to be checked

Activities

General Specifications

Step name:

Give the step a name. This name is used to label the step within your workflow.

Address (URL) using:

You have the following possibilities of entering the URL to which the XML document is to be sent:

Enter an expression that contains a URL.

Note

The address must not contain any blanks since blanks are automatically removed from the address when the step is executed.
If the XML document is sent to an SAP System and a workflow is to be started there, you can enter a static URL. You also have to use the Generate SAP URL wizard. Choose . If the target system has the SAP Release 4.6C or 4.6D, the SAP Internet Transaction Server (SAP ITS) is called and the URL has the following structure:
```
http://<webserver>/cgi-bin/wgate/wf_handler/!?
~protocol=<protocol>&~localkey=<localkey>
                  
```
If the target system has a SAP Release from 6.10, the SAP Web Application Server (SAP Web AS) is called and the URL has the following structure:
```
http://<webserver>/SAP/BC/WORKFLOW_XML/?
~protocol=<protocol>&~localkey=<localkey>
                  
```
In <protocol> you specify the transfer format used in the form of a two-digit number. In <localkey> you specify the ID of the workflow to be started.

Note

When the other SAP System is called, a logon is performed using a predefined user name. This user must be a possible agent of the workflow to be started.

Example

You want to start workflow WS00000000 and use transfer format 01. The SAP System on which the workflow is to be started has Release 4.6D and the address of the server is WEBSERVER01. The entry required in Address (URL) is:

http://webserver01/scripts/wgate/wf_handler/!? ~protocol=01&~localkey=WS00000000
Enter a WebFlow rule for determining a URL.
If the workflow container contains workflow proxies, these can be used as an expression. Each workflow proxy receives a row in the selection field.

Entries on the subsequent tab pages

The number of subsequent tab pages depends on the function selected.

If you select a specific transfer format, the tab page direct form entry is available. If you choose a transfer format group, the tab page format entry using group exists instead.

Tab Page Direct Form Entry.

You make entries for sending the XML document on the tab page outbound XML document.

The tab page inbound XML document is only available if the function can expect an XML response document.

The tab page extended communication is only available if a workflow is started by this Web activity.