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.
| Key element | Check |
|---|---|
| Projects | When automatically checked, only the project setup is checked, and not the related setup like messages and connectors. When started manually, the full project setup is checked. |
| Documents | The document setup is checked, including the document records setup. |
| Document records | Only the document records setup is checked. |
| Messages | The message setup is checked, including the data synchronization setup and message mapping. |
| Message - Data synchronization setup | Only the data synchronization setup is checked. |
| Message mapping | Only the message mapping is checked. |
| Message business events | A check is done if a business event is created for the message business event. Also, a check is done if the target fields and source fields match with the related document setup. |
| Connectors | Only the connector setup is checked. |
| Web services | The web service setup is checked, including the data synchronization setup. |
| Web service - Data synchronization setup | Only the data synchronization setup is checked. |
In this flow, in the activity steps, as an example, the validation is done for documents.
| Name | Responsible | Description | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Check setup |
Application Consultant |
If you have finished the setup, you can run a test to check for errors in the setup. You can do so for:
If an error is found, in the message bar, a message is shown indicating the error. If for an entity, an error exists or the setup is incomplete, an error icon In this activity, as an example, the steps explain how to check a document. Where applicable, notes are added to explain how to check the other types. |
||||||||||||||||||||||
|
Auto fix errors |
Application Consultant |
If errors are found by the automated error check, you can first try to have these errors fixed automatically. For example, an error that can be fixed automatically: The field length of an internal document record field does not match the field length in the related table. In this case, the document record field length is changed to the table field length. You can auto-fix errors for:
In this activity, as an example, the steps explain how to auto-fix a document. Where applicable, notes are added to explain how to auto-fix the other types. |
||||||||||||||||||||||
|
Check setup |
Application Consultant |
If you have finished the setup, you can run a test to check for errors in the setup. You can do so for:
If an error is found, in the message bar, a message is shown indicating the error. If for an entity, an error exists or the setup is incomplete, an error icon In this activity, as an example, the steps explain how to check a document. Where applicable, notes are added to explain how to check the other types. |
||||||||||||||||||||||
|
Manually fix errors |
Application Consultant |
If you have re-run the automated error check, and still errors exist in the setup that are not fixed automatically, manually fix these errors. |
| Name | Responsible | Description | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Check setup |
Application Consultant |
If you have finished the setup, you can run a test to check for errors in the setup. You can do so for:
If an error is found, in the message bar, a message is shown indicating the error. If for an entity, an error exists or the setup is incomplete, an error icon In this activity, as an example, the steps explain how to check a document. Where applicable, notes are added to explain how to check the other types. |
||||||||||||||||||||||
|
Auto fix errors |
Application Consultant |
If errors are found by the automated error check, you can first try to have these errors fixed automatically. For example, an error that can be fixed automatically: The field length of an internal document record field does not match the field length in the related table. In this case, the document record field length is changed to the table field length. You can auto-fix errors for:
In this activity, as an example, the steps explain how to auto-fix a document. Where applicable, notes are added to explain how to auto-fix the other types. |
||||||||||||||||||||||
|
Check setup |
Application Consultant |
If you have finished the setup, you can run a test to check for errors in the setup. You can do so for:
If an error is found, in the message bar, a message is shown indicating the error. If for an entity, an error exists or the setup is incomplete, an error icon In this activity, as an example, the steps explain how to check a document. Where applicable, notes are added to explain how to check the other types. |
||||||||||||||||||||||
|
Manually fix errors |
Application Consultant |
If you have re-run the automated error check, and still errors exist in the setup that are not fixed automatically, manually fix these errors. |
