In this Article

Snap type:

Flow

Description:

This Snap is for executing Pipelines and passing documents into and out of these executions. The following execution modes are supported by this Snap:

Execute a Pipeline for every input document. If the target Pipeline has an unlinked input view, then the input document to this Snap is passed into the unlinked input of the child execution. Similarly, if the target Pipeline has an unlinked output view, then the output document from the child Pipeline execution is used as the output document from the Pipeline Execute Snap.
Execute one or more Pipelines and reuse them to process multiple input documents to this Snap. The child Pipeline must have one unlinked input view and one unlinked output view. As documents are received by this Snap, they are passed to the child Pipeline executions for processing. Any output documents from the child Pipeline executions are used as the output of this Snap.

You can execute Pipelines on the same Snaplex node that the parent Pipeline is running without contacting the SnapLogic cloud. In this mode, the Snap does not need to connect with the SnapLogic cloud servers, allowing you to use this Snap in an Ultra Pipeline. For example, you can use Snaps that do not support Ultra mode with this design.

Deprecated Snaps

This Snap replaces the ForEach and Task Execute Snaps, as well as the Nested Pipeline mechanism.

Schema Propagation

If the child Pipeline has a Snap that supports schema suggest, such as the JSON Formatter Snap or MySQL Insert Snap, then the schema is back propagated to the parent Pipeline. This is useful in mapping input values in the parent Pipeline to the corresponding fields in the child Pipeline using a Mapper Snap in the parent Pipeline.
For the schema suggest to work, the parent Pipeline must be validated first; only then is the schema from the child Pipeline visible in the parent Pipeline.
The Pipeline Execute Snap is capable of propagating schema in both directions: upstream as well as downstream. See the example Schema Propagation in Parent Pipeline – 3.

If there are not enough free resources to execute the Pipeline on the Snaplex, the Snap will wait until resources are available and display the following message in the execution statistics dialog:

Because a large number of executions can be generated by this Snap, only the last 100 completed child executions will be saved for inspection in the Dashboard.

This Snap will eventually replace the ForEach and Task Execute Snaps, as well as the Nested Pipeline mechanism.

Schema Propagation

If the child Pipeline has a Snap that supports schema suggest, such as the JSON Formatter Snap or MySQL Insert Snap, then the schema is back propagated to the parent Pipeline. This is useful in mapping input values in the parent Pipeline to the corresponding fields in the child Pipeline using a Mapper Snap in the parent Pipeline.
For the schema suggest to work the parent Pipeline has to be validated first, only then will the schema from the child Pipeline be visible in the parent Pipeline.
The Pipeline Execute Snap is capable of propagating schema in both directions: upstream as well as downstream. Refer to example "Schema Propagation in Parent Pipeline – 3".

Prerequisites:

None

Support and limitations:

If there are not enough nodes to execute the Pipeline on the Snaplex, the Snap waits until resources are available; and the following message appears in the execution statistics dialog:

Because a large number of Pipeline runs can be generated by this Snap, only the last 100 completed Child Pipeline runs are saved for inspection in the Dashboard.
Works in Ultra Pipelines with the following exception: reusing an execution on another Snaplex is not supported.
Supported in eXtreme mode.

Account:

Accounts are not used with this Snap.

Views:

The Input/Output views on the Views tab are configurable.

Input	This Snap has at most one document or binary input view. Documents or binary data received on this view are sent to the child Pipeline if the child Pipeline has an unlinked input view. The document or binary data can be used to specify Pipeline parameters for the child Pipeline run.
Output	This Snap has at most one document or binary data output view. If the child Pipeline has an unlinked output, then documents or binary data from that view are passed out of this view. If the child Pipeline does not have an unlinked view, then output document or binary data is generated for successful runs with the following field: run_id. Unsuccessful runs write a document to the error view. If reuse is disabled, then the original input document or binary data is added to output document. If the pool size property is greater than one, then the order of the output is not guaranteed to be the same as the input.
Error	This Snap has at most one document error view and produces zero or more documents in the view. If the Pipeline execution does not complete successfully, a document will be written to this error view.

