Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


In this article

Table of Contents
maxLevel2
absoluteUrltrue

...

Input/OutputType of ViewNumber of ViewsExamples of Upstream and Downstream SnapsDescription
Input 

Document

Binary

Binary or Document

  • Min:
  • Max:
  • Mapper Snap
  • Copy Snap
  • ..
Requires the EDI data and internal ID as a JSON document.
Output

Document

Binary

Binary or Document

  • Min:
  • Max:
  • ..
  • ..

The EDI transaction ID and order confirmation.

  • Mapper Snap
  • Copy Snap


Snap Settings


Parameter

...

Data Type
Description
Default Value

...

Example
LabelString

...

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/AOrd_354
Number Of RetriesInteger/ExpressionSpecify an integer value to set the maximum number of reconnection attempts that the Snap must perform, in case of connection failure or timeout.12
Order IDString/ExpressionRequired. Specify a unique identifier for the order.N/A$id
Retry Interval (Seconds)Integer/ExpressionSpecify the duration in seconds for which the Snap must wait between two reconnection attempts, until the number of retries is reached.12
Snap Execution

Drop-down list


Select one of the three modes in which the Snap executes. Available options are:

  • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.
  • Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.
  • Disabled: Disables the Snap and all Snaps that are downstream from it.

Validate & ExecuteExecute only


Troubleshooting

ErrorReasonResolution

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.




...