Back to the changelog

• Feature

  Events accessible from the Designer

  In the Event task picker, Manage events opens the dictionary in a new tab; Open event opens and highlights the selected definition. Back in the Designer, reopen the list to load newly created events. The links are hidden in Expression mode.

• Feature

  Flow warnings on the Monitor

  On a published flow’s Monitor, Admins and FlowDesigners see the “Flow configuration warnings” panel: an SLA variable that does not resolve, a missing AI provider, fields read outside the Data Schema and similar, even when automatic tasks are configured correctly. The link opens the Designer to fix them in a new version.

• Improvement

  Fallback outcomes checked

  With strict data schema, a blocking task cannot be published if human outcomes differ from the System One outcome question. The Designer also flags the error when you use a Preset.

• Improvement

  Human decision time

  Opening an assigned fallback starts observed time tracking. Two warnings help identify a missing task code and a Wait task that will always require a human decision.

• Improvement

  Fallback assignees

  Fallback assignees appear in reconciliation and flow warnings; assignments that reach no active user are also reported during execution.

• Improvement

  Consistent completion across channels

  APIs, the extension and MCP assistants apply the same checks to human fallback. If configuration is invalid, the request stays open without losing the pending decision.

• Improvement

  Clearer AI errors

  If saving an AI result fails, a second problem in the diagnostic log no longer hides the original cause.

• Improvement

  History without false updates

  A Script that writes the same value again no longer adds a “Field updated” row, making actual changes easier to see in history.

• Improvement

  Clearer Script error messages

  Script errors show the original message without repeated “Error: Error:” prefixes; diagnostic codes stay the same.

• Security

  Consistent Flow Agent shielding

  The Flow Agent’s Data Shield evaluation follows the organization’s default LLM provider even when a default Jev provider is configured.

• Improvement

  Automatic retries in the right phase

  A queued retry no longer reruns an automation after the item has left the task’s phase.

• Improvement

  Entry protected from concurrent transitions

  An automatic transition evaluated earlier no longer overwrites a new entry in progress into the same phase.

• Design

  Cleaner release highlights

  Highlights written across multiple lines no longer show the source quotation markers.

• Improvement

  Admin recovery for pending starts

  An Admin’s emergency force can recover an item awaiting start confirmation even when ordinary start roles exclude the Admin, retaining the reason and history.

• Improvement

  Missing AI providers flagged earlier

  Flow warnings now also flag LLM tasks and AI titles that need a default provider which has not been configured.

• Improvement

  More precise Jev conversion warnings

  Conversion to an Auto phase distinguishes positive comparisons from negations and asks you to check uncertain exit paths, with correct wording for a single outcome too.

• Improvement

  Clearer conversion effects

  Before converting a phase to Auto, the Designer warns about non-blocking manual tasks and the form that will remain active.

• Improvement

  More accurate process alert origin

  New Process Map health alerts are identified as event-driven starts. The origin of existing items remains unchanged.

• Integration

  More accurate recovery status

  When creating an item, APIs and assistants distinguish an entry awaiting recovery from automation already halted with no pending entry.

• Security

  Correct attribution for early starts

  When an early start transfers legal hold to an item, the audit record distinguishes the person or assistant from the automatic scheduler.

• Design

  Code warning in your language

  The Designer shows the warning about phase codes shortened to fit the length limit in Italian or English.

• Design

  AI log filters

  The AI log item and task filters follow the page address. Removing a filter also updates the link; Back and Forward restore the corresponding filters.

• Improvement

  Description preserved in the draft

  The description updates in the draft as you type: closing the panel with Esc does not lose text. Saving the flow is still required to persist it.

• Design

  Numbers and local cancellation

  In a numeric field, the first Esc cancels a local edit or error without closing the panel. A second Esc can close it. Ambiguity messages use the entered number; numeric placeholders use a comma in Italian.

• Design

  One message for an invalid number

  Numeric fields with a specific explanation show one message associated with the field, including for screen readers; validation still prevents saving disallowed values.

• Improvement

  Empty numeric fields equivalent to zero

  KPI order, default task timeout, digest interval and notification delay accept an empty field as zero. Other field constraints still apply.

• Improvement

  Recurring cost rows

  Deleting a recurring cost row preserves the values and any errors in the other rows, including during editing.

• Design

  Esc in overlapping controls

  Esc closes the innermost open control first, including flow menus, settings search and item title or entity editing.

• Design

  Accessible AI configuration

  LLM controls respect read-only mode. The Context field label focuses its editor even when showing an expression preview. An unavailable assistant is reported without exposing its technical identifier.

• Security

  Ending impersonation

  Ending impersonation reloads the administrator’s role and features. If session verification fails, sign in again.

• Improvement

  Solution previews

  A preview file cannot be imported as a version: the message asks you to export a Solution version.

• Improvement

  Phase code length

  Codes derived from flow names respect the length limit. A derived phase code also accounts for the flow code length and space reserved for events; custom codes are not rewritten.

• Improvement

  Schema derived from a form

  The data schema derived from a form retains only properties supported by the data contract. Form options, such as choices and format, remain in the original form.

• Improvement

  Deletion by the creator

  The detail also shows Delete to Operators and FlowDesigners who personally created the item, provided no task execution has occurred. A Failed task counts as an execution even for an Admin; final checks remain on the server.

• Improvement

  Derived outcome order

  Saving preserves the order of still-valid derived outcomes and appends new ones. The Designer warns when a non-empty manual set is expanded.

• Improvement

  Savings dates and totals

  A Saving Challenge’s starting month follows the saved calendar date without timezone shifts. Pending rows remain excluded from cumulative consolidated savings.

• Design

  Calendar outcomes and retries

  The calendar shows automatic task outcomes. When Retry is rejected because the phase changed or another attempt started, the message explains the cause in the interface language.

• Improvement

  Policy outcomes in the rule picker

  The rule picker includes the low-confidence outcome defined by the organization policy for applicable AI tasks.

• Improvement

  More accurate AI diagnostics

  Field warnings no longer treat the system prompt as a template, nor report the internal origin marker as “removed by minimization”: it is always excluded from templates. The Jev connection test keeps its normalized diagnostic code in the activity log.

• Improvement

  Consistent task names

  Configuration errors use the Sub-flow, Integration and Script names shown in the Designer.