v26.05: Working with Node Settings
The Settings section appears on every workflow node except the Start node. It gives workflow designers explicit control over node execution order, decoupling logical sequencing from data flow.
Before v26.05, the Precedent Nodes concept was documented inline on each node type and Subsequent Nodes was available only on Write nodes. As of v26.05, both lists are part of a standardized Settings section available across all node categories — Transform, Read, Write, and Rule Set.
The Settings section exposes two lists:
Precedent Nodes — the nodes that must execute before this one. Auto-populated from the node's data input connections (read-only entries) and extendable with logical-only precedents for sequencing.
Subsequent Nodes — read-only. Auto-derived from the logical precedent chain: any node that names this node in its Precedent list appears here.
Configuring Precedent Nodes
To configure precedent nodes:
Select the node on the canvas. The configuration side panel opens.
Expand the Settings section.
To add a logical precedent, select the + button under Precedent Nodes and choose a node from the dropdown.
To remove a precedent, select the X icon beside the node name. Data-input precedents are read-only and cannot be removed from the Settings section — remove them through the node's Input section.
Select Publish to apply the configuration.
Canvas arrows update on publish to reflect the configured logical precedent.
Cycle Detection
The system blocks any selection that would create a circular dependency.
Cycle detection covers:
Self-reference — a node cannot be its own precedent.
Direct cycles — node A → node B → node A.
Indirect cycles — node A → node B → node C → node A.
Cross-type cycles — circular dependencies that span multiple node categories.
If a selection would create a cycle, the system displays a validation warning and the connection is not applied.
Start Node Management for Read and Data Action Nodes
For Read and Data Action nodes, the Start node behaves as the default precedent when no other precedent is configured. As of v26.05, the Start node can be removed from the precedent list once another precedent is selected, and added back later if needed.
To remove the Start node as precedent:
Add another node as a precedent under Precedent Nodes.
Select the X icon beside the Start entry to remove it.
Select Publish.
To add the Start node back as precedent:
Select the + button under Precedent Nodes.
Choose Start from the dropdown.
Select Publish.
Note: Every node must retain at least one precedent at all times. The system prevents removal of the last remaining precedent — whether it is the Start node or any other node.
Renaming and Deleting Referenced Nodes
When a node referenced in another node's Precedent or Subsequent list is renamed, the reference updates automatically. When a referenced node is deleted, it is removed from all Precedent and Subsequent lists across the workflow.