Element <condition>

Purpose: is a pure branch container and takes no attributes of its own.

Why: Use it to group one if branch, optional else-if branches, and an optional fallback branch.

Example

<condition/>

Decision guide

Business value: Groups an ordered, mutually exclusive branch decision as one reviewable workflow block.

• Use when

  • Several child elements belong to if, else-if, and fallback branches.

• Choose another approach when

  • One conditional assignment or validation expresses the requirement more directly.

• Prerequisites

  • Start with if, follow with zero or more else-if branches, and place else last.

• Alternatives

  • Use mapping for a single ordered transformation rule. (See: <mapping>)

Complete examples

Assemble nested objects, conditional lists, arrays, and branches

Use this shape when one deterministic product combines nested records, heterogeneous list entries, literal arrays, and mutually exclusive fields.

<setup rngSeed="42" numProcess="1">
    <generate name="profiles" count="3" target="LogExporter">
        <key name="id" generator="IncrementGenerator"/>
        <nestedKey name="address" type="dict">
            <key name="city" constant="Berlin"/>
            <key name="postal_code" constant="10115"/>
        </nestedKey>
        <list name="contacts" converter="RemoveNoneOrEmptyElement">
            <item>
                <key name="channel" constant="email"/>
                <key name="value" script="'customer-' + str(id) + '@example.test'"/>
            </item>
            <item condition="id % 2 == 0">
                <key name="channel" constant="sms"/>
                <key name="value" script="'+49-30-' + str(100000 + id)"/>
            </item>
        </list>
        <array name="roles" type="literal">
            <value constant="customer"/>
            <value constant="newsletter"/>
        </array>
        <condition>
            <if condition="id == 1">
                <key name="segment" constant="new"/>
            </if>
            <else-if condition="id == 2">
                <key name="segment" constant="active"/>
            </else-if>
            <else>
                <key name="segment" constant="loyal"/>
            </else>
        </condition>
    </generate>
</setup>

Rules and invalid combinations

I501 — Condition Duplicate If

Fail while parsing . Only one tag is allowed in .

Why: A block contains more than one first branch, so branch order is ambiguous.

Resolution: Keep exactly one as the first child; add further conditions as children.

Full rule

I502 — Condition If Missing

Fail while parsing . Must have as the first tag.

Why: A block has no initial branch to establish the first decision.

Resolution: Add exactly one as the first child.

Full rule

I503 — Condition Else After

Fail while parsing . Tag must be the last tag.

Why: An branch is followed by another branch, but is the unconditional final fallback.

Resolution: Move after every and branch.

Full rule

I504 — Condition Else Duplicate

Fail while parsing . There can only be one tag at most.

Why: A block contains more than one unconditional fallback branch.

Resolution: Keep at most one , after all and branches.

Full rule

I505 — Condition Invalid Tag

Invalid tag {tag} in .

Why: The branch container accepts only , , and optional final children.

Resolution: Replace <{tag}> with a supported branch element or move it inside an existing branch.

Full rule

Allowed parents / Allowed children

Allowed parents: else, else-if, generate, if, iterate, nestedKey, while

Allowed children:

else, else-if, if

Related concepts and use cases

• Structured Data and Rule Pipelines — Shows how composite output shapes and the ordered source-filter, mapping, and target-filter pipeline work together without hiding phase boundaries.

Attributes

Show all 0 attributes

None