Skip to main content

Design and run Flows

Flows coordinate the data, processing steps and trigger for an integration workload. This section is for implementers who design Flows and operators who run or investigate them.

Choose a path

Design the workload

A Flow has three main configuration areas:

  1. Data supplies DB or File Definitions and runtime values to the Flow.
  2. Action Steps contains the ordered work, such as Maps, Reports, scripts, outbound Transports, file routing, commands, SQL and sub-Flows.
  3. Execution selects how the Flow starts and controls logging, notifications and other execution policy.

Start with Flow concepts, then use Configure Flow data items and Configure Flow steps as the detailed design guides.

Verify before automation

Use Run and test a Flow manually with sanitised data in the test configuration. A Test Run is not a universal transaction rollback or sandbox: confirm the side effects of every step and external system before execution.

After the Flow behaves correctly, configure its trigger and review Flow properties and execution policy. Scheduled and monitored execution depend on VeloxService and the permissions of its service account.

Operate and extend Flows

Keep each Flow focused on one observable business outcome. Reuse Definitions, Maps, Reports and Transports rather than copying their configuration into several Flows.