Settings

Label Required. 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

Required. The absolute or relative path to the child Pipeline to run. If only the Pipeline name is given, then the Snap searches for the Pipeline in the following folders in this order:

Current project.
Shared project-space.
Shared directory of that Org.

You can also dynamically choose the Pipeline to execute by turning this property into an expression. For example, to execute all of the Pipelines in a project, you can connect the SnapLogic List Snap to this Snap to get the list of Pipelines in the project and execute each one.

The child Pipeline must be designed to be compatible with this Snap. The current requirements are:

No unlinked binary input or output views.

When this property is an expression, the Snap needs to contact the SnapLogic cloud servers to load the Pipeline information for execution. Also, if reuse is enabled, the result of the expression cannot change between documents.
When reusing Pipeline executions, there must be one unlinked input view and zero or one unlinked output view.
If reuse is not enabled, then use at most one unlinked input view and one unlinked output view.
If the child Pipeline has an unlinked input view, make sure this Snap has an input view because the input document or binary data is fed into the child Pipeline.
.

You must manually update the reference to the child Pipeline. If you rename the child Pipeline, then the connection between child and parent Pipeline breaks.
The child Pipeline is executed in preview mode when the Pipeline containing this Snap is saved. Consequently, any Snaps marked not to execute in preview mode are not executed and the child Pipeline only processes 50 documents.
You cannot have a Pipeline call itself (recursion is not supported).

Default value: N/A

Execute On

Select the Snaplex or node on which you want to execute the child Pipeline:

SNAPLEX_WITH_PATH: On a Snaplex that is different from the one on which the parent Pipeline must run.

If you choose this option, a new field, Snaplex Path, appears below this field. For information on working with this field, see If you do not specify a Snaplex, this selection behaves like the LOCAL_NODE option.
LOCAL_NODE: On the same node as the parent Pipeline.
LOCAL_SNAPLEX: On a node in the local Snaplex.

Default value: LOCAL_NODE

Snaplex Path

Required when the option selected in the Execution On field is SNAPLEX_WITH_PATH. Select the Snaplex on which you want the child Pipeline to run. To select from the list of Snaplexes available in your Org, click the icon.

Default value: N/A

Execution label

The label to display in the Pipeline view of the Dashboard. By default, the child Pipeline's label is used. You can use this property to differentiate one execution from another.

Default value: N/A

Pipeline parameters

You can configure Pipeline parameters used for executing the Pipeline in this property. Select the Pipeline parameters defined for the Pipeline selected in the Pipeline field. The Parameter value is the expression property that you can configure as an expression based on incoming documents, or this value can be a constant.

When reuse is enabled, the parameter values cannot change from one invocation to the next.

Parameter name

The Parameter name is the name of the parameter used while executing the Pipeline. You can select the Pipeline parameters defined for the Pipeline selected in the Pipeline field.

Default value: N/A

Parameter value

The Parameter value is the expression property that can be configured as an expression based on incoming documents or can be entered as a constant.

If the value is configured as an expression based on the input, each incoming document or binary data is evaluated for the given expression and the value is set as the parameter value for the parameter name while invoking the Pipeline. The result of the expression evaluation 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.

Default value: N/A

When reuse is enabled, the parameter values cannot change from one invocation to the next.

Reuse executions to process documents

This flag specifies the execution mode to use. When enabled, the Snap starts a child execution and passes multiple inputs to the Pipeline. Reusable executions continue to live until all of the input documents to this Snap have been fully processed.

If this flag is not enabled, then a new Pipeline execution is created for each input document.

Pipeline parameter values can only be changed if this flag is not enabled. In other words, reusable executions cannot have different Pipeline parameter values for different documents.

Ultra Mode Compatibility

If reuse is enabled and this Snap is used in an Ultra Pipeline, then the Snaps in the child Pipeline must also be Ultra-compatible.

