Back to the changelog

• Design

  Your brand colours really show

  The primary and accent colours saved correctly and changed nothing in the interface: the value reached the page, but no part of the styling ever read it. The primary colour now colours the main actions, the active menu entry and the keyboard focus outline, while the accent colours text links. Text on coloured backgrounds adapts on its own to stay readable with any shade, including very light and very dark ones, and the colours work in dark mode too. If you have not set any colour, nothing changes: the look stays exactly as before.

• Improvement

  Deadlines no longer spin

  If a deadline's destination phase was not also a step drawn in the diagram, the operation failed and was retried every minute, forever, with nobody noticing. A deadline's destination is now recognised for what it is: an emergency exit, not an ordinary step of the process. When an item enters a phase through a deadline, that new phase's own deadline now applies, whereas before it was cleared right after entry and the item sat there with no time limit. And a deadline on a final phase is allowed again: the previous version refused it on publication, but it is a legitimate and useful setup, because an item that reaches the final phase stays open until the closing tasks are done — and if nobody does them, you need a way to escalate.

• Improvement

  The designer tells the truth about final phases

  Marking a phase as final hid the phase type and its outgoing transitions, but the diagram kept showing them: you could build an unpublishable process without noticing, and only find out when you tried to publish. The action now asks for confirmation and lists exactly what it removes, the outgoing transitions really are deleted, the type becomes automatic, and the rules stay saved in case you change your mind. A final phase's emergency exits are finally visible in the diagram, drawn with a dashed line and the deadline shown, so they are distinguishable at a glance from ordinary steps. The diagram no longer accepts an outgoing step from a final phase, neither by direct connection nor from the quick-add button, and the AI copilot cannot propose one either.

• Security

  The assistant key leaves the address

  The address for connecting an AI assistant carried the secret key inside it, where it is exposed — and for the main channel that address did not even work, because the service rejects keys passed that way. The address is now clean and the key is copied from a dedicated field. Creating an access key with a double click no longer leaves an active, invisible credential either: the key is shown only once, and the second creation produced a valid credential nobody had ever read, and therefore nobody could knowingly revoke. Cancelling the extension link now really stops the operation, instead of letting it continue and send the token after you have navigated away, and links that open a new window no longer give it any control over the page you came from.

• Improvement

  Variables are protected, and references are visible

  A variable used by a published process can no longer be deleted or renamed: the protection only covered variables used in indicator formulas, and ignored concurrent-work limits, rules and task templates — the reference stayed in the process, pointing at nothing. Publishing a process that uses a non-existent variable is now refused, naming which variable and where; in draft it is only a warning, so you can keep working while already knowing what is missing. An exported process finally keeps the variables it declares it uses even when they no longer exist, instead of dropping the dependency from the document exactly when knowing about it matters most.

• Improvement

  Assignees, queues and confirmations

  Processes generated by the AI assistant now carry their task assignees too: before, the assignee appeared in the definition but the tasks were created with nobody assigned, silently, so the process looked configured when it was not. Items queued behind a concurrent-work limit reappear in the statistics even when that limit is expressed with a variable, whereas before the phase vanished from the saturated-phases panel and the queue existed without being visible. When you manually force a phase change, the tasks of the abandoned phase are closed instead of staying open and cluttering queues, alerts and history, while the closing tasks of the final phase remain usable. The force command is no longer offered on items that are already closed, and copying the activation address now confirms the copy and reports if it failed.