Skip to main content

v27.0.36 - 09/23/2026

· 3 min read

A release about the empty and the orderly: a loop that finds nothing shrugs and moves on, your newest run sits at the top of the list, and subflows stop losing themselves on the way over from a template. And no, you no longer need to be an admin to press Start. 🧹

Features​

  • An interactive trigger that comes from another extension can now offer the "Confirm dialog" and "Send notification" steps as well, so a trigger built by your partner behaves like the built-in page triggers
  • A configuration table inside a step can now hold a SmartFilter per row – the cell shows the expression and opens the SmartFilter builder when you click it (CHN-460)
  • A configuration table can now also carry lookup columns that pick their source and their filter from the other values in the same row, and a table with more columns than fit scrolls sideways instead of squeezing them. No shipped step uses such a column yet – steps from your partner can (CHN-489)

Bugfixes​

  • A For Each Loop whose selector finds nothing now skips the loop and carries on with the step after it instead of failing the execution. A selector pointing at a single value still reports an error, and a misspelled output name reads as an empty collection – so check the spelling first when a loop unexpectedly does nothing (CHN-483)
  • The executions list opens with the newest run at the top, whether you come from "Last execution" on the flow list, from the Flow Workspace or straight from the menu (CHN-484)
  • A flow that runs a "Run SubFlow" step no longer fails right at the end with "AutoFlow Execution does not exist, Entry No.=0" (CHN-482)
  • A flow you create or update from a template now points its "Run SubFlow" steps at your own copy of the subflow instead of at a version number that only existed on the system the template came from. The step works on arrival and keeps the input values the template shipped, a flow imported earlier repairs itself the next time you open the step, and a subflow that is not installed yet is reported as missing instead of passing an empty parameter list off as fine (CHN-488)
  • "Run SubFlow" now also works in a flow started by the interactive Document Modified trigger or by one of the incoming-document triggers – such a run no longer stops after a 15-second wait with "Could not create the SubFlow child execution for step ..." (CHN-491)
  • Starting a flow no longer requires the "AutoFlow Administrator" permission set – a user with the USER role can run flows again (CHN-487)