Decision Flow

Decision Flow

A decision flow is where decision logic lives and runs. It is a sequence of steps. Each step evaluates or calculates something, and the flow runs them in order, from Start to End, every time it is called.

Decision Flow Example

Understanding Decision Steps

Your decision flow consists of various types of steps, each serving a specific purpose in the decision-making process:

Business Logic Steps

Flow Control Steps

  • Start - Every flow begins here (required)
  • Fork - Split processing into parallel paths
  • Data source - Pull external data into your flow
  • Sub-flow - Execute reusable decision components
  • End - Terminate processing (optional)

Steps can be combined in any order the logic needs.

Building Your First Flow

To create a decision flow:

  1. Start Fresh: Click "Decision flows", then "Create a decision flow"
  2. Configure: The system generates a name and ID automatically
  3. Customize: Click "Decision Flow Settings", then "Options", to change the details

Create Decision Flow

Flow Configuration

The configuration modal lets you:

  • Change the flow name and unique identifier
  • Add a description for documentation
  • Enable deletion protection for critical flows

Decision Flow Options

Enable "Block deletion" on flows that are in production. A flow with deletion blocked cannot be removed until the option is turned off.

Working with Steps

Adding Logic

Double-click any step to configure its behavior. Each step type has its own configuration interface tailored to its specific function.

Connecting the Flow

Link steps by dragging from the output port of one step to the input port of another. This creates the execution path your data will follow.

Remember:

  • Most steps have one output (except Fork steps)
  • Steps can have multiple inputs
  • Every flow needs a Start step

Managing Steps

Copy and paste steps within the same flow or between different flows:

Copy Step Paste Step

When you copy a step, its configuration is copied with it.

Best Practices

Keep it Simple: Start with basic flows and add complexity gradually. A working simple flow is better than a complex broken one.

Name Everything: Give your steps descriptive names. "Credit Check" is better than "Step 1".

Document Decisions: Add descriptions to complex steps explaining the business logic.

Test Early: Validate your flows frequently during development.

Plan for Growth: Design flows that can be extended as requirements evolve.


Related Documentation: