URL to the desired REST Service

@since 5.5.0.3 this input support supports FlexDeploy property replacement. i.e. you can use ${{PROP1}} in the input value.

Query String to be used. Use Groovy if desired to use FlexDeploy variables in the query string.

'a=b&c=d&e='+FD_TEMP_DIR+'&f=g'

or, if not using Groovy, simply

a=b&c=d

Spaces will not be trimmed from the string.

@since 5.3.0.1 The query string input also allows FlexDeploy property replacement to be used

Preemptive Authentication

Use preemptive Basic authentication (provide authentication before being asked)

if false, non-preemptive Universal authentication is used.

The file path containing the request body.

*Either Body or Body Path must be supplied.

@since 5.5.0.3 this input support supports FlexDeploy property replacement. i.e. you can use ${{PROP1}} in the input value.

The String to use as the request body.

*Either Body or Body Path must be supplied.

@since 5.5.0.3 this input support supports FlexDeploy property replacement. i.e. you can use ${{PROP1}} in the input value.

Ignore SSL Errors

What action should be taken upon completion of this request? Possible options are:

• ReturnAsOutput - Save the response body and response code to the outputs described below
• SaveToTemp - Save the response body to a response file in the temp directory. 
  • File name will be 'response.json', 'response.xml', or 'response.txt' depending on the response type.
• SaveToArtifacts - Save the response body to a response file in the artifacts directory. Be sure to check 'produces artifacts' if intending to save the file to artifacts.
  • File name will be 'response.json', 'response.xml', or 'response.txt' depending on the response type.

@since 5.3.0.1

Headers to send with the request. Formatted as key=value. One key/value pair per line.  For example:

• my-custom-header=abc123
• x-client-secret=${{FD_CLIENT_SECRET}}

The headers input also allows FlexDeploy property replacement to be used as seen in the x-client-secret header above

@since 5.3.0.1

Groovy validation script to be run against the response body. This input expects a groovy script as plain text, meaning you should not enable the groovy script flag on the plugin input itself. 

Available variables:

• PAYLOAD - accessed as a Json object or a simple string if the return type is not Json
• RESPONSE_CODE - integer response code

Example script:

PAYLOAD.myField && PAYLOAD.myField.equals('myValue')

@since 5.3.0.1

What action should be taken if the Groovy Validation Script fails?  Valid options are:

• JustLog - Simply log the failed result and continue as if successful.
• GenerateTestResults - Generate a simple test results file. The results will not show up in the test results tab unless this is used in a test workflow
• FailExecution - Throw an error and fail this plugin execution

@since 5.3.0.1

Time to wait to allow a connection to be established. Setting to 0 will wait forever.

@since 5.3.0.1

Time to wait for a response after establishing a connection. Setting to 0 will wait forever.

@since 5.3.0.1