FlowVisual
Changelog

What changed

Engine corrections come first. When a release changes numbers, we say so — because those numbers end up in your proposals.

1.0.3

Current
4 August 2026

Engine affected

This release changes results for existing models. The new values are the correct ones.

The engine now handles loops and drop-offs correctly, the diagram reads without explanation, and documents survive restructuring.

Engine
  • A drop-off with an outgoing edge is now called out: drawing “10 % withdraw” and routing those cases back means the real drop-off is 0 %.
  • Rework loops now count towards lead time — previously they only affected cost and utilisation.
  • Loops that revisit a step are reported from three passes per case onwards. Before, a loop could silently multiply demand.
  • A join behind a true parallel split halved the volume; affected steps could drop out of the bottleneck list.
  • An overloaded step on a side branch throttled total throughput and therefore overstated savings.
Proposal & handbook
  • New “Reviewed options” page: variants ranked, with a recommendation and the honest statement of which option is not worth it.
  • Payback is only shown against a real investment named in the document.
  • The cover page now distinguishes whether the bottleneck is solved, merely moved, or still there.
  • The handbook carries its creation date; seed and run count are printed for real.
  • German documents use German decimals, English proposals English thousands separators.
Drawing & interaction
  • Edges carry arrowheads and show their percentages directly in the diagram.
  • Rework edges run dashed underneath the process instead of cutting through nodes.
  • Deleting a sub-process removes the entire subtree; areas can now be deleted.
  • Recently opened documents are offered, and the last session is restored.
  • Corrupted individual files are skipped instead of discarding the whole folder.
  • Large models run noticeably smoother; with reduced motion the animation stands still.

1.0.2

23 July 2026

Engine affected

This release changes results for existing models. The new values are the correct ones.

Maintenance release. Six engine defects corrected and saving made crash-safe.

Engine
  • Utilisation is computed the same way everywhere (peak day / P90) — canvas, handbook and proposal show the same value for the same step.
  • Levers on sub-processes now take effect; previously they silently did nothing.
  • The change table in the proposal also lists changed case volumes and routing splits — no savings without a documented change.
  • Media breaks at joins are no longer counted twice.
  • Lead times close to the capacity limit no longer jump.
Files
  • Saving is crash-safe (temporary file plus atomic rename) — a crash mid-save can no longer corrupt the file.
  • Named versions are stored with the document; previously they were lost on quit.

1.0

25 June 2026

First public release: model, stress-test, four lenses, proposal and handbook export.

Scope
  • Process modelling from six building blocks, with areas and sub-processes.
  • Monte Carlo stress test with P10–P90 bands for lead time and throughput.
  • Four lenses: Model, Operations, IT and Management.
  • Branded proposal and handbook PDFs.
  • macOS and Windows from one codebase, entirely local.

Get FlowVisual 1.0.3

macOS 13 or newer (Apple Silicon and Intel) · Windows 10/11

Get it on the Mac App StoreGet it on the Microsoft Store