v26.05: Working with Rule Set Nodes

Rule Set nodes execute data actions and consolidation-related operations directly as part of a workflow run. Unlike Read, Transform, and Write nodes, Rule Set nodes do not pass tabular data downstream — they update impacted components directly and produce audit log entries equivalent to running the same operation as a task.

Available Rule Set node types

v26.05: Data Action Node

The Data Action node executes any data action that is otherwise available as a task — sheet copy, currency conversion, consolidation, auto journal rules, and rule execution — directly as part of a workflow run. Workflow execution itself is excluded from the supported action list to prevent recursion.

To configure a Data Action node:

1. Click + Add Node from the Level 2 header. The Add Node dialog opens.
2. Select Rule Set from the left panel.
3. Select Data Action from the right panel. The node appears on the canvas and the configuration side panel opens.

4. Fill in the required fields from the configuration panel:

   Parameter	Description
   Name	Unique identifier. Defaults to Data Action_[n].
   Action Type	Selector for the action category (sheet copy, currency conversion, consolidation, auto journal, rule execution, and similar). Matches the Action Type options available in tasks, excluding workflow.
   Action	Specific action to execute. Only individual actions (leaf items) are selectable; folders are not.
   v26.05:  Settings (Optional)	Configure Precedent and Subsequent nodes to control node execution order. See Working with Node Settings for more details.

5. Select Publish in the Level 2 header to save the configuration.

No downstream data

The Data Action node does not pass data to downstream nodes and does not generate a preview. It executes the configured action against impacted components directly.

Audit logging

Write operations generate audit log entries identical to running the same action as a task. Audit logs are produced when the workflow is executed manually or from a task.

Member selection context

If the selected action requires member selection as context, the corresponding dimension is added to the Run dialog’s Selections popup. The Run button enforces that all required dimensions have selections before execution.

Renamed or deleted actions

If the selected action is renamed in the system, the node automatically reflects the updated name. If the selected action is deleted, the selection clears and a validation warning appears on the node — the workflow cannot be published until a valid action is selected.

Multiple Data Action nodes

A workflow can contain multiple Data Action nodes. Each is independent — its name, action type, action selection, and audit log are all node-scoped.