October 2026

This article describes the significant feature enhancements in JustPerform v26.10.

Enhancements to Transaction Table: Deletion and Table Details

Transaction tables now support deleting rows and dimensions in place, and a new Table Details page brings metric and local dimension details together.

Row deletion in the grid

Users can now delete incorrect rows directly from the grid of a transaction table or from its input snippet. The deletion is committed when the table is saved, and it is recorded in the data history. The default snippets, the input snippets, and exports contain only the rows that remain.

Dimension deletion and row merging

Users with Manager access can delete a local or global dimension that is no longer needed, and the deletion is applied when the table is published. When the table does not allow duplicate rows, the rows that become identical are merged into one row: numeric metric values are added together, and other values are cleared. A table must keep at least one global dimension, so the last global dimension cannot be deleted.

Table Details page

A new Table Details page lists the metrics and local dimensions of a transaction table on separate tabs. Users can edit the name and data type of a metric and edit a local dimension, including adding or removing the allowed values of a list dimension. Saved changes stay in sync with the table layout, import, export, the default snippets, and input snippets.

For more information, see the Transactions – Table article.

Enhancements to Workflow: Transform Mapping Node

The Mapping node now gives users more control over which rows match and clearer information about the values that cannot be mapped.

Only Match First option

A new Only Match First option on the Mapping node returns only the first matching row of the mapping table, in row order, when a source value matches more than one row. When the option is cleared, the node returns all matching rows. The option is cleared by default, so existing mappings keep their current results, and the setting applies to all steps in the node.

Skip, wildcard, and space handling

A mapping table can now use *SKIP as a target to leave the matching source values out of the output without failing the run. When the source pattern and the target value both contain a wildcard, the part of the source value that the wildcard matches replaces the wildcard in the target. Leading and trailing spaces are ignored when source values are compared with the mapping table.

Rejected record reporting

When a run stops or finishes with unmapped values, the Execution Output now lists the number of rejected records and the unmapped values by dimension, so users can identify the values that need a mapping. Values that a *SKIP row leaves out are not counted as rejected.

For more information, see the Mapping Node section in the Working with Transform Nodes article.

Enhancements to Workflow: Transform SQL Script Node

The SQL Script node now explains query problems clearly and lets users control which tables a workflow can read.

Specific error messages

Validate, Publish, and Run now report the same message for the same problem. The messages identify syntax errors, unknown nodes, columns, and parameters, and data type problems such as comparing text with a number. Each message gives the line and column of the problem in the query and uses the names of the input nodes. Guardrail messages appear when a query is too complex to run or does not finish in time, and output column messages identify duplicate names, missing aliases, and a column count that does not match the downstream Write node. A forbidden keyword inside a text value, a comment, or a quoted identifier does not block a query.

For more information, see the Resolve Query Errors section in the Working with Transform Nodes article.

Workspace table access option

A new Allow access to workspace tables option in the workflow details lets the SQL Script nodes in a workflow read tables that are not added as node inputs. The option is cleared by default, and the SQL Script nodes then read only the tables that are added as their inputs. Changing the option requires manage access to the workflow.

For more information, see the Input Validation and Security section in the Working with Transform Nodes article and the Editing Workflow Properties section in the Managing Workflows article.

Enhancements to Workflow: Node Failure Messages and Source Change Detection

Workflow nodes now name the problem when a run fails or returns less data than expected, and they flag source components that have changed since the node was published.

Node failure messages

Read, Transform, Write, and Data Action nodes now report a specific message, for example for a deleted source or target, a missing input, an empty table, or rows skipped because a member does not exist. Each message ends with the node name and Success or Failed. The Execution Output shows the message of the selected node, and the Event Log lists the messages of all nodes in execution order, so users who run a workflow from a task see the same information as users who run it from the canvas. When a data preview is limited to 1,000 rows, the message shows the number of rows displayed and the total.

Source change detection

When the sheet, transaction table, remote table, dimension, or mapping table that a Read, Write, or Mapping node uses changes after the node is published, the node now shows an exclamation mark on the canvas and Input table updated in its header. The flag does not change the node or block a run. Adding the source component again and publishing the node updates it, and the selections, layout, filters, and mappings that are still valid are kept.

For more information, see the Viewing Execution Output, Troubleshooting Errors, and Update a Node After a Source Change sections in the Managing Workflows article.

Enhancements to Workflow: Read File Reader Node

The File Reader node now lets users assign a data type to each column: Text, Integer, Number, Percentage, or Date. Text is the default, and users set the data type of each column in the side pane after they select specific columns. A value that does not fit its data type is left blank in the output, and a warning appears when a change would blank an entire column. The file that is uploaded when the workflow runs is checked against the configured data types in the same way.

For more information, see the Configuring File Reader Node section in the Working with Read Nodes article.

Enhancements to Workflow: Node Settings

Selecting and identifying nodes and columns is now clearer in the node side panel.

Display names in node lists

The Input dropdown, the Precedent Nodes dropdown, and the Precedent Nodes and Subsequent Nodes lists now show node display names. The lists update when a node is renamed, without reopening the node.

