YOU ARE DOWNLOADING DOCUMENT

Please tick the box to continue:

Transcript
Page 1: SnapLogic Best Practices: Sub Pipelines and Guaranteed Delivery

SnapLogic Best Practices:Tips and Tricks in 30 Minutes

Praneal NarayanRich Dill

Page 2: SnapLogic Best Practices: Sub Pipelines and Guaranteed Delivery

2

Agenda

Today’s Topic: Nested Pipelines– What is a nested or sub-pipeline?

– Why use them?

– Creating and using them

– Pipeline examples

ForEach Snap– What is the ForEach Snap?

– What can I use it for?

– How is it different from the Task Execute Snap?

– Pipeline example

Page 3: SnapLogic Best Practices: Sub Pipelines and Guaranteed Delivery

3

Before We Get Started…..

Documentation

Download the following:– Snaplex

– JSDK

– Snap Packs

– Mac, Linux and Windows Installers

Community Board and Ideas

Don’t forget to use our Developer Community

developer.snaplogic.com

Page 4: SnapLogic Best Practices: Sub Pipelines and Guaranteed Delivery

4

Nested Pipelines

Provide reusability– A pipeline can be as simple as one Snap or many

– A pipeline can be made up a multiple levels of nested pipelines

Support for guaranteed delivery

Page 5: SnapLogic Best Practices: Sub Pipelines and Guaranteed Delivery

5

ForEach Snap

Provides the ability to invoke a new pipeline for each incoming document

Page 6: SnapLogic Best Practices: Sub Pipelines and Guaranteed Delivery

6

A Few Tips

Add GD to the name (or notes) of a Nested pipeline when used for guaranteed delivery

Use functional descriptive names

When building ForEach pipelines, name them 1 of 2, 2 of 2, etc.

Use database tables or JSON documents to control the execution

Page 7: SnapLogic Best Practices: Sub Pipelines and Guaranteed Delivery

7

Connecting with the SnapLogic Team

@SnapLogic

Facebook/SnapLogic

developer.snaplogic.com

www.snaplogic.com/techtalk


Related Documents