Skip to content
Flux Forms

Home / What's new

What's new in 0.8.0

On-demand flows finally run, a new Run Apex action, and flows from installed packages work.

Flux Forms 0.8.0 is about one thing: the flows and the code a form can reach on submit.

Two kinds of flow that used to be listed as "will not work" now work, and there is a new action type for running Apex your administrator has approved.

On-demand flows now run

A flow created with the "no trigger, invoked on demand" start could not be run at all before — Salesforce refuses to let a packaged application start one. Flux Forms now detects these flows and runs them through an Apex class in your own org instead.

For a marketeer, nothing changes: whitelist the flow, pick it in an Invoke flow action, done. The routing is automatic and ordinary autolaunched flows take exactly the path they always did.

For an administrator it is a one-time setup: register the proxy class in the new Apex Handler Settings tab, and grant the background Automated Process user access to each on-demand flow. Nobody has to write the class — a ready-made one ships as its own small package, Flux Forms Flow Proxy.

See Apex Handler Settings.

On-demand flows also receive two inputs Salesforce supplies itself — emailAddress and individualId — which the flow does not list among its own variables. Flux Forms adds them to the captured contract automatically, so they show up in the review step and can be mapped from form values. Nothing to configure.

A new Run Apex action

A purpose can now approve Apex classes a form may run on submission, next to the flows it already approves. In the Form Builder, Run Apex offers those handlers with their inputs and outputs as typed rows — the same experience as a flow's variables, because the class describes its own contract.

This is the way to extend Flux Forms with logic that is easier to write in code than in a flow.

  • Approving a class needs configuration-admin access, the same bar as writing one.
  • The builder never types a class name: every picker lists classes discovered from the org, so a typo is not expressible, and Save rejects a form naming a class its purposes do not approve.

See Approve Apex handlers and Run Apex actions.

Flows from installed packages work

The flow picker now shows flows belonging to installed packages with their package prefix (acme__Send_Welcome), and Flux Forms keeps that prefix with the flow so it starts the right one. Just pick it from the list.

If you whitelisted a packaged flow before this release, its prefix was not recorded and Flux Forms treats it as living in your own org. Remove it and add it again from the picker so the prefix is captured. Your own flows need nothing.

Purpose Manager shows what cannot run yet

  • Each purpose has an Apex actions section, with Add Apex handler, the class's declared inputs and outputs, and a display name.
  • An on-demand flow whitelisted while no Apex handler is registered is flagged in its own row with Needs Apex handler. The flag clears on its own once you register one, and it never blocks whitelisting.
  • Refresh on a flow row now re-reads the variable contract and the trigger type together, so the two halves always come from the same read.

The Form Builder stays quiet about all of this on purpose — it is a configuration job, and only a configuration admin can see or fix it.

Nothing you already had changes

Flows whitelisted before this release keep working untouched, without re-whitelisting or refreshing: an entry with no recorded trigger type deliberately means "start it the original way".

Ordinary autolaunched flows still take the original code path. If you ever want a single code path for everything, Route all flows through this handler in Apex Handler Settings is the escape hatch — off by default.

Where to read more

Last updated: 2026-09-10