If you need to use Snaps that are not Ultra-compatible in an Ultra Pipeline, you can create a child Pipeline with those Snaps and use a Pipeline Execute Snap with reuse disabled to invoke the Pipeline. Since the child Pipeline is executed for every input document, the Ultra Pipeline restrictions do not apply.

For example, if you want to run an SQL Select operation on a table that would return more than one document, you can put a Select Snap followed by a Group By N Snap with the group size set to zero in a child Pipeline. In that configuration, the child Pipeline is executed, performs the select operation, and then the Group By Snap gathers all of the outputs into a single document or binary data. That single output document or binary data can then be used as the output of the Ultra Pipeline.

Default value: Not selected

Number of Retries

The maximum number of retry attempts that the Snap must make in case of a network failure. If the child Pipeline does not execute successfully, an error document is written to the error view.

This feature is incompatible with reusable executions.

Example: 3

Default value: 0

Retry Interval

The minimum number of seconds for which the Snap must wait between two successive retry requests. A retry happens only when the previous attempt resulted in an exception.

Example: 10

Default value: 1

Pool size

Multiple input documents or binary data can be processed concurrently by specifying an execution pool size. When the pool size is greater than one, the Snap starts executions as needed up to the given pool size. When Reuse is enabled, the Snap starts a new execution only if all executions are busy working on documents or binary data and the total number of executions is below the pool size. However, in Spark mode, if you execute multiple Pipelines simultaneously, the Hadoop cluster might face resource constraints, depending upon the complexity of the Pipelines and the size of the documents being processed.

Default value: 1

Timeout

The maximum number of seconds for which the Snap must wait for the child Pipeline to complete execution. If the child Pipeline does not complete executing before the timeout, the execution process stops and is marked as failed.

Example: 10

Default value: 0 (No timeout is the default)

Snap execution

Page lookup error: page "Anaplan Read" not found.

If you're experiencing issues please see our Troubleshooting Guide.

Examples

Execute Child Pipeline Multiple Times

Pipeline Execution Example

The project, PE_Multiple_Executions,demonstrates how the Pipeline Execute Snap can be configured to execute a child Pipeline multiple times. It contains the following Pipelines:

PE_Multiple_Executions_Child - A simple child Pipeline that writes out a document with static string and the number of input documents received by the Snap.
PE_Multiple_Executions_NoReuse_Parent - A parent Pipeline that executes the PE_Multiple_Executions_Child Pipeline five times. You can save the Pipeline to examine the output documents. Note that the output contains a copy of the original document and the $inCount field is always set to one because the Pipeline was separately executed five times.
PE_Multiple_Executions_Reuse_Parent - A parent Pipeline that executes the PE_Multiple_Executions_Child Pipeline once and feeds the child execution five documents. You can save the Pipeline to examine the output documents. Note that the output does not contain a copy of the original document and the $inCount field goes up for each document since the same Snap instance is being used to process each document.
PE_Multiple_Executions_UltraSplitAggregate_Parent- A parent Pipeline that is an example of using Snaps that are not Ultra-compatible in an Ultra Pipeline . This Pipeline can be turned into an Ultra Pipeline by removing the JSON Generator Snap at the head of the Pipeline and creating an Ultra Task.
PE_Multiple_Executions_UltraSplitAggregate_Child- A child Pipeline that splits an array field in the input document and sums the values of the $num field in the resulting documents.

Converting Existing Pipelines

Converting existing pipelines

The Pipeline Execute Snap can replace some uses of the Nested Pipeline mechanism as well as the ForEach and Task Execute Snaps. For now, this Snap only supports child Pipelines with unlinked document views (binary views are not supported). If these limitations are not a problem for your use case, read on to find out how you can transition to this Snap and the advantages of doing so.

Nested Pipeline

Converting a Nested Pipeline will require the child Pipeline to be adapted to have no more than a single unlinked document input view and no more than a single unlinked document output view. If the child Pipeline can be made compatible, then you can use this Snap by dropping it on the canvas and selecting the child Pipeline for the Pipeline property. You will also want to enable the Reuse property to preserve the existing execution semantics of Nested Pipelines. The advantages of using this Snap over Nested Pipelines are:

