Skip to main content

Usage of Sub Flow Objects (Start, Call, End)

Explains the usage and logic of Sub Flow objects including Start, Call, and End components in the workflow design.

Using Sub Flow Objects

The Sub Flow components (SubFlowStart, SubFlowCall, and SubFlowEnd) are used to modularize workflow logic by allowing one flow to call another flow and return results. This setup supports reuse, encapsulation, and clearer design.

Components Overview​

1. SubFlowStart​

This object marks the beginning of a sub-flow. When a main flow calls a sub-flow using SubFlowCall, execution starts from this object.

2. SubFlowCall​

This is the main object responsible for triggering another flow from within the current workflow. In the Properties tab, it has the following fields:

  • Sub flow: The actual sub-flow to be executed is selected here. The sub-flow must begin with a SubFlowStart.
  • Result: This dropdown reflects return values defined in the sub-flow's SubFlowEnd object. The selected result is what will be returned once the sub-flow completes.

Once a sub-flow is selected, execution will continue into that flow. The flow executes independently and eventually returns to the calling flow upon reaching the SubFlowEnd.

3. SubFlowEnd​

This object ends the sub-flow. It can optionally define a return value, such as a label or outcome, which is returned to the main flow.

The value specified here will appear in the Result dropdown of the SubFlowCall object, enabling conditional flow continuation in the parent process.

Example Flow​

  1. The main flow uses a SubFlowCall object and selects a sub-flow from the list.
  2. The selected sub-flow starts from SubFlowStart and processes independently.
  3. At the end of the sub-flow, the SubFlowEnd object returns a defined result.
  4. The main flow receives this result and continues execution accordingly.

Flowchart Logic​

(Main Flow ↓ SubFlowCall ↓ → [SubFlowStart] → [SubFlow Logic] → [SubFlowEnd (with Return Value)] ↓ (Back from SubFlowEnd with Result) Continue)

Notes​

  • You must always begin a sub-flow with a SubFlowStart and end it with a SubFlowEnd for return value support.
  • Result values are configured in the sub-flow's end node and determine how control returns to the main flow.
  • This design improves readability and reusability by isolating logical units in separate flows.

Screenshot​

Sub Flow Call Property Panel