Element <templates>

Purpose: Container for reusable AMA template definitions.

Why: Use it to group reusable AMA template declarations.

Example

<templates/>

Decision guide

Business value: Makes the output-to-template mapping explicit and reviewable.

• Use when

  • Several outputs select templates declared in the same AMA block.

• Choose another approach when

  • A legacy descriptor intentionally declares its sole template directly.

• Prerequisites

  • Give every template a unique id.

Complete examples

Render profiled EDIFACT output and package its artifacts

Use the AMA family when partner-specific EDIFACT separators, templates, output names, side artifacts, and archive packaging must be modeled together.

UNH+__message_id__+ORDERS:D:96A:UN'

<setup rngSeed="42">
    <ama-generate defaultEdifactProfileRef="unoc3" variablePrefix="__" variableSuffix="__">
        <edifactProfiles>
            <profile id="unoc3" decimal="." data="+" comp=":" release="?" term="'"/>
        </edifactProfiles>
        <templates>
            <template id="order_template"
                      path="templates/order.template.edi"
                      edifactProfileRef="unoc3"
                      sourceScripted="True"/>
        </templates>
        <variable name="message_id" generator="IncrementGenerator"/>
        <output type="ORDERS" templateRef="order_template" filename="ORDERS___message_id__"/>
        <artifact type="edi_outputs" folder="edi"/>
        <artifact type="edifact_trace_csv" filename="ORDERS___message_id___trace.csv"/>
        <package type="zip" filename="ORDERS___message_id__.zip"/>
    </ama-generate>
</setup>

Rules and invalid combinations

No additional element-specific rules. Required attributes, types, and supported values are shown below.

Allowed parents / Allowed children

Allowed parents: ama-generate, else, else-if, if, while

Allowed children:

template

Attributes

Show all 0 attributes

None