Multiple executions can be started to process documents in parallel.
The Pipeline to execute can be determined dynamically by an expression.
The original document or binary data is attached to any output documents or binary data if reuse is not enabled.

ForEach

Converting a ForEach Snap to the Pipeline Execute Snap is pretty straightforward since they have a similar set of properties. You should be able to select the Pipeline you would like to run and populate the parameter listing. The advantages of using this Snap over the ForEach Snap are:

Documents or binary data fed into the Pipeline Execute Snap can be sent to the child execution through an unlinked input view in the child.
Documents or binary data sent out of an unlinked output view in the child execution is written out of the Pipeline Execute's output view.
The execution label can be changed.
The Pipeline to execute can be determined dynamically by an expression.
Executing a Pipeline does not require communication with the cloud servers.

Task Execute

Converting a Task Execute Snap to the Pipeline Execute Snap is also straightforward since the properties are similar. To start, you only need to select the Pipeline you would like to use, you no longer have to create a Triggered Task. If you set the Batch Size property in the Task Execute to one, then you will not want to enable the Reuse property. If the Batch Size was greater than one, then you should enable Reuse. The Pipeline parameters should be the same between the Snaps. The advantages of using this Snap over the Task Execute Snap are:

A task does not need to be created.
Multiple executions can be started to process documents in parallel.
There is no limit on the number of documents that can be processed by a single execution (i.e. no batch size).
The execution label can be changed.
The Pipeline to execute can be determined dynamically by an expression.
The original document will be attached to any output documents if reuse is not enabled.
Executing a Pipeline does not require communication with the cloud servers.

"Auto" Router

Converting a Pipeline that uses the Router Snap in "auto" mode can be done by moving the duplicated portions of the Pipeline into a new Pipeline and then calling that Pipeline using a Pipeline Execute. After refactoring the Pipeline, you can adjust the "Pool Size" of the Pipeline Execute Snap to control how many operations are done in parallel. The advantages of using this Snap over an "Auto" Router are:

De-duplication of Snaps in the Pipeline.
Adjusting the level of parallelism is trivially done by changing the "Pool Size".

Propagate Schema Backward – 1

Schema propagation in parent pipeline - 1

The project, PE_Backward_Schema_Propagation_Contacts, demonstrates the schema suggest feature of the Pipeline Execute Snap. It contains the following files:

PE_Backward_Schema_Propagation_Contacts_Parent
PE_Backward_Schema_Propagation_Contacts_Child
contact.schema (Schema file)
test.json (Output file)

The parent Pipeline is shown below:

The child Pipeline is as shown below:

The Pipeline Execute Snap is configured as:

The following schema is provided in the JSON Formatter Snap. It has three properties - $firsName, $lastName, and $age. This schema is back propagated to the parent Pipeline.

The parent Pipeline must be validated in order for the child Pipeline's schema to be back-propagated to the parent Pipeline. Below is the Mapper Snap in the parent Pipeline:

Notice that the Target Schema section shows the three properties of the schema in the child Pipeline:

Upon execution the data passed in the Mapper Snap will be written into the test.json file in the child Pipeline. The exported project is available in the Downloads section below.

Schema Propagation in Parent Pipeline – 2

Schema propagation in parent pipeline - 2

The project PE_Backward_Schema_Propagation_Books demonstrates the schema suggest feature of the Pipeline Execute Snap wherein a new record is inserted into the target table with the MySQL Insert Snap being the one that back-propagates schema. It contains the following Pipelines:

PE_Backward_Schema_Propagation_Books_Parent
PE_Backward_Schema_Propagation_Books_Child

The record to be inserted is passed through the parent Pipeline is shown below:

The parent Pipeline must be validated in order for the child Pipeline's schema to be back propagated to the parent Pipeline. Below is the Mapper Snap in the parent Pipeline. Notice that the Target Schema section shows the three properties of the schema in the child Pipeline:

