Skip to content
Back to

Operation Node

Overview

Section titled “Overview”
  • Transformations – Modify field values (e.g. uppercase, number, template)
  • Validations – Check values and optionally reject rows (e.g. required, lessThan)

Operations are executed in order. Each operation can have a source field and target field.

Step output ports

Section titled “Step output ports”

On Operation and Filter hosts, you can toggle gets output port(s) on a top-level stack step (plug control on the operation badge). That adds teal canvas output ports beside the matching stack step so you can wire intermediate results, or IF/SWITCH branch row sets, to other nodes. The host output port (emerald) still carries every row after the full stack.

When at least one step siphon is exposed, host output sits one pitch below the last siphon (with the same pitch of clearance to the node bottom), IF/SWITCH badges grow to cover every stacked siphon, and a light through-stack path shows how rows flow. Collapsed IF/SWITCH rows show each siphon’s case next to its port (case Field='value', default, or true / false), right-aligned with the op labels above, instead of the one-line switch summary. When you expose no step ports, the node keeps the classic layout: centered input and output, no exe path, no extra band under the stack.

Hover a port on the graph to see its kind, label, id, and a row preview; click the port to pin the preview until you dismiss it. Output ports show that preview whether or not you wire them downstream. After a run, empty SWITCH/IF siphons show zero rows in the grid. Explore demo: Operation Step Output Ports (stamp/lane stacks wire from host output; siphons stay on enrich intermediates and SWITCH branches).

Configuration

Section titled “Configuration”

See Workflow schema for the full schema. The operation node uses:

{
  "custom": {
    "execution": {
      "operations": [
        {
          "type": "transformation",
          "action": "uppercase",
          "params": {}
        }
      ]
    }
  }
}

On error

Section titled “On error”

Each operation can set On error: raise error (run audit error) or raise exception (persisted workflow exception). See Exception management.

Section titled “Related”