A developer wants a set of activities to execute sequentially, one after another, and also wants to be able to collapse that group into a single labeled block on the designer canvas for readability. The activities share the same variables and do not require any conditional or parallel behavior. Which container should the developer use?
Trap 1: Flowchart
A Flowchart arranges activities as nodes connected by arrows and is intended for complex branching logic. For a straight-line group of activities, it adds unnecessary connectors and visual complexity. It also does not collapse into a single labeled block the way a Sequence does. Since the scenario explicitly needs no conditional behavior, a Flowchart is overkill and less readable.
Trap 2: State Machine
A State Machine models execution as named states with transitions triggered by conditions, which suits long-running, event-driven processes. A simple ordered list of activities gains nothing from states and transitions, and the developer would have to define entry and exit conditions artificially. It also cannot be collapsed into a single inline block, so it fails the readability goal while adding structure the scenario does not need.
Trap 3: Parallel
Parallel runs its branches concurrently, starting them at the same time, which is not what a strictly sequential group requires. Using it here could introduce race conditions if the activities touch shared variables or UI, and it makes execution order nondeterministic. The scenario states the activities must run one after another, so Parallel contradicts the core requirement even though it is a valid container.
- A
Sequence
A Sequence executes its children in the exact order they appear, top to bottom, and it can be collapsed on the canvas with an editable DisplayName. It supports shared variables declared in its Variables panel, so the grouped activities keep their scope. Since no branching or concurrency is needed, Sequence is the simplest container that satisfies both the execution order and the readability requirement.
- B
Flowchart
Why it fails: A Flowchart arranges activities as nodes connected by arrows and is intended for complex branching logic. For a straight-line group of activities, it adds unnecessary connectors and visual complexity. It also does not collapse into a single labeled block the way a Sequence does. Since the scenario explicitly needs no conditional behavior, a Flowchart is overkill and less readable.
- C
State Machine
Why it fails: A State Machine models execution as named states with transitions triggered by conditions, which suits long-running, event-driven processes. A simple ordered list of activities gains nothing from states and transitions, and the developer would have to define entry and exit conditions artificially. It also cannot be collapsed into a single inline block, so it fails the readability goal while adding structure the scenario does not need.
- D
Parallel
Why it fails: Parallel runs its branches concurrently, starting them at the same time, which is not what a strictly sequential group requires. Using it here could introduce race conditions if the activities touch shared variables or UI, and it makes execution order nondeterministic. The scenario states the activities must run one after another, so Parallel contradicts the core requirement even though it is a valid container.