...
Final Output: Once the stop condition is satisfied or the iteration limit is reached, the final output of the pipeline will be collected and passed to the next step or processed further based on the overall workflow.
Download this pipeline.
Next steps (if applicable):
If additional Snaps are required for processing, transformation, or routing in the child pipeline, configure those accordingly.
Examples might include:
Filter Snap to filter out unnecessary data.
Data Transformation Snaps for applying complex transformations.
HTTP Client or Database Snaps if external calls or data lookups are needed.
Return Output to Parent Pipeline:
Once the child pipeline completes its steps, it should return its output document to the parent pipeline.
This output will be used by the PipeLoop Snap in the parent pipeline to evaluate the stop condition or proceed with further iterations.
Execute the PipeLoop Snap. The parent pipeline will pass the generated JSON input to the PipeLoop Snap, which then initiates the iterative process by calling the child pipeline.
Evaluate the Output:
After each iteration, the PipeLoop Snap will evaluate the output document from the child pipeline.
The stop condition will be assessed to determine if further iterations are necessary or if the loop should end.
| Attachments |
|---|