Forum Discussion
You should use the Pipeline Execute and strive to replace the nested pipeline snap. You would never have to worry about it.
I am interested to learn why you went that route.
Agreed on your note of enhancement.
The reason we went that route was because re-usable components (ie. nested pipelines which was originally called sub-pipelines) was a bullet point in the SnapLogic sales pitch 3.5 years ago 🙂. Neither the Task Execute nor the Pipeline Execute were available when we were developing our first pipelines, and we never adapted to the new features since the previous became our standard and easy to use. It’s quicker/easier to drag-and-drop a highly-reused nested pipeline with pre-filled parameters, and fill in the few variable parameters, rather than wait for the Pipeline Execute to pull the suggest options, select one of the available pipeline choices, and then specify and fill in all the required parameters.
Related Content
- 3 months ago
- 6 months ago
- 4 years ago
- 10 months ago