Studio Web Maestro duplicates the sequence flow label and condition when an element is added between two gateways

News Knowledge Base
1

In the Studio Web Maestro process designer, a conditional sequence flow connects two exclusive gateways and carries a name (for example With Condition) and a condition. After an element such as a task is dropped onto that connector to insert it between the two gateways, the flow is split into two segments and both segments show the same label and the same condition. Is the duplicated label and condition expected?

Issue Description

Studio Web Maestro models processes as a BPMN diagram. A sequence flow — the arrow between two shapes — can carry a name and, when it leaves an exclusive gateway, a condition that decides whether the flow takes that path.

When an element is inserted onto an existing conditional sequence flow, the designer does not create one new arrow. It splits the original flow into two sequence flows so the new element sits in the middle, and the name and condition that described the original flow are propagated to the resulting segments.

This is why the inserted segment (element › gateway 2) shows the same With Condition label and the same condition as the original gateway-to-gateway flow.

The label on a sequence flow logically describes the condition under which the process takes that path, so the label appears on the segment that continues out of the first gateway.

Symptoms

A conditional sequence flow runs between two exclusive (XOR) gateways on the Maestro canvas. Inserting an element onto that connector produces the following states:

Before adding the element

  • A single sequence flow connects gateway 1 to gateway 2.
  • The flow is named With Condition with a condition set under Properties › Conditions (e.g. 1 === 1).
  • A separate Default path connects the same two gateways.

After dropping the element

  • The connector is split into two segments: gateway 1 › element, and element › gateway 2.
  • Both segments display the same name With Condition.
  • Both segments carry the same condition 1 === 1.
  • The Default path is unchanged.

The reader perceives this as a duplicated or unwanted second condition on the inserted segment.

Resolution

This is expected behavior of the Maestro process designer, not a defect. The condition is only evaluated where it is meaningful — on the flow leaving the gateway — so the duplicated label on the downstream segment does not change how the process runs.