Mapping: Execute
Execute configured mapping against given file or JSON.
Parameters
Which mapping to use & which revision to use (ex: draft)
Threshold required for the mapping run to be considered successful — runs below the threshold mark the workflow step as failed:
- Partial: not all mapped elements must succeed
- Complete: all mapped elements must succeed
- At least 50%: must succeed
- At least 75%: must succeed
When on, per-node execution stats are persisted alongside the tracker so you can audit what the mapping did.
Only shown when the mapping writes through the XLSX line writer. When
on, the mapping output is written into a provided template XLSX file
instead of a fresh workbook, preserving formulas and formatting — and an
optional Template file input connector is added to the node.
Read-only list of the external parameters the selected mapping accepts on top of its input file (label and expected type). Each one generates an input connector on the node to inject the value at execution time.
Input
The data the mapping runs on. Accepts a File, multiple Files, a JSON value or multiple JSON values (JSON inputs are serialized to files before execution). The connector label follows the reader type of the selected mapping.
One connector per injected parameter declared by the mapping, typed according to the parameter's expected type: String, Number or JSON.
Only present when Use a template file is on: the XLSX file the mapping
output is written into.
Output
File generated by the mapping. The connector label follows the writer type of the selected mapping.
Number of elements processed by the mapping (Integer).
Number of elements successfully mapped (Integer).
Number of elements that failed to map (Integer).
Number of elements skipped by the mapping (Integer).