Back to the changelog

• Improvement

  Duplicate-proof entity reference

  The code identifying your entity — order number, case, ticket — is now reduced to a canonical form before being compared and stored. Previously a stray space, a tab, an invisible character pasted from another program or a different capitalisation was enough to spawn two separate cases on the same entity, bypassing the "one active instance" rule. The same rule now also applies when you change an item's reference, not just when you create it.

• Security

  Verified entity type and assignee

  An entity type belonging to another flow — or to another organisation — can no longer be attached to an item; legitimate cases still work, namely the flow's default type or one declared as multi-flow. Likewise, the person set in the flow design must match an active user in your organisation: previously an address with a typo or a former colleague's was accepted silently, and the result was worse than an error, because that task never raised reminders or escalations and stayed hanging on nobody. Dynamic expressions remain free.

• Improvement

  Event-based start that actually works

  When setting up event-based start from the designer, the list of linked events was silently discarded: the switch stayed on but with no event attached, so a trigger that would never fire. It is now saved properly. Also, deleting an event removes its reference from the flows that used it, instead of leaving a dead link behind.

• Improvement

  Impossible settings, rejected up front

  An SLA of zero or negative minutes — already expired the moment the item is born — and a time window starting and ending at the same minute are now rejected with an explanation, instead of being accepted and behaving unpredictably. The overnight window, crossing midnight, remains fully supported. A negative cost per minute, which distorted item and flow cost totals, is no longer accepted.

• Design

  Filters, calendar and numbers that add up

  The Draft filter finally shows drafts: a flow with a published version and a more recent draft disappeared from the very filter meant to find it. In "All Items" the calendar also exposes the start date and completion date views, and if no item in the period has the chosen date it switches to the start date and tells you, instead of appearing empty for no reason. Average lead time is now weighted by the number of completed items: previously a day with a single item counted as much as a day with a hundred. UTC is selectable again among alert time zones.

• Improvement

  Required reference and missing translations

  In flows requiring an entity reference, the "New item" dialog no longer generates an automatic code in place of the field left empty: the reference must actually be entered. Also fixed two areas that stayed in Italian with an English interface: flow status on the Events page and the What-if summary copied to the clipboard, numbers included.