Sending data via REST or SOAP

Scheduled integration functionality that performs aQuery in Database, and directs the result to a destination WebService that can operate in REST or SOAP.

Then up to 3 can be configuredQueries Transactional (Insert, Update and Delete) to be executed in case of success, error and/or always.

• Register the search Sql;
• Enter the partner service data (URL, authorization, ...) that will receive the query results;
• Define the negotiations according to the return of the partner service;
• Set the frequency.

JOB Listing Sending Data (REST/SOAP)

The list screen displays all Data Submission Jobs in the environment, allowing users to view the Method Name (integration identifier), last modification date, and active integration indicator. In the actions tab you can call theURL from the endpoint, go to the edit screen, delete the record, export (for backups or migration) or navigate to the integration monitoring screen.

Creating a Data Sending JOB (REST/SOAP)

Available fields and their respective functionalities:

• Active: Defines whether the endpoint can be called;
• Method name: Endpoint identifier;
• Database: CadastroDB record in which the query will be executed;
• CRON Scheduling: Code with 6 parameters that define the periodicity of the integration according to [http://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/crontrigger.html](http://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/crontrigger.html)
• Return Encoding: Encoding to be used in the data that is sent to the destination Web Service;
• Integration queue: Execution context within the environment, scope of processing queues;
• SQL Field: Defines the SQL query that will be processed by the database.
• Authorization: Defines the settings of the Web Service that will be responsible for processing the result of the Query performed.
• WS URL : URL for the Web Service call that will receive the query data;
• WS Method: Request method for the Web Service;
• Web Service Authorization Type: None (public), Bearer (hardcoded) or Basic Auth (associated with a Platform Credential record);
• WS Token: Token or Credential to be associated with the Web Service Authorization Type.