Flowchart Activity

Purpose: A flowchart is a collection of activities and connections between them. This is the root container activity for flowchart-based workflows, allowing you to create complex workflows with multiple paths and connections.

Input Properties

This activity has no input properties. It contains child activities and connections that define the workflow flow.

Output Properties

This activity has no output properties.

Port Properties

Start

The activity to execute when the flowchart starts. This is the entry point of the flowchart.

Type: IActivity

Note: Typically a Start activity, but can be any activity. This activity is executed first when the flowchart runs.

Child Activities and Connections

Activities

The collection of activities in the flowchart.

Type: ICollection<IActivity>

Note: Add all activities that will be part of the flowchart workflow.

Connections

A list of connections between activities. Connections define the flow from one activity to another.

Type: ICollection<Connection>

Note: Define connections between activities to create the workflow flow. Connections can specify outcomes and conditions.

Usage Example

Scenario: Create a simple flowchart workflow

Configuration:
- Start: Connect to Start activity
- Activities: Add Start, WriteLine, If, End activities
- Connections:
  - Start → WriteLine
  - WriteLine → If
  - If (True) → End
  - If (False) → End

Result:
- Flowchart executes starting from the Start activity
- Activities execute based on connections
- Flowchart completes when End activity is reached

Important Notes

  • Flowchart is the root container for flowchart-based workflows
  • Activities are connected using Connections that define the flow
  • The Start activity marks the entry point
  • Flowcharts support complex branching and looping through connections
  • Use End activities to mark completion points
  • Connections can specify outcomes for conditional branching
  • Flowcharts use token-based or counter-based flow control (configurable)
  • For sequential execution, consider Sequence activity instead

Related Activities