v0.39.0
July 9, 2026
Two big process-governance features. Ideal path and deviations: declare a flow’s “happy path” and FlowSharp flags on its own the items that stray from it. Exception routes: timeouts, WIP limits and SLA breaches can move an item into states the operator must not be able to pick by hand (Escalation, Overdue, Out-of-WIP), with automatic SLA escalation to a dedicated state.
-
Feature
Ideal path and deviation detection
Declare a flow’s ideal path right in the designer: the states of the “happy path” are highlighted in **gold** on the canvas (nodes and edges), so the expected route is readable at a glance. On every transition FlowSharp works out whether the item has left the ideal path (an off-path jump or a step backwards) and marks it **deviated**, remembering where and when — reaching a final state (e.g. KO) does not count as a deviation. A **“Deviated” filter** in the Monitor isolates off-track items; the item detail shows a badge and pinpoints the deviation on the timeline; on the Process Map an amber deviation badge appears on nodes plus a dedicated Diagnostics alert. You can also tag the **roles** of an actor on the map, and FlowSharp warns if they can’t start the linked flow manually.
-
Feature
Exception routes: timeout, WIP and SLA to unlinked states
A new **“Exclude from manual selection”** flag makes a state reachable **only** by automatic routes (timeout, WIP, SLA or rules): the operator doesn’t see it in the manual transition menu and the system rejects the attempt — the Admin **force-transition** can still override, with an audit trail. The timeout and WIP-redirect target pickers now offer **all** states of the flow; choosing an unlinked state **auto-adds the arc** with an “exception” style (dashed + ⚡), and removing or changing it asks for confirmation. SLA now has **two modes**: warning-only (as before) or **automatic escalation** — on breach the item is moved once to a configured state, even off-graph, and the deviation is recorded. The designer also warns about a timeout that loops back to the same state without a guaranteed exit.
-
Improvement
Map health and flow portability polish
Map-health **reports and notifications** are now produced in the tenant’s default language (AI report, notification title and body). Flow **export/import** carries the safe configuration fields too, without dragging along tenant-specific references, and creating a **new version** of a flow copies the full configuration and preserves node positions. The map **analysis panel** now refreshes correctly when you change the period.