When a web service action doesn't run successfully, you can troubleshoot the web service action.
You have several options to troubleshoot a web service action. You can, for example:
Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Validate connectivity setup |
Application Consultant |
If you open a form or save (changes to) the setup of a key element in Connectivity studio, the setup is validated automatically. If errors are found in the setup, an error icon is shown. You can click the icon to show the related error messages. You can also manually start an automated test to check for errors in the setup. As a result, the found errors are shown. Also, the error icons are shown where applicable.
When errors are found, you can try to fix these errors automatically.
You can check and auto-fix errors for these key elements in Connectivity studio:
In this flow, in the activity steps, as an example, the validation is done for documents.
|
||||||||||||||||||||||
Test outbound web service action |
Application Consultant |
You can test an outbound web service action without sending a request to the external web service. So, you only test the outbound web service action setup and not the full process with connection to the external web service. When testing, the outbound web service action does run the request message and response message. So, data can be impacted. Therefore, you are advised to only test an outbound web service action in a Development or Test environment. For the result of an outbound web service action test, view the message history of the related request message and response message. |
||||||||||||||||||||||
Test inbound web service action |
Application Consultant |
You can test an inbound web service action without receiving an HTTP request from the external application. So, you only test the inbound web service action setup and not the full process with connection to the external application. When testing, the inbound web service action does run the request message and response message. So, data can be impacted. Therefore, you are advised to only test an inbound web service action in a Development or Test environment. For the result of an inbound web service action test, view the Result section on the test page. You can also view the message history of the related request message and response message. |
||||||||||||||||||||||
Monitor web service action history |
Application Consultant |
When a web service action is run, you can view the web service history. The web service history shows, for example, the:
Possible issues can occur, for example, in the:
|
Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Validate connectivity setup |
Application Consultant |
If you open a form or save (changes to) the setup of a key element in Connectivity studio, the setup is validated automatically. If errors are found in the setup, an error icon is shown. You can click the icon to show the related error messages. You can also manually start an automated test to check for errors in the setup. As a result, the found errors are shown. Also, the error icons are shown where applicable.
When errors are found, you can try to fix these errors automatically.
You can check and auto-fix errors for these key elements in Connectivity studio:
In this flow, in the activity steps, as an example, the validation is done for documents.
|
||||||||||||||||||||||
Test outbound web service action |
Application Consultant |
You can test an outbound web service action without sending a request to the external web service. So, you only test the outbound web service action setup and not the full process with connection to the external web service. When testing, the outbound web service action does run the request message and response message. So, data can be impacted. Therefore, you are advised to only test an outbound web service action in a Development or Test environment. For the result of an outbound web service action test, view the message history of the related request message and response message. |
||||||||||||||||||||||
Test inbound web service action |
Application Consultant |
You can test an inbound web service action without receiving an HTTP request from the external application. So, you only test the inbound web service action setup and not the full process with connection to the external application. When testing, the inbound web service action does run the request message and response message. So, data can be impacted. Therefore, you are advised to only test an inbound web service action in a Development or Test environment. For the result of an inbound web service action test, view the Result section on the test page. You can also view the message history of the related request message and response message. |
||||||||||||||||||||||
Monitor web service action history |
Application Consultant |
When a web service action is run, you can view the web service history. The web service history shows, for example, the:
Possible issues can occur, for example, in the:
|
Related to | Notes |
---|---|
Set up web service action - Outbound |
  |
Set up data synchronization - Table events - Outbound web service action |
  |
Set up web service action - Inbound |
  |
Troubleshooting web services |
  |