The Pipeline Execute Snap is configured as:

The child Pipeline is as shown below:

The MySQL Insert Snap is configured as shown below, note here that only specifying the table name will also suffice, the schema shown in the Mapper Snap is automatically taken from the table.

Upon execution the record (passed through the Pipeline Execute Snap) is written into the target table. This can be confirmed using a standalone MySQL Select Snap. The following screenshot shows all the records in the target table after the Pipeline is executed with the latest insert highlighted.

The exported project is available in the Downloads section below.

Propagate Schema Backward and Forward

Backward and forward schema propagation

The project, PE_Backward_Forward_Schema_Propagation, demonstrates the Pipeline Execute Snap's capability of propagating schema in both directions – upstream as well as downstream. It contains the following Pipelines:

PE_Backward_Forward_Schema_Propagation_Parent
PE_Backward_Forward_Schema_Propagation_Child

The parent Pipeline is as shown below:

The Pipeline Execute Snap is configured to call the Pipeline schema-child. This child Pipeline consists of a Mapper Snap that is configured as shown below:

The Mapper Snaps upstream and downstream of the Pipeline Execute Snap: Mapper_InputSchemaPropagation, and Mapper_TargetSchemaPropagation are configured as shown below:

When the Pipeline is executed, data propagation takes place between the parent and child Pipeline:

The string expression $foo is propagated from the child Pipeline to the Pipeline Execute Snap.
The Pipeline Execute Snap propagates it to the upstream Mapper Snap (Mapper_InputSchemaPropagation), as visible in the Target Schema section. Here it is assigned the value 123.
This is passed from the Mapper to the Pipeline Execute Snap that internally passes the value to the child Pipeline. Here $foo is mapped to $bar. $baz is another string expression in the child Pipeline (assigned the value 2).
$bar, and $baz are propagated to the Pipeline Execute Snap and propagated forward to the downstream Mapper Snap (Mapper_TargetSchemaPropagation). This can be seen in the Input Schema section of the Mapper Snap.

The exported project is available in the Downloads section below.

These zip files are exported projects. They have to be imported into a project space to be used. To do this go to Manager, navigate to a project space and select Import from the drop-down menu. If you are unable to import the project, the Pipeline's files (SLP) are also included in the Download section for you to download and import.

Downloads

	File	Modified

No files shared here yet.

Snap Pack History

Click to view/expand

