| 1. | Click Connectivity studio Integration Design. |
| 2. | Click the Web service tab. |
| 3. | In the list, find and select the desired web service action. |
| 4. | Click Edit. |
| 5. | Expand the Setup for data synchronization section. |
| 6. | In the Synchronization type field, select 'Table events'. |
| 7. | Each table event that occurs to a record is logged in the data synchronization log for that record and related table. On processing the data synchronization log, by default, log entries for a child record of the source document are added to outbound message queue for the root record of the source document. Example: The source document has a root record 'Sales order' and a child record 'Sales line'. A table event is logged for a sales line. If Redirect event is: - Yes, the sales order record is added to the outbound message queue instead of the logged sales line record. As a result, the sales order and all its sales lines are exported by the web service action. - No, the sales line record is added to the outbound message queue. As a result, only the logged sales line and the sales order are exported by the web service action. You can choose to not redirect events to the root record. |
| Select No in the Redirect event field. | |
| 8. | In the outbound message queue, several entries can exist for a unique message. On processing the outbound message queue, all entries for a unique message can be bundled in one message run, which results in one file. You can choose to bundle outbound message queue entries. |
| Select Yes in the Bundle outbound queue by message field. | |
|
Note: You cannot apply bundling to an outbound web service action that uses a stream. |
|
| 9. | Sub-task: Add data synchronization records. |
| 9.1 | You can initialize the table event records based on the records of the source document of the request message. For each source document record, a record is added. |
| Click Initialize. | |
|
Note: You can also add table event records manually. To do so, click New. You can only select a record from the source document of the request message. |
|
| 9.2 | For each added record, define the applicable settings. |
| In the list, find and select the desired record. | |
| 9.3 | Decide if you want to log record inserts for the record. |
| Select or clear the Insert check box. | |
| 9.4 | Decide if you want to log record updates for the record. |
| Select or clear the Update check box. | |
| 9.5 | Decide if you want to log record deletions for the record. |
| Select or clear the Delete check box. | |
| 9.6 | If the Update check box is selected, decide if you want to restrict table event logging to only the fields as defined for the record in the source document of the request message. If selected, only changes to the fields of the source document record are logged. If cleared, all changes to the record are logged. |
| Select or clear the Check used fields check box. | |
| 9.7 | Define the desired type of the table event triggers: - SQL trigger: You can generate the SQL triggers in your database. So, no custom coding is required in the database. - Event handler: You must add custom code to the related tables for each selected event. This results in a better performance and can be useful for transactions like sales orders. |
| In the Trigger type field, select an option. | |
| 10. | Sub-task: Create SQL triggers. |
| 10.1 | If you have records with the trigger type 'SQL trigger' selected, create the SQL triggers. |
| Click Create SQL triggers. | |
|
Note: To view the created SQL triggers, click SQL trigger. All existing SQL triggers for all messages are shown. |
|
| 11. | Close the page. |
To apply the 'Table events' data synchronization setup, select Yes in the process outbound queue field on the dialog to run a:
You can also directly process the outbound queue.
| Related to | Notes |
|---|---|
|
Set up data synchronization for outbound web service action |