Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Set up message |
Application Consultant |
Use messages as the carriers that transport data from a source to a target, based on the mapping as defined on the message. On a message you define:
|
||||||||||||||||||||||
Set up record mapping |
Application Consultant |
The message is the carrier for all the information that is needed for the integration. On the message record mapping, you define for each target document record the mapped source document record. | ||||||||||||||||||||||
Set up field mapping |
Application Consultant |
The message is the carrier for all the information that is needed for the integration. On the field mapping you define which target document record fields are mapped to which source document record fields. The resulting field mapping is used to get the right data from the source and get it in the right format to the right place in the target.
|
||||||||||||||||||||||
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.
|
Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Set up message |
Application Consultant |
Use messages as the carriers that transport data from a source to a target, based on the mapping as defined on the message. On a message you define:
|
||||||||||||||||||||||
Set up record mapping |
Application Consultant |
The message is the carrier for all the information that is needed for the integration. On the message record mapping, you define for each target document record the mapped source document record. | ||||||||||||||||||||||
Set up field mapping |
Application Consultant |
The message is the carrier for all the information that is needed for the integration. On the field mapping you define which target document record fields are mapped to which source document record fields. The resulting field mapping is used to get the right data from the source and get it in the right format to the right place in the target.
|
||||||||||||||||||||||
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.
|
Related to | Notes |
---|---|
Add message to task |
  |
Review and complete data migration setup |
  |