v0.84.2
August 22, 2026
**Truly immutable versions and data protection that follows the family.** Reactivating a version used by items creates a new draft instead of reopening it; an archived process can't be republished or shared by mistake; duplicate copies exactly the chosen version; and a new sensitive classification on the parent process also protects child elements already generated in other processes.
-
Improvement
Reactivations without surprises
Reactivating a disabled version that has in-progress or completed elements creates a new draft and leaves the historical version untouched: people working on those elements can no longer have the process changed under their feet. The version history now also shows disabled and archived versions, with the Reactivate button finally reachable.
-
Improvement
Archived means archived
An archived process can't be republished directly (restore first, then publish) and accepts no new share links; archiving revokes existing links. Republishing an older version is now declared as a rollback, in the audit trail and in the response.
-
Improvement
Honest settings on published versions
On published versions, the Designer settings tabs (Data, Form, entity URL, Variables, KPIs) are read-only with an explanation, instead of accepting changes that wouldn't be saved. Saving from the canvas still creates the fork as always.
-
Security
Sensitive data protection reaches children
When a process spawns elements in other processes, a new sensitive classification added to the parent now also protects already-created children: propagation happens automatically on the copied paths, updating history too. Never implicit de-classifications: removals remain an explicit choice.