Back to the changelog

• Improvement

  Unambiguous numbers

  Values such as 1.440 or 10.000 are no longer silently saved in timeouts, delays, SLAs, iterations, rules and API calls: the Designer shows the two possible readings and blocks "Save" until the number is written as intended; imports and the API return a clear error. Already saved values keep working as before and are flagged at publish time, with a badge on the node. When data is passed to a Sub-flow, ambiguous text targeting a numeric field fails the task instead of converting silently, and a missing parent field is no longer created empty in the child.

• Improvement

  Blocking tasks, amendments and reopenings

  Manual phase changes (browser, extension, MCP) count only the latest instance of each blocking task: a failed attempt that was later superseded no longer holds the case. A participant task failed for a contact to be fixed keeps the phase open, the final one included, until the contact is corrected. Tasks of a phase already left can no longer be edited (amending completed ones remains), the outcome of a skipped or failed task cannot be rewritten and no task reopens on a concluded case: the interface explains it instead of offering actions that would fail.

• Improvement

  Completion metrics equal on every channel

  Observed duration, declared effort and reliability are computed the same way from browser, extension, API, MCP and the participants' portal; fallbacks closed by a person count as human work in Analytics, process maps and KPIs, and a new "tasks without duration" counter tells how much of the costs is still estimated. A realignment script, run by the team, completes the metrics of tasks already closed.

• Security

  Webhook log protected at write time

  The execution log of Webhook tasks is now written already protected: the case's sensitive fields and secrets no longer reach the log, not even at rest, while the real call still carries the actual values. Rows written earlier remain protected on read.

• Security

  Legal hold on document versions too

  Under legal hold, replacing a document no longer deletes previous versions nor frees space; deletion always answers with an explicit refusal, removing the reference from the data remains possible and is recorded, and the expiry of documents in the Trash is suspended while the hold lasts, restarting from zero when it is released. The Document field and the Trash show the hold state.

• Improvement

  Event start switched off across the flow family

  Unwiring a Process Map edge, or deleting, deactivating and archiving a map, switches event start off across every version of the flow, the Published one included, and the response tells the truth about what stays on; new map versions carry their links along. Whoever tries to switch event start off from a flow sees who keeps it on, and the administrator has a new "Switch off from all sources" action, with a mandatory reason recorded in the activity log. Archiving a map that switches starts off requires permissions on the flows involved and an informed confirmation.

• Improvement

  Events wait for blocking tasks on human phases

  On a human phase an "event received" rule no longer moves the case out while a blocking task is still open: the event stays recorded and the rule fires, once, when the last blocking task closes. Direct subscription actions remain an immediate move and are now flagged at publish time.