May 2026

This article describes the significant feature enhancements in product name and version here v26.05.

Enhancements to Workflow

The following workflow features are enhanced in this release:

New Read node: File Upload

A new File Upload node is available under the Read category in Workflow. The node lets workflow designers configure a file-based data source whose actual file is supplied by users at runtime.

Create File Upload data type

Workflow designers can now add a File Upload node, name it, choose the allowed file type (CSV in this release; Excel multi-sheet planned), and select a sample file for design-time preview. The sample file is shared across all workflow users and is used only to configure the downstream File Reader node - it never executes as part of a run and is not added to the upload history.

Manage Run-Time Upload and File History

At runtime, the Run dialog displays a dedicated File Uploads section per File Upload node, with controls for Choose file, Encoding, and Delimiter. The Run button stays disabled until every File Upload node has a valid file. A Previously Uploaded Files section, scoped to the logged-in user, lists past runtime uploads in reverse chronological order for audit.

New Read node: File Reader

A new File Reader node is available under the Read category in Workflow. The File Reader pairs with a File Upload node and parses the uploaded file into a tabular dataset for downstream consumption.

The node accepts a configurable Start Cell (defining the header row and leftmost column - for example, A1) and a Column Selection option for picking specific columns from the source file. All downstream mapping is based on column position (Column A, B, C...), not header name - so renaming a header in the runtime file does not break downstream nodes. All values are read as text. Downstream nodes (Mapping, SQL, Write) handle any type conversion. One File Upload node can feed multiple independent File Reader nodes.

New Rule Set node: Data Action

A new Data Action node is available under the Rule Set category in Workflow. The node executes any data action that is otherwise available as a task - for example, 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.

The Data Action node updates impacted components directly and does not pass data downstream or generate a preview. Write operations produce audit log entries identical to running the same action as a task. Multiple Data Action nodes are supported in a single workflow, each independent.

Node Settings

The Settings section is introduced on every workflow node (except Start), providing an explicit configuration surface for execution ordering. Precedent Nodes -- previously derived implicitly from data flow connections -- are now exposed in the Settings section for explicit configuration. Subsequent Nodes, previously available only on Write nodes, are now extended to all node categories. Settings decouples logical execution sequence from data flow, giving workflow designers explicit control over node ordering.

Settings for Precedent and Subsequent nodes

Each node exposes a Precedent Nodes list (the nodes that must execute before it) and a read-only Subsequent Nodes list (auto-derived from the precedent chain). Precedents are auto-populated from data input connections and can be extended with logical-only precedents for sequencing. The system blocks selections that would create a circular loop, covering self-reference, direct, indirect, and cross-type cycles. Canvas arrows update on publish to reflect the configured logical precedent.

Settings for Read and Data Action nodes

For Read and Data Action nodes, the Start node can be removed from the precedent list when another precedent is selected, and added back later if needed. The system enforces that every node retains at least one precedent - the last remaining precedent cannot be removed. All cycle-detection and unique-edge validations remain in effect.

SFTP Remote Table Logging Enhancement

The logging for SFTP Remote Tables has been enhanced to provide detailed logs for all processed files, instead of showing only the most recently processed file along with a single aggregated count of total records.

This enhancement improves traceability, debugging, and auditability for SFTP-based data loads.

Key Benefits

Users now have file-level visibility in the logs, enabling them to:

• Track processing at the individual file level

• Monitor processing across multiple files within a batch

• Validate data load results more effectively

• Troubleshoot issues with greater accuracy

Message Box Enhancement (Final Log Summary)

When multiple files are processed, the Message Box now displays:

• The total aggregated record count across all processed files

• File-level record counts for each individual file

Scope

This enhancement applies only to:

• The final Message Box output

• SFTP-based data loads

Enhancements to Transaction Table

The following Transaction Table features are enhanced in this release:

Save data from the grid

Users can now enter, update, and save data directly from the Transaction Table grid. Previously, the only way to add data to a Transaction Table was through the Import functionality. With this enhancement, designers can type values into cells, insert rows in place (right-click > Insert row below), update existing rows, and save - without exporting and re-importing the file. All validation rules applied during import (mandatory dimensions, duplicate handling, data type enforcement) apply identically to grid entry.

User defined Input snippet

This release introduces support for user-defined Input snippets on Transaction Tables. Until now, every Transaction Table exposed only the three default snippets - Original Table, Entire Data, and History. With this release, users can create a fourth, user-defined snippet of type Input.

