Created by @dwhite
A sample pattern one could use to trigger a large data orchestration process with several steps (synchronous and parallel) that has an asynchronous response at the start so the calling process will not wait. Response contains a SnapLogic Ruuid so one could call back later to check on status or log.
Insert you child data warehousing process pipelines into the pipeline execute(s) as needed. Assign pipeline to a trigger task. Call from external application/process
Sources: Any child pipeline process performing data loads / gets
Snaps used: Pipeline Execute, Mapper, Copy
Asynchronous Orchestration Process.slp (16.8 KB)