HTTP Form Post

Sends a multipart/form-data POST request to a Web service and returns the result in tokens. To configure this activity, you will need access to a Web service, its API, and a basic understanding of HTTP transactions.

See the tokens this activity produces.

Example: You could use this activity to automatically fill out an online venue request application form.

To add this activity to a workflow definition

• Drag it from the Toolbox Pane and drop it in the Designer Pane.

To configure this activity

• Select the activity in the Designer Pane to configure the following property boxes in the Properties Pane.
• Activity Name
• Activity Description
• Web Service
• Request
• Form Data
• Preferred Response Format
• Advanced Properties

  Click the Advanced button at the top of the Properties Pane to view and configure these properties.

• Request Cookies
• Request Headers
• Response Header Tokens
• Advanced Options

Tokens for HTTP Form Post

The HTTP Form Post activity produces the following tokens.

Name	Description	Sample Syntax*
Content File	The file returned by the Web service in response to the HTTP web request. You can use this token in another HTTP Form Post activity to post a file to a form.	%(HTTPFormPost_Content File)
Content	The data returned by the form you are posting to.	%(HTTPFormPost_Content)
Content Length	The length of the response in characters or bytes.	%(HTTPFormPost_Content Length)
Response Status	The status code returned with the request. If the request succeeded, the status code will be in the 200s. If it failed, the code will be in the 400s or 500s. These warnings will appear in the Message tab of the workflow's instance details.	%(HTTPFormPost_Status)
Response Status Description	The description that accompanies the status code.	%(HTTPFormPost_Status Description)
Request Succeeded	Whether the HTTP form post succeeded or not. This token will have one of two values: "True" or "False."	%(HTTPFormPost_Succeeded)

*"HTTPFormPost" will change to match the name specified in the Activity Name property box.

Note: All non-alphanumeric characters, except underscores, are removed from the name. For example, if you rename the activity "Fill out ^Form^," the syntax for the Content token will be: %(FilloutForm_Content).