For more information, see the Configuring Precedent Nodes section in the Working with Node Settings article and the Use Display Names and Unique IDs section in the Understanding Node Categories and Types article.

Valid input nodes

Each Input dropdown now lists only the nodes that can be valid inputs for that node, such as Read, Mapping, and SQL Script nodes. The remote table selector in the Read node lists only remote tables whose data residency is not Virtual. A saved workflow that already has an invalid input opens normally, and the flagged node must be reassigned or removed before the workflow can be saved.

For more information, see the Select Valid Input Nodes section in the Understanding Node Categories and Types article and the Configuring Remote Table Node section in the Working with Read Nodes article.

Complete names on hover

Hovering over a name that is too long to display in a side panel, a dropdown, or the Execution Output now shows the complete name. Mapping dropdowns open wider, and the highlight spans the full option.

For more information, see the Use Display Names and Unique IDs section in the Understanding Node Categories and Types article.

Unique IDs for duplicate names

When columns in a node, or nodes in a workflow, share a display name, each one now gets a unique ID with a numeric suffix, for example Time and Time_1. Display names do not change, so SQL queries and downstream nodes can reference each column.

For more information, see the Use Display Names and Unique IDs section in the Understanding Node Categories and Types article.

Enhancements to Workflow: Parameters

Workflow parameters now filter members and properties in more nodes. Parameter selections take effect after the workflow is published.

Parameters in sheet and transaction table nodes

In Read Sheet and Read Transaction Table nodes, and in the Overwrite based on section of Write Sheet and Write Transaction Table nodes, the member selector now lists every workflow parameter, and users can combine parameters with fixed members. When the workflow runs, the selection includes the members that each parameter resolves to. Write nodes clear only the rows inside the resulting overwrite scope before they write.

Parameters in master data read nodes

In a Read Master Data node, each property that is not localized now has a filter icon for selecting workflow parameters. The node returns only the rows whose property value matches the members that the parameters resolve to. When more than one parameter is selected on a property, the resolved values are combined without duplicates.

For more information, see the Parameters in Sheet and Transaction Table Nodes and Parameters in Master Data Read Nodes sections in the Working with Parameters article.

Enhancements to Workflow: Audit Log

The audit log of a workflow run now lists every metric that the run affects, including the metrics that depend on a written metric at every level of the dependency chain. Each dependent metric shows the metric that triggered it, so users can trace the path of an impact. When more than one node writes to a metric, the audit log keeps the history of each write with the node name, node type, workflow, time, and user, most recent first. This applies to runs from the canvas and from tasks.

For more information, see the Review Metric Changes in the Audit Log section in the Working with Write Nodes article and the Audit logging section in the Working with Rule Set Nodes article.

Enhancements to Activity Tasks and Platform

This release completes how workflows, transaction tables, and mapping tables open from activity tasks, and it upgrades the platform services to Spring Boot 4.

Task internal links for workflows, transaction tables, and mapping tables

A task in an activity can carry an internal link to a system component, and workflows, transaction tables, and mapping tables can now be linked in the same way as sheets. Selecting the task opens the component in a new JustPerform tab, where the component fills the canvas and its level-2 headers, toolbars, and actions are available, including running a workflow. A new tab icon appears beside each task that has an internal link and opens the component in a browser tab. The user's existing permissions on the component apply.

Spring Boot 4 upgrade

The Intelligence, MCP, Core, and Agent services are upgraded to Spring Boot 4, in two parts, so that they stay on a supported framework version. Functionality is unchanged.

Enhancements to Design System 2.0

This release extends Design System 2.0 (DS 2.0), the updated visual design, to email notifications, version history pages, and empty screens. It also resolves layout, alignment, and visual issues on screens that already use DS 2.0.

Enhanced email templates in DS 2.0

Email notifications now use a DS 2.0 template that displays the logo and reflects whether your organization uses the Lineos brand. Links in the email, such as Activate profile, open DS 2.0 pages, and long links wrap within the email layout. The Lineos platform team manages account activation emails.

Enhanced version history pages in DS 2.0

Version history pages now use DS 2.0, including the grid, the pop-up dialogs, and the Refreshed and Not Refreshed status indicator. The status indicator stays in sync with the refresh state of the sheet, and the grid displays without an extra horizontal scrollbar.

Enhanced empty screens in DS 2.0

Empty screens now use DS 2.0. These are the placeholders that appear for lists, tables, dashboards, and sheets when there is no data, no search results, or nothing set up yet. Their illustrations, messages, and action buttons follow one consistent layout across the application. Functionality is unchanged.

Enhanced UI elements in DS 2.0

This release resolves layout, alignment, and visual issues on screens migrated to DS 2.0, so that screens look and behave consistently:

• Side panel and navigation: Labels, alignment, and the hover, pressed, and checkbox states in the side panel and left navigation panel display as designed. Breadcrumb separators and the navigation panel resize handle also display correctly.

• Page headers and layouts: The L2 header on the Overview page and the Activity dashboard displays with the correct layout and hover highlighting, without flicker or blank options. Chevron icons and status buttons on the Overview page use the correct design.

