Back to the changelog

• Design

  Safer concurrent saves

  If someone else changes the same data, saving reports a conflict without overwriting their work. Case, map and designer drafts retain the version you started from; reloading after a designer conflict also rebuilds its open panels. Saving case data keeps the full page details available.

• Improvement

  Linked documents and protected closed cases

  When an integration uploads a document directly to a case, the file and its data reference are confirmed together, with a history entry. Repeating confirmation does not duplicate the link. A new upload to an already closed case is rejected before transfer, while an upload that already succeeded continues to report success. Failed or expired Library uploads no longer unnecessarily retain the reserved name.

• Improvement

  AI decisions that are easier to configure

  The cursor stays in place while editing decision questions, and deleting a phase with the Delete key asks for confirmation. Checks consistently report invalid configurations and missing or incompatible providers, including at publication. Decision rules and uncertainty handling remain as configured in the flow.

• Improvement

  Clearer history and waiting queues

  History distinguishes leaving the queue manually from an override, retains event names and presents actors and dates more clearly. Corrections to notes and ratings on completed tasks leave a trace. Queued cases are ordered by position, and scheduled starts wait while the flow is suspended. In Italian forms, “0.500” is correctly recognized as 0.5.

• Integration

  More precise integration responses

  Creating a case returns its actual state after the initial tasks. Integration tools better distinguish an invalid request, a missing task and an already completed one; audit-log failures have a recognizable code. The API documentation describes the new checks and the codes clients need to handle.