Product Updates - 9th March 2026 (v3.68)

This release introduces ecosystem subscription management, a new confirmation checkbox component, and date/time duration calculation support. We've also begun the first phase of upgrading the platform to .NET 10, and resolved several important issues across workflow status handling, data merging, activity execution, and the builder interface.

🪄 Feature Updates

Ecosystem Subscription Management

You can now manage subscriptions directly within the ecosystem interface. The subscription API has been enhanced to include company name information alongside a company search capability, making it easier to locate and manage subscriptions across your organisation. This lays the foundation for richer subscription management workflows going forward. (7596)

This feature is available to Ecosystem Orchestrators and is accessed via the user-profile icon in the top-right, clicking ‘Settings/Ecosystem’ and then navigating to the Subscriptions menu. Subscriptions can be assigned to one or more Companies with access to the Ecosystem and allow for granular control to be applied to which Workflows, Performance Dashboards, and Assets, that each Company can view or edit.

Date and Time Calculations Based on Duration

Workflows and dashboards can now calculate a DateTime field based on elapsed duration from another DateTime field. This makes it possible to surface time-based metrics — such as time in step or time to completion — directly within workflow steps and dashboard views, without manual calculation. (7864)

To use this in a target DateTime component, set the following in the defaultValue:

• “defaultValue”: “=shiftDateByDuration(’{<firstDateTimePath>}, ‘{<textFieldDataPathContainingShiftDetails>}’

The value to shift by can be retrieved from the text field, or hard-coded into the calculation.

Valid values in the text field are ‘# <timePeriod>’ where # is a number and <timePeriod> is one of:

• sec, secs, second, seconds
• min, mins, minute, minutes
• hr, hrs, hour, hours
• day, days
• week, weeks
• month, months
• year, years

Any other string value than those listed above will not produce the expected output in the target DateTime component.

🐞 Bug Fixes

Activity execution logic refined for system events

Activity execution logic has been updated to correctly distinguish between Submit and $Update system events. Activities configured to run on $Update will now only trigger in response to an $Update event, rather than also firing during a regular workflow submission. If you need an activity to run on both Submit and $Update, you will need to configure two separate activities. (7865)

A Submit event occurs the first time that a step has its ‘Submit’ button clicked to move the step through to a Completed state. An Update event occurs where a previously completed Step is edited and adjusted.

Submit events use AddActivity or AddConditionalActivity, where Update events must now use newly created AddUpdateActivity or AddConditionalUpdateActivity activity types.

Workflow completion status correct after step navigation

Fixed an issue where workflows that exited early — after a user navigated back to a previous step — would display an incorrect completion status. Step events are now ordered correctly by modification date, ensuring the displayed workflow status accurately reflects its current state. (1643)

Array values preserved during data merge operations

Fixed an issue where array field values were being inadvertently cleared when workflow data was merged with itself. Array values are now correctly preserved through merge operations, preventing unexpected data loss in affected workflows. (1660)

Submit messages now render HTML formatting correctly

Submit message content now renders HTML formatting as intended. Previously, raw HTML tags were displayed as plain text rather than being rendered, which could affect confirmation messages configured with rich text content. (1655)

Dashboard panels no longer update when value changes are prevented

Resolved an issue where dashboard panels continued to receive and apply data updates even when the preventValueUpdates flag was set. Panels configured to prevent updates will now correctly block incoming value changes. (8002)