Run Web Request Rule
This activity allows you to run a web request in your workflow definition. When the workflow runs, the activity takes one or more values from earlier in the workflow as inputs to the rule. The activity passes the inputs to the web request which produces a result. The result is stored in one or more default tokens specified in the web request. You can use the resulting tokens elsewhere in your workflow process.
You may want to disable activities if you only want to test specific sections of your workflow. To disable activities:
- Select an activity in the designer pane to highlight it.
- In the Description property box, clear Enable.
Tokens for Run Web Request Rule Activity
This activity produces the following tokens:
| Name | Description | Sample Syntax* |
|---|---|---|
| Result Found | A boolean value indicating whether results were found. | %(WebRequestRule_ResultFound) |
| Result Count | The number of headers in the response. | %(WebRequestRule_ResultCount) |
| Request Succeeded | A boolean indicating the success or failure of executing the request. | %(WebRequestRule_Request_Succeeded) |
| Response Content | Contains the body of the response. | %(WebRequestRule_Response_Content) |
| Response Headers | A multi-value token containing the list of headers. | %(WebRequestRule_Response_Headers) |
| Response Status | The HTTP status code of the response. | %(WebRequestRule_Response_Status) |
| Result File | Reserved for internal use. | %(WebRequestRule_Result_File) |
* The "WebRequestRule" portion of the syntax changes to match the activity's name.
Note: Only the default web request rule tokens are defined here. Output parameters and additional custom tokens defined within the rule will appear as additional available tokens to the workflow, following the syntax "%(WebRequestRule_ParameterOrTokenName)" as defined in the previous note.