When Create Snippet is opened, four snippet types are listed; only Input is active in this release (the other three are reserved for future use). The Input snippet inherits the parent Transaction Table's metrics, dimensions, and Enable Duplicates setting as read-only - these stay in sync automatically when the parent table changes. Users configure the snippet's own layout (Rows and Filters), Preferences, Name, Title, and Private/Public visibility.

Once published, the snippet appears in the Snippet list under the Public or Private tab, and supports the standard snippet operations: favourite, copy, delete, and open in a new tab. Multiple Input snippets can be created on a single table, each independent.

For more information see Transactions - Table.

Align Board Summary Control Counts with Control Details

When viewing control statuses on a board and selecting the summary indicators (Valid, Error, Warning), the Control Report Details now exactly match the corresponding summary counts.

The board-level summary and its Details view are now fully aligned. This consistency is achieved by eliminating duplicate control counting at the summary level and calculating only unique control records when multiple snippets reference the same control metric with the same intersection.

Version Display for Models, Connections, Table Sets, and Remote Tables

product name and version here provides access to the latest version information for models, connections, table sets, and remote tables.

Models

The latest version of a model is available from the three-dot menu in the rule navigation header for Advanced, Virtual, and Standard Models.

The version history is updated when the following actions occur:

• Creating a model

• Deleting a model

• Updating a standard model (e.g., adding or removing dimensions, modifying information)

• Updating a virtual model (any changes)

• Updating a journal model (any changes)

• Updating an advanced model (e.g., modifying queries or other information)

Version History Search

In the Version History table, users can search records using the following fields:

• Event ID

• Object Key

• Object Name

Column Filtering

In the Version History table, each column displays a filter icon when you hover over the column header. Clicking the icon shows available values for that column. Multi-select filtering is supported.

Connections

In the Connections table, the latest version of a connection can be accessed from the three-dot menu for that connection.

Table Sets and Remote Tables

In the left resource panel, the latest version of a table set or remote table is available from the three-dot menu of the respective item.

Hide Level 2 Header When Set Range Is Enabled on Rows or Columns

Previously, when Set Range was enabled on Rows, Columns, or both in an Input or Report snippet, dimension and metric members driven by FA Context were still incorrectly appearing in the Level 2 header for that axis. The Level 2 header is now correctly suppressed for any axis where Set Range is active, only members placed in the Filter section, or on an axis where Set Range is not enabled, continue to appear at Level 2.

Additionally, any configuration change, such as toggling the Set Range checkbox or moving a dimension/metric between sections, is now reflected immediately in the live preview without requiring a Publish or manual refresh. When Set Range is disabled on an axis, that axis reverts to standard behavior and Level 2 header members display as normal. Members moved to the Filter section or to a non-Set Range axis correctly appear at Level 2 headers.

Enhanced Save Failure Message

When users enter data in a Sheet or Input Snippet with “Enable Input to Parent” turned on, they can select multiple parent members and input data across all resulting combinations. However, if the number of combinations exceeds the system limit (2,147,483,647), the save operation fails.

This feature improves the user experience by:

• Displaying a clear, centered error message when the limit is exceeded.

• Explicitly explaining that the failure is due to too many parent member combinations.

• Guiding users to take corrective action, such as reducing the number of selected parent members.

Overall, it ensures users immediately understand why the save failed instead of assuming their data was successfully saved.

Multiple Auto Mapping Rules Aggregation

When configuring multiple Auto Mapping Rules with the same output target (for example, P12000), the system previously applied the rules sequentially, causing the results of earlier rules to be overwritten by the last executed rule.

product name and version here now aggregates the results of all applicable rules, ensuring that:

• Earlier rule results are not unintentionally overwritten

• Financial outcomes are accurate, consistent, and predictable

Note: Auto Mapping rules that do not produce matching data (for example, null results or empty sources) are excluded from the aggregation.

Enhancements to Platform

The following platform-level enhancements are included in this release:

Axios library upgrade

The Axios HTTP client library is upgraded to a later version, addressing security advisories and aligning the platform with current dependency standards.

Maintenance schedule for metric tables (StarRocks)

The maintenance schedule for metric tables on StarRocks is changed from monthly to weekly to prevent performance degradation on long-running, large-data processes. The activity applies to metric tables only; dimension tables are not impacted.

Enhancements to Dimensions - Hyphen validation in Dimension Name

Validation for the Dimension Name field is enhanced to reject the hyphen character (-). When a hyphen is entered, the inline validation message "Please do not enter special characters except underscore." appears below the field, the field border is highlighted in red, and the dimension cannot be saved until the invalid character is removed. Underscore (_) remains the only allowed special character.

Resolved Issues in May 2026

The following issues are resolved in May 2026 release.