In this article
Table of Contents | ||||
---|---|---|---|---|
|
...
Input/Output | Type of View | Number of Views | Examples of Upstream and Downstream Snaps | Description | ||
---|---|---|---|---|---|---|
Input | Document Binary Binary or Document |
|
| Requires the EDI data and internal ID as a JSON document. | ||
Output | Document Binary Binary or Document |
|
| The EDI transaction ID and order confirmation. |
|
Snap Settings
Parameter |
---|
...
Data Type | Description | Default Value |
---|
...
Example | |
---|---|
Label | String |
...
Field Sets
Specify advanced parameters that you want to include in the request.
This fieldset consists of the following fields:
...
Required. The name for the Snap. You can modify the default name to be specific and meaningful, especially if you have more than one of the same Snaps in your pipeline. | N/A | Ord_354 | ||
Number Of Retries | Integer/Expression | Specify an integer value to set the maximum number of reconnection attempts that the Snap must perform, in case of connection failure or timeout. | 1 | 2 |
---|---|---|---|---|
Order ID | String/Expression | Required. Specify a unique identifier for the order. | N/A | $id |
Retry Interval (Seconds) | Integer/Expression | Specify the duration in seconds for which the Snap must wait between two reconnection attempts, until the number of retries is reached. | 1 | 2 |
Snap Execution | Drop-down list | Select one of the three modes in which the Snap executes. Available options are:
| Validate & Execute | Execute only |
Troubleshooting
Error | Reason | Resolution |
---|---|---|
Batch execution failed | The Pipeline ended before the batch could complete execution due to a connection error. | Verify that the Batch size field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open. |
...