v0.99.34
November 10, 2026
Every process can close with a clear outcome that flows back to the parent process, stages can repeat over a list of items, and completed tasks are better protected from mistakes and concurrent edits.
-
Feature
Process outcome and return from a Sub-flow
Final stages can now declare an outcome and a short description, including dynamic text built from the case data. When the case closes, the outcome stays recorded and visible in the detail, the history, the exports and for your external assistants. If the case was launched by another process through a Sub-flow, the parent process receives the child's outcome and description and can use them in the following steps. Cases already closed stay as they were, with no empty panels.
-
Feature
Stages that repeat over a list
A stage can repeat for each item of a list in the case data, one item at a time or several in parallel, up to 200 items. Each repetition has its own tasks, with a title and assignee that can depend on the item, and its own working data; at the end the results flow into the case explicitly. If the system restarts, work resumes without duplicates. Duplication, new version and export keep the configuration, and erasing a person's data also cleans the copies tied to the items.
-
Improvement
Better protection for completed tasks
A task that is already complete can no longer be completed a second time, and correcting its outcome or note requires starting from the up-to-date version. Completion and failure events fire only when the status really changes, so no duplicate cases or notifications are created. If someone else has already changed the task, the dialog tells you and refreshes itself.
-
Improvement
Concurrent edits under control
Conversational assistant profiles and the «Edit flow» window warn you when someone else has changed the same item in the meantime, instead of silently overwriting. Turning off the confirmation request before recording an outcome now asks for an explicit confirmation.
-
Security
Credentials in addresses recognized in more forms
The checks that prevent saving passwords or keys inside a web address now also recognize hidden or encoded forms, including nested ones. The same check applies uniformly when saving, publishing, when assistants read the flow, on import and in the execution log.
-
Improvement
Refinements
Document links requested by external assistants last 2 minutes and every issue is logged. The guide to the personal data erasure preview is clearer. An event subscriber without a type is rejected with an explicit message, truncated placeholders are rejected also when a case is created, the «Shift» move handles February 29 correctly and import warns when a declared scheduled event is unused.