Input 

• Binary

• Document

• Min: 1

• Max: 1

• Mapper

• Copy

The document or binary data to send to the child Pipeline.

Output

• Binary

• Document

• Min: 1

• Max: 1

• Mapper

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the pipeline by choosing one of the following options from the When errors occur list under the Views tab:

• Stop Pipeline Execution: Stops the current pipeline execution if the Snap encounters an error.

• Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

• Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Label*

Default Value: ELT Database Account
Example: ELT RS Account

String

The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

Pipeline*

Default Value: N/A
Example: demo-child-pipeline

String/Expression

Specify the path of the pipeline to execute.

Pipeline Parameters

Use this field set to define child pipeline parameters to use for executing the pipeline.

Parameter name

Default Value: <value> or None.
Example: <value>

String/Suggestion

Specify the name of the parameter. You can select the Pipeline Parameters defined for the Pipeline selected in the Pipeline field.

Parameter value

Default Value: <value> or None.
Example: <value>

String/Expression

Specify the value for the pipeline parameter, which can be an expression based on incoming documents or a constant. 

If you configure the value as an expression based on the input, then each incoming document or binary data is evaluated against that expression when invoking the pipeline. The result of the expression is JSON-encoded if it is not a string. The child Pipeline then needs to use the JSON.parse() expression to decode the parameter value.

When Reuse executions to process documents is enabled, the parameter values cannot change from one invocation to the next.

Loop options

Define the iteration configuration.

Stop condition

Default Value: N/A
Example:

String/Expression

Specify the condition to be evaluated during execution. The loop execution stops when the stop condition is met.

Iteration limit

Default Value: 10
Example: 15

Integer/Expression

Specify the maximum limit for the number of iterations to run.

Debug iteration outputs

Default Value: 
Example:

Checkbox

Select this checkbox to list the documents from each iteration, index and stop condition evaluation for debug purposes.

Execution options

Define the child pipeline execution configuration.

Execute on

Default Value: LOCAL_NODE
Example: SNAPLEX_WITH_PATH

Dropdown list

Select the one of the following Snaplex options to specify the target Snaplex for the child Pipeline:

• SNAPLEX_WITH_PATH: Runs the child Pipeline on a user-specified Snaplex.

• LOCAL_NODE: Runs the child Pipeline on the same node as the parent Pipeline.

• LOCAL_SNAPLEX: Runs the child Pipeline on one of the available nodes in the same Snaplex as the parent Pipeline.

Snaplex path

Default Value: N/A
Example:

String/Expression

Appears when you choose the SNAPLEX_WITH_PATH option.

Specify the Snaplex to execute on.

Execution label

Default Value: N/A
Example: demo

String/Expression

Specify the label to display in the Dashboard for the current execution.

Snap Execution

Default Value: 
Example: Validate & Execute

Dropdown list

Select one of the following three modes in which the Snap executes:

• 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.

Account validation failed.

The Pipeline ended before the batch could complete execution due to a connection error.

Verify that the Refresh token 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.