Back to the changelog

• Improvement

  Logos are visible, and large files upload

  An uploaded logo showed the broken-image icon with no error message at all: the file was saved correctly, but the address returned never reached the service that serves those files. The defect also affected the site icon, the header logo and the print pages. A second one turned up next to it: a default technical limit, lower than the ones the product advertises, rejected every upload above 1 MB before it even arrived — SOP PDFs of up to 10 MB had never been uploadable.

• Design

  Branding gets its own section

  Logo and colours now have their own entry in the Management menu, instead of sitting at the bottom of the organisation details. The two sections save independently: changing the branding does not touch the company details, and vice versa.

• Security

  A personal key no longer widens what you can see

  Any user can generate a key to connect an AI assistant, and that key was created with no restrictions. In the contract assistants use, "no restrictions" means "everything": even a read-only user with no assigned items could list every process and item in the organisation and open their details. Visibility is now computed on each request using the same rules that apply on the regular screens, so the assistant sees exactly what you see.

• Security

  Credentials and sessions close when they should

  One-time password-recovery links can no longer be used twice: two simultaneous requests could both succeed, because checking and consuming were two separate steps. A revoked key now stops working immediately even on connections already open, whereas before a session started shortly earlier kept operating with its old privileges for up to an hour, writes included; the same applies to an expired or disabled key, or one whose role was lowered. And the live-updates channel closes when the session expires instead of staying open indefinitely, no longer announcing activity on processes the listener is not allowed to see.

• Security

  The mail server can no longer point inwards

  The organisation-configurable mail server address reached its destination with no validation at all: the protection existed for providers that work over the web, but not for traditional ones. It now covers both, is applied immediately before every send and not only on saving, and the connection is anchored to the verified address. An item's history also masks sensitive fields when read by an assistant, as it already did in the interface.

• Improvement

  Work no longer gets stuck

  If a process limits how much work can proceed at once, closing an item on its final phase did not free the slot: the queue stalled and whoever was waiting never started. Tasks are now completed in the intended order by hand or from an external assistant too — the rule only applied to automatic start, so you could close the third while the first was still open. A repetition limit is finally respected, because the count excluded exactly the steps it was meant to count. And a deadline set on a final phase no longer retries forever: the configuration is refused on publication and, on already-published processes, it stops attempting an impossible operation.

• Improvement

  Complete templates and exports

  Saving a process as a template now carries shared views, variables and declared dependencies as well, on top of the KPIs already included in the previous version. The same applied to export and to export via assistant: three paths meant to produce the same document, producing three different ones. Templates and export files produced earlier cannot be recovered and need regenerating.

• Improvement

  Errors you can see and contracts that hold

  Importing a process with a malformed task now explains what is wrong instead of returning a server error, and the same goes for a template saved in the past. Creating a process while passing start settings no longer ignores them silently: they are refused with a message pointing to where they are actually set. A connector name already in use gets a clear answer even when two people create it at the same instant. List and statistics pages reject filters that do not exist instead of answering as if they had applied them. Comparing two versions of a process no longer reports differences that are not there. And an assignee made only of spaces is refused, rather than being read as "no assignee".

• Improvement

  Slow replies no longer overwrite your work

  About twenty situations shared the same defect: a reply arriving late was applied even if you had meanwhile changed screen, filter, conversation or selection. Among them, the AI-generated description wiping the text you had just typed, the copilot applying a proposal to a design that had since changed, a provider test result referring to a configuration already edited, and closing a task that closed the wrong one. In the same direction: selections no longer point at items that disappeared after a refresh, a direct link to a page keeps filters and position after signing in, and the address for creating a new process works instead of being read as the identifier of a non-existent one.

• Design

  Printing, dates and language

  Printing a map stops if the main diagram is missing, instead of producing a document without its content, and offers a retry. The trend chart shows the right day for those working west of Greenwich too. AI-assisted generation has adequate waiting times on every operation, not just some. Durations are written in the chosen language, and a dismissed welcome message stays dismissed for the right person rather than for the browser.

• Integration

  Changes that need attention

  Variables edited through the API now require stating which revision you are editing: writing without it returns an explicit response explaining how to proceed. It is a safeguard, because a variable feeds formulas, rules and templates across the whole organisation, and a blind write erased other people's work without a trace. Forcing a status change now requires a written reason when called directly too, as the interface already demanded: before, the operation went through and the history showed a generic note. Some configurations that never worked at runtime — a deadline on a final phase, a repetition limit with no exit destination — now block publication until corrected. And on-premise installations with the mail server on the local network must declare it in the configuration, as already required for the AI engine.