Purpose
One process can serve several entry points. This block routes its table according to the launch context: for example, show a form to a Workspace user while processing inbound API data without a manual step.
Inputs and outputs
One input and three outputs: manual — “Run process button”, api — “API call”, workspace — “Workspace button”. Only the current launch method’s output is active. Others carry an inactive-branch signal with the same schema. An unconnected active output ends that branch.
Other methods and simulation
other handles schedules, events, calls by another flow and UBC Analytics buttons: manual/api/workspace or stop, default manual. simulation selects the branch for validation, simulation and designer preview: manual/api/workspace, default manual. Calling a REST source does not change the launch method to api; that branch represents inbound API delivery context.
Setup sequence
- Place the block before the parts that differ.
- Connect the required outputs to a form, processing or message.
- Define behavior for other launch methods.
- Select each used branch in the simulation setting in turn.
- Verify a controlled run from each entry point and publish the agreed process.
Rejoining branches
Use “Merge branches” after alternatives when execution must continue from the completed alternative. An inactive branch differs from an active empty table. Background branches need complete parameters and accessible sources; routing does not create files or form values.
Reusable loading example
The Workspace branch asks for a period and displays a data review. The API branch validates the delivered payload. Both lead to controlled writing. Give a schedule an explicit route with default parameters, or choose stop when the process is intended only for a person and API.