Skip to content

Managing templates

At a glance

  • Every template gets a menu (hover the "..." next to it) with Configure, Duplicate, and Delete.
  • Categories organize your template list — create one, rename it, or delete it (only if it's empty first).
  • A brand new organization gets a "default" category automatically; you can't create another one with that name.

Beyond creating a template during setup, the template list has its own management options — for organizing, reusing, and cleaning up templates over time.

Managing a template

Hover over a template in the list and open its "..." menu:

OptionEffect
ConfigureEdit the template's own settings (name, input source, category, priority, description) without touching its mapping.
DuplicateCreate a copy of the template, prompting you through the same settings as creating a new one, prefilled from the original. Use this to branch off a variant of an existing template rather than starting from nothing.
DeleteRemove the template entirely. This can't be undone.

The "..." menu open next to a template row, showing Configure, Duplicate, and Delete Template options

The Configure Template dialog

Configure (and Duplicate, which reuses the same form prefilled from the original) opens a dialog with:

FieldTypeDescriptionRequired
NameTextTemplate name.Yes
Input SourceRadio (File / Email / Http)The runtime source the deployed template reads its input document from, separate from the file you upload during setup to build the mapping against.Yes
CategorySame field set at creation; see setup.Yes
PrioritySame field set at creation; see setup.Yes
DescriptionFree textOptional notes about the template.No

File and Email add no further fields. Http reveals an Edi Options radio (Post, Get, or Token) and, depending on which is selected, one or more credential fields the runtime injects as schema variables:

Edi Options valueFields
PostUser (text) and Password (masked). Both required.
GetSame User and Password fields as Post. A third value — an OAuth token, base64-encoded from User and Password — is generated automatically; it isn't a field you fill in yourself.
TokenUser, Password (plain, unmasked text here rather than a password field), and Endpoint (text, the URL to authenticate against). All three required.

Switching Input Source away from Http clears whichever Edi Options selection and credential values were entered; they aren't preserved if you switch back.

Configure Template dialog with Input Source set to Http, Edi Options set to Token, and User, Password, and Endpoint fields visible

Categories

Categories group templates in the list — see Choosing a domain and template for how the accordion that groups them actually behaves (one category open at a time, default open by default, no separate filter control).

  • Creating one — use the category control above the template list, give it a name, and confirm. Every organization starts with a "default" category that already exists — you can't create a second category named "default." The Create button stays disabled while the name field is empty or matches an existing category's name (checked live as you type, with an inline "Category name already exists" error) — there is no server round-trip needed to see the conflict.

    The "Add Category" popover open above the template list, with a Name field and a disabled Create button

  • Renaming one — hover a category and use its menu, choosing Rename; the category's name switches to an inline editable field right there in the list, rather than opening a separate dialog.

  • Deleting one — also from its menu, via Delete Category, but only once it's empty — move or delete every template in it first. There is no confirmation prompt on click; the delete request fires immediately, and an empty category disappears from the list right away.

Sorting and finding templates

Use the sort control (the sort icon above the list) to switch between:

Sort optionOrder
DefaultBy Priority value, lowest first.
Name A → Z / Name Z → AAlphabetical by template name, either direction.
Recently usedBy the most recent entry in the template's own usage history (the latest usedAt timestamp among its recent files), most recent first. A template with no recorded usage sorts as if it had never been used.

Categories themselves are always alphabetical by name regardless of the template sort choice, with one exception: a category named "Other" is always pushed to the very end of the list.

There's no search box for templates by name, and no way to view more than one category's templates at once — on a domain with many templates, open the category you need and use Sort within it, since that's the whole toolset for narrowing the list down.