Skip to main content

v27.0.8 - 05/26/2026

· 2 min read

AutoFlow joins the print queue 🖨️ – your flows can now watermark, rebrand, or archive every PDF Business Central prints, and report parameters respect live values from the flow. Bonus: a Case step for cleaner branching instead of stacked decisions.

Features​

  • Intercept any PDF Business Central is about to print and replace it with a modified version from a flow – watermark drafts, drop a customer's letterhead on every invoice, archive every quote to SharePoint. Use the new When a PDF is printed trigger; end the flow with a Return PDF step to deliver your version. Paid-tier feature (CHN-234)
  • The PDF Print step's report parameters now accept SmartField placeholders – print the same report layout with different filters, accounts, or date ranges depending on the flow's runtime data (CHN-258)
  • Reach into your own AL with the new Run Codeunit / Report step – invoke any codeunit or processing-only report by ID, optionally passing a flow-resolved record. Report parameters accept SmartField placeholders too. A built-in block-list protects system-critical codeunits from accidental flow calls (CHN-199)
  • New Case step picks one of several branches based on a SmartField expression – like switch/case, without the stack of nested decisions (CHN-230)
  • Exporting a Main/Sub flow pair as a template now preserves the SubFlow's stable Code (used by Run-SubFlow callers) and its custom icon – templates work straight after import in a fresh environment (CHN-249)

Bugfixes​

  • The PDF Print step accepts filter-only reports (Trial Balance, G/L Register, …) – the Record Selector is now optional for reports without a DataItem table (CHN-250)
  • Users without AutoFlow permissions no longer see an AutoFlow menu in their role center, and standard BC role centers stop showing the menu by default – opt-in via Personalize (CHN-256)
  • Licensing failures surface as readable errors instead of a silent blank package list; the activation wizard verifies the API key actually persisted before declaring success, and a View API Key action helps support diagnose stuck activations (CHN-254)
  • When a flow fails mid-execution on a synchronous trigger (Webhook, the new PDF Print trigger), the per-step log and status now tell you which step failed – previously the diagnostic trail was rolled back along with the runner state (CHN-252)