Skip to content

Transformations

Transformations inside workflows run as service_call steps against the Transformers capability provider. There are no first-class xslt / xml2json / json2xml / liquid / csv step types.

Capabilities

Capability Path
transformers.apply_xslt /applyXSLT
transformers.xml2json /xml2json
transformers.json2xml /json2xml
transformers.apply_liquid /applyLiquid
transformers.csv_to_json /csv2json
transformers.json_to_csv /json2csv
transformers.xml_to_csv /xml2csv
transformers.csv_to_xml /csv2xml
transformers.flatfile_to_xml /flatfile2xml
transformers.xml_to_flatfile /xml2flatfile
transformers.validate_json_schema /validateJsonSchema
transformers.validate_xsd /validateXsd

Reference demos

flows/workflows/transform_testing_demo.yaml — artifact-driven XSLT 3.0 chain via service_call.

flows/workflows/csv_transform_demo.yaml — CSV → JSON records (and round-trip to CSV). Quote fields that contain the delimiter ("meshflows:runs" when delimiter is :). First row is the header unless has_header: false.

flows/workflows/xml_csv_demo.yaml — native XML ↔ CSV (transformers.xml_to_csv / csv_to_xml).

flows/workflows/flatfile_demo.yaml — BizTalk Flat File Schema Wizard XSD (order-flatfile.xsd, tags HDR; / DTL; / FTR;) ↔ nested Order XML. JSON layout is the MeshFlows equivalent. POC, not a full FFDASM.

flows/workflows/json_schema_validate_demo.yaml — JSON Schema artifact; valid payload succeeds, invalid fails with path/message.

flows/workflows/xsd_validate_demo.yaml — XSD artifact; valid XML succeeds, invalid fails with element/path and message.

flows/workflows/soap_http_xslt_demo.yaml — SOAP 1.1 as HTTP + XSLT wrap/unwrap (no WSDL). See SOAP over HTTP + XSLT.

Example pattern:

- id: to_json
  type: service_call
  capability_name: transformers.xml2json
  capability_version: "^1.0"
  path: /xml2json
  payload_from: initial

Common Patterns

  • XML input to canonical JSON.
  • JSON input to XML for legacy system integration.
  • CSV text to JSON records (quote fields that contain the delimiter).
  • XML ↔ CSV via transformers.xml_to_csv / csv_to_xml (designer: XML → CSV / CSV → XML).
  • XSLT mapping from source schema to target schema.
  • SOAP 1.1 envelope wrap/unwrap (see SOAP over HTTP + XSLT).
  • JSON Schema validation of a payload against a workflow artifact.

Design Guidance

  • Keep mapping logic deterministic.
  • Version transformation artifacts with workflow changes.
  • Prefer small, composable transformations over monolithic mappings.
  • Prefer payload_file / artifact refs for large stylesheets (see transform demo).

Diagnostics

  • Capture transformation outputs in traces where safe.
  • Validate sample payloads before production rollout.