• Dialogs and pop-ups: The Format Metric, Rerun Metric Calculation, Member Selector, Property Selector, Add Metrics, Import, and Insert/Edit Link dialogs display completely and consistently.

• Sheets and grids: Sheets, filters, right-click menus, and data grids display without stray lines, duplicate separators, or extra spacing.

• AI chat: The design, hover states, text styles, and context menu text in AI chat are corrected.

• Messages and controls: The save confirmation message, dropdown lists, input fields, and the Update selected button display and behave as designed.

• Catalog and dashboard pages: Catalog pages follow the DS 2.0 design, and dashboard icons display correctly.

Add "File Delta" extraction mode for SFTP/S3 remote tables

Remote Tables sourced from SFTP or S3 now support a third extraction mode, File Delta, alongside the existing Full and Delta modes. File Delta automatically identifies and loads the most recent file in the configured SFTP or S3 location based on its file timestamp. Users no longer need to upload files under a fixed file name that overwrites the previous file each time a new one is generated.

Where to find it: When creating or editing a rule for a Remote Table in the Import Rules panel, the Rule mode dropdown now includes File Delta as a third option. File Delta is available only when the remote table’s source type is SFTP or S3.

Event log message when no new file is found: If no file newer than the last processed file exists at the source location, the event log records: “No new files found since the last File Delta run.”

Hide metric filter from level 2 header

Metric filters can now be toggled on or off in the level 2 header using the new Enable User Selection checkbox in the Member Selector dialog.

To access this setting: Click the filter icon next to any Metric field in Sheet Layout.

How it works:

• Checked: The Metric filter appears in the level 2 header, allowing end users to change the metric selection directly.

• Unchecked: The Metric filter is hidden from the header.

By default, this option is enabled and works across sheets and snippets.

For multi-axis and multi-section layouts: Each Metric field has its own independent Enable User Selection setting per axis or section.

Visually identify invalid members in Sheets, Snippets, and Boards

The web UI now highlights invalid members in-place in addition to a generic "Invalid member inserted" message, matching the Excel Add-in’s behavior, instead of silently removing them. When users insert invalid members, affected cells are instantly highlighted using a configured style, making it easy to spot and correct issues without disrupting their workflow.

Configurable "Invalid Member" style

Users can define a custom "Invalid Member" style in the style settings, specifying color and formatting to apply across Sheets, Snippets, and Boards. The system applies this style to invalid entries without requiring a page refresh.

Key behaviors

• Invalid members are highlighted individually using the configured style.

• Valid members in the same operation are saved successfully.

• Multiple invalid entries are flagged and highlighted simultaneously.

• If no custom style is configured, the system displays the generic "Invalid member inserted" message as before.

Distinguish zero-value from blank cells in sheets and snippets

The Consider Zero as Data option lets users clearly distinguish intentional zero entries from blank cells in Sheets and Snippets (Input, Report, OData, and Control types). This gives users explicit control over how zero values are displayed.

How it works:

• Enabling or disabling the option takes effect only when you publish the Sheet or Snippet.

• When enabled and published, entering 0 in a cell displays as 0 rather than appearing blank.

• When disabled, cells containing 0 appear blank (default behavior).

• The setting applies independently to each Sheet and Snippet.

Excel Add-in: The checkbox is visible but read-only in the Excel Add-in.

Consolidate two log entries for remote table tasks with associated calculations

When a Remote Table task under "Calculations & Data Flow" triggers an associated Calculation as part of its execution, the system now creates a single merged log entry instead of two separate ones, allowing users to view complete execution details in one place. The entry’s identifier reflects the origin of the execution, either the triggering Process task or the Remote Table itself. The Task Event Log popup shows the same merged details for whichever scenario applies.

Triggered from the process task

When executed from the Process form/activity or via a schedule configured in Process, the Task Monitor displays one entry using the Process Task’s Event ID. The associated Remote Table's Categories, Activity, Status, timing, and other details are included in this entry rather than appearing as a separate row.

Triggered directly from the remote table

When executed directly on the Remote Table (manually or via a schedule configured on the Remote Table, outside of the Process form/activity), the Task Monitor displays one entry using the Remote Table’s Event ID. The associated Calculation's Categories, Activity, Status, timing, and other details are merged into this entry.

Star Rocks workspaces now support MTD, QTD, and HTD time series

In a Star Rocks workspace, on sheets where both "Consolidate Data in Sheet" and “Maintain as YTD Balance” are enabled, you can now select MTD, QTD, or HTD as your time series without report definition errors. The sheet loads and renders values correctly, matching the behavior of PostgreSQL-backed workspaces.

Double-click trigger for edit warning in protected journals

The "User not authorized to edit data because of data protection" warning popup in protected journals is now triggered only on double-click actions in protected fields (Description or Line Items), rather than on every single click, selection, drag selection, or header/filter interaction. Double-click is a deliberate gesture that signals intent to edit, while single-click interactions represent read-only navigation and viewing. This distinction reduces unnecessary interruptions during basic navigation and viewing while maintaining edit-protection restrictions.

Resolved Issues in October 2026