Testing Operations
The Test tab of the Edit REST Operation window lets you test Operations and view logging without ever leaving the Connector Wizard.
To test an Operation that you're building, simply specify a Connection, enter values for any Operation Variables you have defined, and then click Test at the bottom.
Note: By default, logging covers only INFO, WARN, and ERROR events. To also include DEBUG events, check Debug Logging.
When you click Test, RunMyJobs makes the service call you have specified, and then the following things happen.
-
The response code displays at the bottom.
-
The following additional tabs display.
-
Response Headers: Use this tab to view the response headers.
-
Response Body: Use this tab to view the response body. If the response is binary, you can download the file (if any) that was returned.
-
Output Parameters: Use this tab to verify that you have correctly extracted the values you need from the response body. In this tab, a null value is represented by <null>.
If an expected value is not found, a "No value found for output parameter" message displays for that value, but the call is allowed to succeed. You can click Details to view the stack trace for the error.
-
Conditions: If you are using Connection Wizard 2.0.0.0 or later, and the Operation includes at least one Condition, this tab displays the overall Evaluation Result for Success Conditions and Failure Conditions. It also displays the Expressions created from the Success and Failure Conditions. A Summary also displays.
Note: If a Failure Condition is Met, the Success Condition displays as Not Evaluated because Failure Conditions take precedence over Success Conditions.
Note: If you have Run Request set to Once and the call fails due to Conditions not being met, a warning displays, indicating that you might want to set Run Request to Until Conditions are met so that the call can be automatically retried. However, whether you want to do this depends on your specific use case.
Note: Even if you have set Run Request to Until Conditions are met, the call will be sent only once each time you click Test.
Note: On the lower right, the response code for the call displays next to the Test button. This can be helpful if you are not using the call's response code to determine success or failure.
-
Log: This tab displays the log from the call. In this view, obfuscated values display as rows of asterisks.
-