EOL: SentryOne Test reached its end of life date on June 15, 2022. See the Solarwinds End of Life Policy for more information.
Cloud actions are responsible for gathering data by connecting to Salesforce or other sites that provide a REST API. Each action can fulfill a unique roll within a test:
- Prepare tests by ensuring the expected results are up to date.
- Clean-up an environment before or after a test execution.
Execute REST Query (grid)
| Icon | Description |
|---|---|
 | The Execute Rest Grid action performs HTTP Requests that parses and stores the response (table) values into a resource grid. |
| Function | Description |
|---|---|
| Rest Connection | The cloud connection that's created in the test group level or test level asset. |
| Endpoint URL | The web address that accepts the web request. Endpoints can use the following actions:
|
Settings Tab
| Function | Description | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Results Format | Selects whether the results return in Json or Xml format. | |||||||||
| Content Type | The information needed to send in the header. For example, application\json, application\javascript, application\xml, etc. | |||||||||
| Root Json Path | Json can return results that have several root objects. Each object contains corresponding data. Identifying the root only returns the results for that root. Example: { Note: Setting the root Json path to data only returns the results id and data1column. Setting the root Json path to data2 only returns data2key and data2column results. | |||||||||
| Timeout (s) | Sets the amount of time in seconds the request should fail if there is no response from the web service. | |||||||||
| Number of retires | Sets the number of attempts to connect before the execution fails and reports an error. | |||||||||
| Resource key | Identifies the tile's name if it needs to be called in the Execution Track, Assert, or Teardown steps of the test. | |||||||||
| Grid Column(s) | The user defined column names, token paths, and data types for each column. Using the Json example above, you can add two columns with the data root Json path. Example
|
Headers Tab
| Function | Description |
|---|---|
| Headers Tab | Headers are information about the type of data returned. Add and remove headers by selecting the corresponding buttons. Once a header is added, select in its corresponding name and value fields to configure them. |
Cursor / Paging Settings
| Function | Description |
|---|---|
| Token Path | Identifies the child token that's used. |
| Is Return Value URL | Select this option if the Token Path is a URL. |
| Query String Parameter | Identifies the (optional) parameters needed to complete the Json request. |
| Cursor Finished Value | The value needed to identify the output data is complete. |
Test Results Tab
Select Test to see the results returned based on the configuration in the previous tabs.
Execute REST Query (scalar)
| Icon | Description |
|---|---|
 | The Execute Rest Query (Scalar) action performs HTTP Requests that parses and stores the response value into a resource grid. |
| Funciton | Description |
|---|---|
| Rest Connection | The cloud connection that's created in the test group level or test level asset. |
| Endpoint URL | The web address that accepts the web request. Endpoints can use the following actions:
|
Settings Tab
| Function | Description | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Results Format | Selects whether results are returned in Json or Xml format. | |||||||||
| Content Type | The information needed to be sent in the header. For example, application\json, application\javascript, application\xml, etc. | |||||||||
| Root Json Path | Json can return results that have numerous root objects with corresponding data for each root. Identifying the root only returns the results for that root. Example: { "data": { "id" : "1", "data1column": "test1" } "data2": { "data2key": "1", "data2column:" "test2" } } Note: Setting the root Json path to data only returns the results id and data1column. | |||||||||
| Timeout (s) | Sets the time (in seconds) the request action should take place before it's a failure. | |||||||||
| Number of retires | Sets the number of attempts to connect before the execution fails and reports an error. | |||||||||
| Resource key | Identifies the tile's name if it needs to be called in the Execution Track, Assert, or Teardown steps of the test. | |||||||||
| Grid Column(s) | The user defined column names, token paths, and data types for each column. Using the Json example above, you can add two columns with the data root Json path. Example:
|
Headers Tab
| Function | Description |
|---|---|
| Headers Tab | Headers are information about the type of data returned. Add and remove headers by selecting the corresponding buttons. Once a header is added, select in its corresponding name and value fields to configure them. |
Test Results Tab
| Function | Description |
|---|---|
| Scalar Value | You can add your own data to populate the column only when testing your configuration. Select Test to see the results returned based on your configuration in the previous tabs. |
Execute Salesforce Query Grid
| Icon | Description |
|---|---|
 | The Execute Salesforce Query Grid action executes a query to gather a data grid from Salesforce. |
Execute Salesforce Query Grid Editor
| Function | Description |
|---|---|
| Batch Size | Sets the amount of records retrieved from Salesforce per trip. The max records in a batch is 2000. |
| Connection asset | The connection asset contains the connection string to the Salesforce source. |
| Low memory mode | Selecting this option stores the results on disk instead of on memory. This option is recommended for large result sets. |
| Include deleted | Checking this option includes deleted records in the result set. |
| Query asset | The asset that contains the query you want to execute. |
| Resource key | The name given to the results that's stored in the Test Resources. |
Execute Salesforce Query Scalar
| Icon | Description |
|---|---|
 | The Execute Salesforce Query Scalar action executes a query that gathers a single value from Salesforce. |
Execute Salesforce Query Grid Editor
| Function | Description |
|---|---|
| Connection asset | The connection asset contains the connection string to the Salesforce source. |
| Expected type | Defines the expected datatype that's returned. |
| Query asset | The asset that contains the query you want to execute. |
| Resource key | The name given to the results that's stored in the Test Resources. |
Load File From Cloud Provider
| Icon | Description |
|---|---|
 | Loads a file from a selected Cloud asset connection. |
| Function | Description |
|---|---|
| Connection Asset | The connection asset you wish to connect to. |
| Source | The source of the connection. |
| Match Pattern | The pattern used to specify multiple files. |
| File Name | The file name you wish to use for the connection. |
Load Grid From Cloud Provider
| Icon | Description |
|---|---|
 | Loads a grid file from a selected Cloud asset connection. |
Settings Tab
| Function | Description |
|---|---|
| Resource Key | The resource key for the cloud connection. |
| Connection Asset | The asset you wish to connect to. |
| Source | The source of the connection. |
| Match Pattern | The pattern used to specify multiple files. |
File Format
| Function | Description |
|---|---|
| Format | The file format for the connection. |
| Delimiter | Select the delimiter for the file. |
| Quote | |
| Lines to Skip | Select lines you wish to skip. |
| Lines to Scan | Select the lines you wish the action to scan. |
| Detect Formats | Select this button to detect the format within the grid file. |
Preview
