...
Input schema specifies the structure of the data that a service or system expects to receive. It defines the required fields, data types, and any validation rules that the incoming data must adhere to.
Output schema defines the structure of the data that a service or system will produce and send back as a response. It ensures that the response data is formatted correctly and contains all the necessary information.
For HTTP Service type like Shopify, use webhooks or API calls in JSON format
(See Sample 1 & 1a)
Sample 1:
...
For SQL Service Type like Seko systems
...
(DCM, TMS,
...
WMS, DMS, PSMS) specify the list of fields you use as a source for SP parameters (See Sample
...
Sample 1:
...
Sample 2:
...
here)
Part III - Trigger Configuration
...
Click SAVE button to save configuration
Click SAVE button to save the version
Sample 1a
...
Sample 2a
...
Pipeline Templates Menu
Templates are pre-defined pipelines which follow the same structure that can be reused for different Clients. This reduces errors and saves time and effort, as you don’t have to start from scratch each time.
...
Pipeline action steps are the individual tasks or actions that are executed as part of a pipeline. These steps define the specific operations that need to be performed, such as building code, running tests, deploying applications, or any other automated tasks.
SAVE the Template
...
See Also: https://seko.atlassian.net/wiki/x/OwDJsQ