TRANSLATOR-WORKFLOW

Translator workflow. The chain of mappings and transformations an EDI Translator orchestrates to route a message end-to-end.

Definition

A translator workflow is the sequential or parallel orchestration of EDI transformation steps within an EDI Translator or B2B gateway. The workflow decomposes a business use case into elementary steps: inbound payload parsing, syntactic validation, mapping to the intermediate format, business-rule application, mapping to the target format, signing, archiving, emission. Every step is implemented by a typed component (parser, validator, mapper, signer).

Origin

The workflow concept in the EDI context comes from early Sterling Gentran tools (1983) then IBM Sterling B2B Integrator (2010 after acquisition), which structured the transformation chain into configurable sub-processes. Today, modern tools like Boomi, MuleSoft B2B and Workato expose their translator workflows as visual graphs with drag-and-drop steps, conditional branches, and transactional compensations.

Example in context

An X12 ORDERS → EDIFACT EANCOM INVOIC translator workflow typically chains: (1) raw X12 850 parsing, (2) X12 syntactic validation, (3) mapping to internal canonical model (e.g. OAGIS ProcessPurchaseOrder), (4) enrichment with supplier data from the ERP, (5) EANCOM INVOIC generation, (6) EANCOM MIG Schematron validation, (7) S/MIME signing, (8) evidence-grade archiving, (9) AS2 emission. Each step is observable (Trace ID), idempotent (look-back window), and replayable on failure.

Related terms

• EDI Translator — the component executing the translator workflow.
• Integration broker — generic concept that encompasses translator workflow.
• Mapping — elementary step of a translator workflow.