Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Copy message |
Application Consultant |
You can create a copy of a message. For example, to troubleshoot a failing message that is already in operation, you can copy the message. So, you do not disrupt the operational data. |
||||||||||||||||||||||
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.
|
||||||||||||||||||||||
Add file to Working folder |
Application Consultant |
If you want to test an import message with an external file-based source document, you need a file with test data to be imported. This file must be available in the Working folder that is defined for the source connector. You can add the test data file to the Work folder in these ways:
|
||||||||||||||||||||||
Run message for testing purposes |
Application Consultant |
You can run a message for testing and troubleshooting purposes. You can find and analyze the results in the:
Note: If the message setup is validated, a message run can still result in errors or give an unexpected result. In this case, you can choose to store all processed records in the message history for analysis purposes. To do so, before the test run, on the message header, set the Store history field to 'Yes'. When the issue is solved, do not forget to set the Store history field back to 'No'.
|
||||||||||||||||||||||
Monitor message history |
Application Consultant |
You can review and analyze the history of message runs that have run with errors. You can investigate these errors and take the appropriate actions to solve the errors. If the errors are solved, you can re-run the message run. To monitor the message history, use the Connectivity studio integration operations workspace.
|
||||||||||||||||||||||
Monitor file history |
Application Consultant |
You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history.
Registered file actions are the:
You can monitor the file history from the Connectivity studio Integration operations workspace.
|
||||||||||||||||||||||
Analyze tracer |
Application Consultant |
When you run a message for testing purposes, you can use a tracer to register what the message does when it is run. When the message has run using the tracer, you can review the registered actions in the tracer. Usually, you use this to find issues in the message run. | ||||||||||||||||||||||
Merge message |
Application Consultant |
You can troubleshooted a failing message using a copy of that message. When you have made changes to the message copy to solve the issue, the same changes must be applied to the original message. To do so, you can merge the message copy with the original message. When you merge a message (source) with another message (target), the:
Note: Use this merge option carefully. You cannot undo the overwrite action. |
Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Copy message |
Application Consultant |
You can create a copy of a message. For example, to troubleshoot a failing message that is already in operation, you can copy the message. So, you do not disrupt the operational data. |
||||||||||||||||||||||
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.
|
||||||||||||||||||||||
Add file to Working folder |
Application Consultant |
If you want to test an import message with an external file-based source document, you need a file with test data to be imported. This file must be available in the Working folder that is defined for the source connector. You can add the test data file to the Work folder in these ways:
|
||||||||||||||||||||||
Run message for testing purposes |
Application Consultant |
You can run a message for testing and troubleshooting purposes. You can find and analyze the results in the:
Note: If the message setup is validated, a message run can still result in errors or give an unexpected result. In this case, you can choose to store all processed records in the message history for analysis purposes. To do so, before the test run, on the message header, set the Store history field to 'Yes'. When the issue is solved, do not forget to set the Store history field back to 'No'.
|
||||||||||||||||||||||
Monitor message history |
Application Consultant |
You can review and analyze the history of message runs that have run with errors. You can investigate these errors and take the appropriate actions to solve the errors. If the errors are solved, you can re-run the message run. To monitor the message history, use the Connectivity studio integration operations workspace.
|
||||||||||||||||||||||
Monitor file history |
Application Consultant |
You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history.
Registered file actions are the:
You can monitor the file history from the Connectivity studio Integration operations workspace.
|
||||||||||||||||||||||
Analyze tracer |
Application Consultant |
When you run a message for testing purposes, you can use a tracer to register what the message does when it is run. When the message has run using the tracer, you can review the registered actions in the tracer. Usually, you use this to find issues in the message run. | ||||||||||||||||||||||
Merge message |
Application Consultant |
You can troubleshooted a failing message using a copy of that message. When you have made changes to the message copy to solve the issue, the same changes must be applied to the original message. To do so, you can merge the message copy with the original message. When you merge a message (source) with another message (target), the:
Note: Use this merge option carefully. You cannot undo the overwrite action. |
Related to | Notes |
---|---|
Troubleshooting integration |
  |
Message process |
  |
Solve errors - Message run |
  |
Troubleshooting messages |
  |