Back to the changelog

v0.99.1

October 18, 2026

External participants receive their links and reply from the public portal; sturdier transitions and task completions on every channel; pre-1.0 cleanup; installation profiles for the SaaS.

  • Feature

    External participants: links sent and public portal

    When a case enters a Collaborate phase with an external participant, their personal link is really sent according to the contact policy (email, webhook or event, with reminders during business hours). The participant opens the public portal, sees only their part, records the outcome and uploads the requested documents; every access is tracked. The link stays valid while the task is open and can be revoked from the case. Requires the "External collaboration" entitlement.

  • Improvement

    Transitions serialized with data edits

    Every phase change, from any channel, queues up with edits to the case data: history and phase deadline always reflect the real data. If a concurrent edit changes the final gate's outcome, the transition answers "retry" instead of closing the case on stale data.

  • Improvement

    Completing a task: same rules everywhere

    From the browser, the extension or an agent via MCP, completing a task follows the same rules: who may do it, what goes into history ("Task «name» completed — outcome: …"), what happens if the task is already closed. An unexpected outcome on a Webhook task with human fallback is no longer an error: it hands the decision to a person.

  • Improvement

    Cleanup before 1.0

    Secrets encrypted with the old format are converted automatically at upgrade; events without an organization and outdated task settings are removed; a few duplicated API properties disappear. Integrators find the details in the changelog.

  • Feature

    Installation profiles

    Three declarative profiles (single machine, two-node SaaS with managed database, dedicated) and an installation-kit generator that prepares configuration, compose files and checklist without touching anything. Nothing changes for single-machine installations.

  • Improvement

    Designer

    The phase "Type" field is now "Progression" and explains who decides the exit from the phase.