Skip to content
Flux Forms

Home / Admin setup

Apex Handler Settings

Register the class that starts on-demand flows, and the one permission everyone forgets.

For Salesforce administrators.

Flux Forms Setup → Apex Handler Settings is where you register the single class that starts on-demand flows on the submit engine's behalf.

Why this exists

A flow created with the "no trigger, invoked on demand" start cannot be started by Flux Forms directly — Salesforce does not allow a packaged application to start one. Flux Forms detects these flows automatically and runs them through an Apex class in your own org instead.

Nothing about whitelisting such a flow is different. The routing is automatic, and ordinary autolaunched flows are untouched by it.

The settings

Setting What it does
Flow proxy class The class that starts on-demand flows. Chosen from the classes in your org that implement the handler interface — you never type a name.
Handler active Switches the proxy on. With it off, on-demand flow actions fail with a clear message rather than calling a class you deliberately disabled.
Route all flows through this handler Sends every flow through the proxy, not just the on-demand ones. Leave it off unless you specifically want one code path for all flows.

The class name is validated before it is stored, so a class that has since been deleted is refused at save time with a readable message instead of sitting there waiting to fail during someone's submission.

Nobody has to write that class

A ready-made one ships as its own small package, Flux Forms Flow Proxy. Install it after Flux Forms and FluxFormsOnDemandFlowHandler appears in the picker.

A developer who would rather own the code can copy the class from the Flux Forms Flow Proxy source instead. Either way it ends up in your own org, where you are free to change it.

If the picker is empty, the screen names the interface to implement, fluxforms.SubmitActionApexHandler. See the global warning in Approve Apex handlers — a public class compiles and then never shows up.

The one permission that is easy to miss

Submit actions run in the background as the Automated Process user, and that user needs access to each on-demand flow before it will run:

A permission set with a Flow Access entry naming that flow, assigned to the Automated Process user.

The org-wide Run Flows permission is not a substitute, and no package can grant this for you — the grant has to name your flow, which does not exist when the package is built.

Putting it together

  1. Install Flux Forms Flow Proxy (or deploy the class).
  2. Here, set the Flow proxy class and tick Handler active.
  3. Whitelist the on-demand flow in Purpose Manager, exactly as you would any other flow. See Whitelist flows.
  4. Grant the Automated Process user Flow Access on that flow.

Miss step 1, 2 or 4 and the flow whitelists fine but fails at submit time, with the message naming this screen. Purpose Manager flags those rows with Needs Apex handler so you can see which entries cannot run yet.

Who can see this screen

Configuration admins only. Marketeers and builders do not see the tab, and are not shown warnings about it — registering the proxy is a configuration job they could not fix. See Getting access.

Last updated: 2026-09-10