Skip to main content

Advanced REST Client

Description

Advanced REST Client is a step in the Utility Plugin for Process Studio Workflows. The REST Client workflow step enables you to consume RESTful services by making REST calls. It is an extension of the step ‘REST Client’ with more features as follows:

- Authenticated Proxy Support

- Option to ignore SSL certificate validation

- Request Timeout

- Form-data request body along with file upload by providing file path

- Ability to read HTTP Response headers

- Ability to test REST API

Limitations: Process Studio variables, parameters, and field names must never be same as the Parameter Key, irrespective of case (upper case or lower case).

Configurations

No.Field NameDescription
1Step nameSpecify the name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2HTTP MethodSpecify the HTTP method with which the step will interact with a resource. Available HTTP methods are: GET, PUT, DELETE, POST, HEAD, OPTIONS, or PATCH.
3URLSpecify the path to a REST client resource (HTTP URL).
Settings Tab:Enter basic connection information for accessing a resource.
General:
1Request timeout in secondsThe time to establish the connection with the remote host.
SSL Configuration:Provide authentication details for accessing a resource that requires SSL certificate authentication.
1Ignore SSL certificate verificationEnable this checkbox to ignore SSL certificate verification while making HTTPS connection.

(This strategy ignores certificate checking, making it insecure and only to be used where it makes sense!!)

2Trust store fileSpecify trust store file path in case of HTTPS connection.
3BrowseClick Browse button to select trust store file from local machine.
4Trust store passwordSpecify trust store password in case of HTTPS connection
Proxy Configuration:
1Use System ProxyEnable checkbox to allow REST client to use the Process Studio's default proxy configurations. In case of AE agent, it will use agent's proxy configurations.
2Proxy TypeSelect Proxy server type (HTTP/HTTPS)
3Proxy HostSpecify the name/IP of a proxy host, if proxy authentication is required
4Proxy PortSpecify the port number of a proxy host, if proxy authentication is required
5Proxy UsernameIn case of authenticated proxy server, provide username
6Proxy PasswordIn case of authenticated proxy server, provide password
7Proxy Exceptions (Non- Proxy Hosts)Specify the Proxy Exceptions, that is, non-proxy hosts.

The Proxy Exceptions (Non-Proxy Hosts) can hold semicolon- separated hostnames, IP addresses, and domain names that must not be accessed through the proxy server. When a client requests access to a resource, the proxy server checks the hostname or IP address against the semicolon separated non- proxy hosts. If there is a match, the proxy server forwards the request directly to the target server without going through the proxy.

For example, if the Proxy Exceptions (Non-Proxy Hosts) set to "localhost;127.0.0.1;*.mydomain.com", then requests to the localhost, 127.0.0.1 and any server under the mydomain.com domain will be accessed directly without going through the proxy server.

It will be considered when the “Use System Proxy” checkbox is unchecked and proxy details (at least Proxy Host and Proxy Port) are provided into the plugin.

Parameters Tab:This tab contains table with three columns to provide request (URL) parameters
1Parameter KeySpecify the Request parameter keys to set value.
2Parameter ValueSpecify the Request parameter keys values.
3DescriptionSpecify a description for the parameter.
Authorization Tab:Enter authorization details for a resource in the Authorization tab.
HTTP Authorization:
1TypeSelect Request Authentication (No Authentication, Basic Authentication, Bearer Token, and OAuth 2.0).
2UsernameIn case of Basic Authentication provide username
3PasswordIn case of Basic Authentication provide password
Headers(0) Tab:This tab contains table with four columns to provide request headers
1Header KeySpecify request header key
2Header ValueSpecify request header value
3Header Value FieldDefine the content of any HTTP headers using an existing field. Populate the list of fields by clicking the Get fields button.
4DescriptionSpecify a description for header
Request Body Tab:Request Body tab has a group of radio buttons as follows:
Request Body:
1noneIn case where request does not have a request body
2rawSpecify raw Request Body as Text, HTML, XML, JSON or XML. You could insert fields in the raw body from the navigator by double clicking the field. Else, use template support in request body to substitute fields and environment variables/parameters in appropriate placeholders (?{fieldname}, ${environment variable}).
3form-dataEnter Request body in tabular format in a form. Use form-data to send non-ASCII text or large binary data.
4x-www-form-urlencodedEnter Request body in tabular format in a form. Use x-www- form-urlencoded to send simple text/ASCII data.
5read from fileIn case where request body to be read from a file.
6read from fieldIn case where request body text to be read from a field.
7binaryIn case where request body is to be read from a file.
8GraphQL (Beta)Specify GraphQL to execute the GraphQL query schema. Query: Specify a GraphQL query to read or fetch values or a mutation to write or post values.

E.g. Query:

{

students

{

id

fullName

}

}

GraphQL Variables: GraphQL variables help to factor dynamic values out of the query and pass them as a separate dictionary.

You could insert fields in the Query and GraphQL Variables from the navigator by double-clicking the field. Else, use template support in the request body to substitute fields and environment variables/parameters in appropriate placeholders (?{fieldname}, ${environment variable}).

Note: Please make sure, when substituting (field or environment variable) a string value we have to explicitly enclose that value in double quotes ("").

Limitation: Subscription query are not supported by ARC GraphQL.

Form-data:This tab contains table with five columns:
1Key TypeSelect form-data parameter key type (Text/File) from the dropdown list.
2KeySpecify form-data parameter key.
3ValueSpecify form-data parameter value.
4Value FieldSelect a field containing form-data parameter.
5DescriptionSpecify a description for form-data parameter String.
x-www-form-urlencoded:This tab contains table with three columns:
1KeySpecify a parameter key.
2ValueSpecify a parameter value.
3DescriptionSpecify a description for parameter.
Read from file:This tab contains table with five columns:
1Content type for request bodySelect content-type for request body dropdown.
2File PathSpecify request body file path.
3View Request Body ContentsClick this button to view request body file contents
Read from field:This tab contains table with five columns:
1Content type for request bodySelect content-type for request body from dropdown
2Field nameSpecify request body raw text to be read from a field.
HTTP Response Tab:This tab has Output fields.
1Response StatusSpecify the output field to hold the HTTP Response status (e.g 200 OK). The default field name is ArcRespStatus.
2Response Time (milliseconds)Specify the output field to hold the HTTP Response time in milliseconds. The default field name is ArcRespTime.
3Response Headers (JSON)Specify the output field to hold the HTTP Response headers in the JSON format. The default field name is ArcResponseHeaders.
4Response Cookies (JSON)Specify field name to set HTTP Response Cookies in JSON format. The default field name is ArcRespCookies.
5Response BodySpecify the output field to hold the HTTP Response body text if any. The default field name is ArcRespBody.
6Output FileSpecify the output field to hold the file path for file received in the HTTP Response. The default field name is ArcRespOutputFile.
7Add File to ResultCheck this option to add HTTP Response output file to workflow result.