Developer Workflow Guide

10.2.2
- 10.5.6
- 10.5.3
- 10.5.2
- 10.5
- 10.4.1
- 10.4.0
- 10.2.1

Back Next

Sequence Flows

A sequence flow connects workflow objects to specify the order that the Data Integration Service runs the objects. The editor displays sequence flows as arrows. You can create conditional sequence flows to determine whether the Data Integration Service runs the next object.

You cannot use sequence flows to create loops. Each sequence flow can run one time.

The number of incoming and outgoing sequence flows that an object can have depends on the object type:

Events: A Start event must have a single outgoing sequence flow. An End event must have a single incoming sequence flow.
Tasks: Tasks must have a single incoming sequence flow and a single outgoing sequence flow.
Gateways: Gateways must have either multiple incoming sequence flows or multiple outgoing sequence flows, but not both. Use multiple outgoing sequence flows from a gateway to split a workflow. Use multiple incoming sequence flows to a gateway to merge multiple branches into a single flow.

When you connect objects, the Developer tool gives the sequence flow a default name. The Developer tool names sequence flows using the following format:

If you create a conditional sequence flow, you might want to rename the sequence flow to indicate the conditional expression. For example, if a conditional sequence flow from a Mapping task to a Command task includes a condition that checks if the Mapping task ran successfully, you might want to rename the sequence flow to MappingSucceeded. You can rename and add a description to a sequence flow in the sequence flow general properties.

Workflows

Conditional Sequence Flows

Parameters and Variables in Conditional Sequence Flows

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal