Forum Discussion
I don't have a child pipeline (and I don't want one). I think the Pipeline Execute Snap only works if I was calling a child pipeline, Correct? - > Yes. You can set the pipeline to invoke itself with the Pipeline Execute Snap(and set the needed parameters), but its not an ideal solution 😄
And yes, I don't think that you can set the pipeline parameters without passing it from the parent process or external REST call.
Looking at your case, I guess your pipeline is exposed as a REST endpoint, so either:
- you can pass the InvoiceID, EmployeeID as a query parameters while calling the pipeline
- or store the parameters in a file(SLDB or any other external file locations), database table, SnapLogic Tables etc.
Thanks for your responses. You have confirmed my suspicions. It does seem a gap that SnapLogic is unable to provide business metric audit capability without not insignificant customisations.
- pramisetti6 years agoNew Contributor II
Hello,
My suggestion rather than using tail snap use Group By N snap and keep the Group Size as 0. It will wait for all the documents which are processing in first pipeline and then you can map your object after Group By N something like $group.Date etc… and call the second process. I also use the Tail Snap to control the flow of the execution. Please share the setting of the second Pipeline Execute Snap. Do you have the “reuse” on? If so, the pipeline will start as soon as the main pipeline starts, but if the “reuse” is off, it should start when there is an input document getting into the Snap.