Release	Snap Pack Version	Date	Type	Updates
November 2024	main29029	13 Nov 2024	Stable	Updated and certified against the current SnapLogic Platform release.
August 2024	438patches28470	22 Oct 2024	Latest	Added the PipeLoop Snap that enables you to loop on pipeline executions based on a stop condition or iteration limit. The execution workflow of this Snap enables the parent pipeline to control and manage iterative processes using the child pipeline, for scenarios where repeated processing is needed until a specific stop condition is met.
August 2024	438patches28047	16 Sep 2024	Latest	Enhanced the Head and Tail Snaps (for the Number of documents and Document offset fields) to support pipeline parameters via expressions that enable you to reuse the pipelines.
August 2024	main27765	21 Aug 2024	Stable	When the Router Snap was the first Snap in a triggered task, the documents were not processed. Previously, the response contained a `200 status code` but was empty. Now, it processes one document and provides non-empty output. Behavior change: Previously, the Router Snap generated no output without an input document. Now, the Snap generates an empty document when no input document is provided.
May 2024	437patches26857	10 Jul 2024	Latest	Enhanced the Pipeline Execute Snap to support expression values via pipeline parameters for the Batch size field that enables you to use intermediate pipelines for generic use cases.
May 2024	main26341	08 May 2024	Stable	Updated and certified against the current SnapLogic Platform release.
March 2024	436patches25576	19 Mar 2024	Latest	Fixed an issue with the Pipeline Execute Snap where a condition resulted in the output documents not being read.
February 2024	main25112	14 Feb 2024	Stable	Updated and certified against the current SnapLogic Platform release.
November 2023	main23721	08 Nov 2023	Stable	Updated and certified against the current SnapLogic Platform release.
August 2023	434patches22576	23 Aug 2023	Latest	Fixed an issue with the Pipeline Execute Snap that caused a null pointer exception during the retry when the input view was a Binary type. Retry is not supported for a Binary input view with this Snap.
August 2023	main22460	16 Aug 2023	Stable	Updated and certified against the current SnapLogic Platform release.
May 2023	433patches22107	08 Aug 2023	Latest	Fixed an issue with the Pipeline Execute Snap that caused it to acknowledge the Ultra pipeline message before the message reached the last Snap in the pipeline. Because of the early acknowledgment, the last Snap in the pipeline failed and the response could not be sent back.
May 2023	433patches21744	28 Jun 2023	Latest	Fixed an issue with the Pipeline Execute Snap where a missing label produced a null pointer exception.
May 2023	433patches21196	25 May 2023	Latest	Fixed an issue with the Pipeline Execute Snap where no input view produced a null pointer exception.
May 2023	433patches21040	15 May 2023	Latest	Provided a fix to ensure the Data Validator works with "unknown" data types.
May 2023	main21015	10 May 2023	Stable	Upgraded with the latest SnapLogic Platform release.
February 2023	432patches20279	29 Mar 2023	Latest	The Pipeline Execute Snap now returns errors from child pipelines with a unique identifier.
February 2023	432patches19695	07 Mar 2023	Latest	Fixed an issue with the Pipeline Execute Snap that was causing `Unable to create a deep copy of the object` errors. As of 29 Mar 2023 we have discovered an issue with this patch affecting the Pipeline Execute Snap. If you have pipelines leveraging the Pipeline Execute Snap, we recommend you NOT use this patch and instead use patch 432patches20279.
February 2023	main19844	09 Feb 2023	Stable	Upgraded with the latest SnapLogic Platform release.
November 2022	main18944	10 Nov 2022	Stable	Upgraded with the latest SnapLogic Platform release.
September 2022	430patches18070	22 Sep 2022	Latest	The Pipeline Execute Snap with binary output that is used in a low-latency feed Ultra Pipeline now works as expected. The requests are now acknowledged correctly.
August 2022	main17386	11 Aug 2022	Stable	Upgraded with the latest SnapLogic Platform release.
4.29	main15993	14 May 2022	Stable	Upgraded with the latest SnapLogic Platform release.
4.28 Patch	428patches15026	22 Mar 2022	Latest	Fixed an issue with HTTP Router Snap where the Snap did not work as intended for a GET request that used a Cloud URL when the HTTP Router was the first Snap in the triggered task Pipeline.
4.28	main14627	12 Feb 2022	Stable	Enhanced the Filter Snap with the Null-safe access checkbox. Select this checkbox to consider the valid values in the filter expression and remove the missing or empty data instead of treating them as null.
4.27 Patch	427patches13726	18 Jan 2022	Latest	Enhanced the Filter Snap with the Null-safe access checkbox. Select this checkbox to consider the missing data or empty value as null when accessing the source path.
4.27	main12833	13 Nov 2021	Stable	Enhanced the Gate Snap with the Output Document Content field that enables you to indicate the count of input documents and the specific (first or last) document to include in the output.
4.26	main11181	14 Aug 2021	Stable	Added Binary Copy Snap to copy a binary stream to the Snap’s output views. You can use this Snap if you want to send the same information to multiple endpoints.
4.25 Patch	425patches10571	08 Sep 2021	Latest	Enhanced the performance of Binary Router Snap via more efficient IO utilization.
4.25	main9554	08 May 2021	Stable	Enhanced the HTTP Router Snap to support Ultra Pipelines.
4.24	main8556	13 Feb 2021	Stable	Added the Ignore empty stream checkbox to the Gate Snap Settings
4.23	main7430	14 Nov 2020	Stable	Enhances the Data Validator Snap by making the Constraint value field as optional under the Constraints.
4.22	main6403	12 Sep 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.21 Patch	flow8855	-	Latest	Fixes the Binary Router Snap's failure in Ultra Pipelines by preventing a deep-copy (performing a copy of the original objects recursively) of binary data headers.
4.21	snapsmrc542	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.20	snapsmrc535	-	Latest	Adds a new Snap, Gate, which enables you to consolidate multiple input streams into a single output document where each input stream is displayed as a label containing the list of records that were received by that input view. The Pipeline Execute Snap now provides the following capabilities: Specify the Snaplex on which to run child Pipelines. You can now select the Snaplex on which to run the child Pipelines through the Execute On and Snaplex Path fields. The default option is executing the child Pipeline on the same Snaplex node as the Parent, but you can also specify a different Snaplex through the drop-down list, which includes the option to manually enter a Snaplex name. Configure retry logic for child Pipeline executions. You can now configure retry logic for child Pipeline executions though the following fields: Number of Retries, Retry Interval, and Timeout fields.
4.19	snaprsmrc528	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.18 Patch	flow7743	-	Latest	Added a property Validate full JSON path to the Data Validator Snap to fix an issue wherein a field validation failure against a constraint does not produce an error.
4.18	snapsmrc523	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.17 Patch	flow7637	-	Latest	Fixed an issue with the Data Validator Snap wherein the output fails to report all but one of the violations when there are multiple constraints of the Required type.
4.17 Patch	ALL7402	-	Latest	Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.
4.17	snapsmrc515	-	Latest	Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box.
4.16	snapsmrc508	-	Latest	Pipeline Execute Snap: Added the capability to select either document (previously supported) or binary data (new) for your input and output Views.
4.15 Patch	flow6263	-	Latest	Improved the error messages to include the source path of the constraint for data validation failures.
4.15	snapsmrc500	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.14	snapsmrc490	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.13	snapsmrc486	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.12 Patch	flow4895	-	Latest	Fixed an issue in the Data Validator Snap that made multiple copies of lineage on the error path.
4.12	snapsmrc480	-	Stable	Resolved an issue with the Union Snap that caused excessive CPU utilization.
4.11 Patch	flow4461	-	Latest	Fixed an issue with the Pipeline Execute Snap that could cause the parent pipeline to freeze when the child pipeline fails.
4.11 Patch	flow4292	-	Latest	Resolved an issue with the Union Snap in Ultra Mode that spikes the CPU utilization to ~30% during startup of 120 instances.
4.11	snapsmrc465	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.10	snapsmrc414	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.9.0 Patch	flow3094	-	Latest	Addressed an issue in Binary Router where the Snap did not wait until all threads were completed to write data to the output views.
4.9.0 Patch	flow3320	-	Latest	Data Validator Snap - fixed Type constraint feature.
4.9	snapsmrc405	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.8.0	snapsmrc398		Stable	Filter: Snap-aware error handling policy enabled for Spark mode. This ensures the error handling specified on the Snap is used.
4.7.0 Patch	flow2598		Latest	Addressed a possible race condition when reusing pipelines with a Pipeline Execute Snap.
4.7.0	flow2297		Stable	Fixed an issue with Ultra pipeline when invoking, using Pipeline Execute, a child pipeline that contains a non-Ultra compatible Snap.
4.7.0	snapsmrc382		Stable	Recommendation: The Pipeline Execute Snap is meant to eventually replace ForEach and Task Execute. It is suggested you use Pipeline Execute for all new pipelines and update existing pipelines at your earliest convenience. Updated the Pipeline Execute Snap with Execute during preview field.
4.6.0 Patch	flow1909		Latest	Resolved an issue with Union Snap slowing down pipelines.
4.6.0	snapsmrc362		Stable	The following Snaps now support error view in Spark mode: Copy, Union. ForEach: The value for the Maximum instances property is limited to a maximum of 100. A value higher than 100 will automatically be limited down to 100 during pipeline execution. Pipeline Execute: Snaplex property added to let you specify the Snaplex on which to run the child pipeline. Resolved an issue in Task Execute Snap that caused an internal server error (status code: 500). Resolved an issue in Pipeline Execute Snap that did not show parameter suggestions when the pipeline is selected from another project. Resolved an issue in Copy Snap that showed errors on the UI while the Javascript was being executed. Resolved an issue in Filter Snap that failed with "could not filter the document" if upstream data for ServiceNow Query.
4.5.1	flow1574		Latest	Resolved an issue with Pipeline Execute not able to load pipeline selected from the pipeline picker property. Enhanced error handling in Pipeline Execute for when Reuse is enabled and the pipeline path is an expression whose result is not constant. Resolved an issue in Pipeline Execute not including the runtime ID and state in error documents.
4.5.0	snapsmrc344		Stable	NEW! Pipeline Execute introduced in this release. This Snap provides a way to flexibly and efficiently execute pipelines and flowing documents into and out of these executions. Resolved an issue in Task Execute Snap to ensure JAVA 7 and JAVA 8 Snaplex give the same output. Resolved an issue with the Router Snap routing to the wrong output when used in Spark mode
4.4.0			Stable	Resolved an issue with Exit Snap hanging during validation if threshold is not met. Spark support added to the Copy, Filter, Router, and Union Snaps.
4.3.2			Latest	Resolved an issue with Task Execute where java.math.BigInteger cannot be cast to java.lang.String exception if input document variable was a numeric type. Resolved an issue with Task Execute failing with expression enabled. Resolved an issue with data preview not working in the ForEach Snap. Resolved an issue with Execute during Preview functionality broken in the ForEach Snap. Resolved an issue with ForEach Snap not representing the output schema correctly during preview.
4.3.1			Latest	Resolved an issue with the ForEach poll interval being inconsistent.
4.3.0			Stable	In Data Validator, the pattern option now works with partial matches. Exit Snap Error handling improved to handle messages that are non-strings. Exit Snap now supports expressions in the Exit error message property. ForEach Snap now generates output documents when run. Output documents will also be produced if a child pipeline called by the ForEach is manually stopped.
4.2.2			Latest	Resolved an issue in ForEach where a recursive pipeline in synchronous mode was unable to finish execution. Resolved an issue in Data Validator not working for partial matches.
		August 7, 2015 (2015.25/4.2.1)		NEW! Exit Snap introduced in this release. This Snap forces a pipeline to stop with a failed status if it receives more records than the user-defined threshold. Resolved error in ForEach Snap where an exposed error view triggered a pipeline failure.
		June 27, 2015 (2015.22)		The Router Snap now supports even distribution across all output views if no expressions are defined. With this change, Routes is no longer a required field.
		June 6, 2015 (2015.20)		Task Execute should have Execute on preview Directory Browser Snap did not render output data when running from "Windows" Groundplex.
		May 15, 2015		ForEach: Error was not thrown on validation if the child pipeline was not provided.
		May 2, 2015		Binary Router: enhanced error handling Filter: bug fixes Router: bug fixes
		December 20, 2014		Updated Snaps may include new or changed functionality or be otherwise improved. Data Validator: Type constraint added. Union Snap: Preserve order was removed.
		July/Summer 2014		NEW! Binary Router Snap introduced in this release. NEW! Task Execute Snap introduced in this release.
		June 30, 2014		Data Validator (Beta Release). This Snap validates incoming documents and their attributes against constraints you define. ForEach: Addressed an issue with parallel execution not working properly.
		April 2014		ForEach Snap updated to support Snaplex selection and pipeline parameters.
		January 2014		NEW! ForEach Snap introduced in this release.
		November 2013		NEW! Head Snap introduced in this release. NEW! Tail Snap introduced in this release.
		Initial Release (June 2013)		Router Snap introduced in this release. Copy Snap introduced in this release. Union Snap introduced in this release. Filter Snap introduced in this release.