Before You Put an LLM in a Flow
Let an LLM generate content if the result is reviewable. Do not let it make the business decision.
Tag: flow
7 posts in this channel.
Screen Flow Component Validation Without Surprises
Flow screen validation is a three-method contract. Keep internal and external errors separate, render them at the right time, and never make navigation depend on accidental component state.
An Error Contract for LWC, Apex, and Flow
Errors become much easier to handle when LWC, Apex, and Flow agree on a small contract: stable codes for automation, safe messages for people, and correlation details for support.
Bulk-Safe Invocable Apex
An invocable method receives a list for a reason. Treat every request as independent, query and write in collections, and return one useful outcome for every input.
Where Flow Should End and Apex Should Begin
Flow and Apex overlap, but they are not interchangeable. I use Flow for visible orchestration and Apex when data structures, transaction control, scale, or reuse become the real problem.
Seven Summer '26 Flow Updates That Add Up
Summer '26 has a cluster of small Flow improvements that make automation safer, faster, and easier to configure: unanimous approvals, scheduled-flow batching, date operators, better data tables, styling overrides, and cleaner Apex-defined inputs.
Flow-Friendly Apex Is Becoming Its Own Design Discipline
Summer '26 makes Apex actions easier to configure in Flow Builder. The opportunity is bigger than nicer inputs: build actions admins can use safely without reading the source.