Back to the changelog

• Improvement

  A single command to change status

  The two buttons "Force status change" and "Force transition" shared the same icon and near-identical names, but did very different things: one respected the transitions drawn in the process, the other overrode them all. The command is now one, with a "Respect the flow" checkbox on by default: only an administrator can untick it, and doing so makes the reason mandatory, because that operation is recorded in the history as an override. And a trapped item — a phase with no way out — opens the command already in unlock mode, instead of offering an empty list precisely when it matters most.

• Improvement

  You only see the commands you can use

  Those who cannot design processes now see them read-only: before, the full designer opened — toolbar, panels, Save button — where every action would have been rejected, with two unexplained "Forbidden" warnings on opening. The Analytics sections are reserved to those who design and measure processes, and the menu entry only appears to those who can enter. And a task's note field only appears to those who can actually save it: before, you wrote the note and lost it to a generic error.

• Improvement

  The designer works without HTTPS too

  On unsecured connections — an internal network without certificates, an older browser — adding a phase, a note or a task did nothing, with no message at all: identifier generation depended on a browser feature only available on secure connections. It now works everywhere.

• Improvement

  Configuring email without surprises

  The values proposed by the provider forms — port, region, zone — are now really saved: before, they were shown on screen but never entered the save, and the server answered "required field" while the value seemed to be there. Required fields are marked and saving is disabled until they are filled. The status message no longer contradicts itself when no provider is configured. And the guide has a dedicated email providers section — priority between installation and organisation, what each type needs, the most frequent pitfalls — with every help link on the page now pointing there.

• Improvement

  More honest server responses

  Deleting a phase that contains work from the designer now says no and explains, listing the phases involved and how many items they hold: before, it answered "all good" while keeping the phase, and the process could become unpublishable. An empty request no longer clears an item's assignee dragging its open tasks along: clearing remains possible only by stating it explicitly. And the general statistics reject filters that don't exist, instead of returning numbers for the whole history as if they were filtered.

• Design

  Polish and accessibility

  The five switches in the Status panel can be operated from the keyboard and are announced correctly by screen readers. Global variables are protected against concurrent edits: two people saving the same variable no longer silently overwrite each other. Renaming a Process Map no longer fails on the first try. A non-standard boolean in the variables editor declares itself instead of showing up as `true`. And the Disable button's tooltip no longer says "Settings".

• Security

  Fewer clues for outside observers

  The system-reserved event category can no longer be assigned from outside: a custom event cannot present itself as a system event. The public process trigger no longer reveals which processes exist: an invalid key and a non-existent process get the same answer. Embed domain validation applies on every path — manual entry, automatic discovery and approval. Notifications switch off when the condition that raised them clears, instead of staying forever. And a momentary AI assistant error no longer lights up the "Connection to server lost" banner while the connection is alive.