Back to the changelog

• Feature

  The item title, everywhere it matters

  The item title is now a first-class property: visible in the quick view, on Kanban cards, in the Calendar and in the detail page — always next to the entity reference, never replacing it. It can be edited from the detail page with a properly visible editor, every change is recorded in the history with the previous value, and search finds it everywhere: lists, filters, exports. In flows, `{{item.title}}` resolves in every channel — webhooks, events, scripts, conditions and AI prompts.

• Feature

  Title template, optionally AI-generated

  In flow settings (Entity tab) you can define a title template over item data — e.g. `{{item.data.lastName}} : {{item.data.orderNumber}}` — that recomputes itself whenever data changes. With the AI option, the template becomes the prompt and the title is generated once, in the background, only when every placeholder has a value: no titles coined from half-filled data. The Try button checks it against a real item and flags empty placeholders. Where a template exists, the title is managed by the flow and can't be edited by hand.

• Security

  AI receives only what the flow allows

  The assignee in AI prompts moves from a hard-coded ban to a per-flow choice: protected by default on every flow, existing and new. When protected, the prompt receives `[redacted]` instead of the value — the model knows the field exists, not who it is. The title can be marked AI-sensitive too. Webhooks and non-AI integrations are unchanged: values travel in the clear there as always, so passing the assignee to a CRM remains possible.

• Improvement

  Empty automations no longer claim success

  An automatic task with no executable configuration used to pass publishing and show as "Done" in milliseconds without doing anything — even when blocking. Publishing now rejects it with a clear error, and for already-published flows the designer's promise holds: a blocking task fails, a non-blocking one is skipped with the reason recorded. The audit trail tells what actually happened.

• Improvement

  Deleting a Process Map unwires everything, and says so

  Deleting a Process Map now unwires published flows too: the confirmation lists the affected flows by name and which event starts will cease, and the response reports the outcome flow by flow. The Process Maps page gains a Delete button for administrators. Items already in progress are untouched. Event-start configuration is now editable on published flows as well — the manual remediation path that was missing.

• Improvement

  Distinguishable task runs and a searchable filter

  When the same task runs multiple times on an item, the runs are now distinguishable: times with seconds, per-run duration, an "Iteration N of M" badge and a short id in the task card — a rating or note can no longer land on the wrong run. And the flow filter on the Tasks page becomes a searchable selector grouped by family, keyboard-navigable, even with hundreds of versions.

• Improvement

  AI summaries honest for integrations too

  Item lists and MCP tools now expose the AI Summary's status, reason and timestamp: an integration can no longer mistake a summary the server knows is outdated for a current one. The guide documents every staleness reason.

• Improvement

  Procedures with preview and rich media

  "New version" scrolls you visibly to the editor and the formatted preview is one click away. Procedure bodies can embed images, videos, PDFs and diagrams: external hosts go through the security domain verification.

• Design

  One bar across Monitor and Analytics

  Monitor and Analytics now share the same navigation bar in the header, with the current view highlighted and no jumps when switching. "Back" from the designer truly returns to where you came from, even after a reload. Every question mark opens the same guide window. "Automation Plan" is now "Implementation Plan", and in Italian the per-flow actions say "Analisi", for screen readers too.