Skip to content
Flux Forms

Home / Tips and best practices

Best practices

Habits that keep forms working months after you built them.

Naming and versioning

  • Use clear, stable Form Keys. Lowercase, unique, and permanent — the key can never be changed, and links you have sent depend on it. Prefer annual-survey over annual-survey-jan-2026.
  • Keep one Active Form Config per form. For substantive changes to a form already collecting answers, create a new version rather than editing the live one, so past submissions stay interpretable. See Forms and configs.

Purposes

  • Ask for the purpose before you build the form. Empty pickers in Data Mapping and Submission Actions are almost always a missing purpose, and you cannot widen your own access.
  • Ask for the narrowest purpose that works. Read access where you only prefill; edit access only where you actually write.

Branding

  • Duplicate before you tweak. Editing a shared theme changes every form using it. If a change is for one campaign, work on a copy.
  • Clear a colour rather than guessing it. An empty value keeps the design-system default, which is better than an approximation that drifts from the real brand.

Logic

  • Remember the two halves of "show only when". Check the field's Hidden toggle and add a Shown rule. One without the other does nothing.
  • Put specific rules lower. For field effects the lower rule wins, so the most specific rule should have the final say.
  • Never use logic as security. Language, branding and URL-parameter conditions read values the visitor can edit. Block stops someone in the browser, not on the server.
  • Re-check rules after editing a field's options. A condition comparing against a removed option silently never fires. Health flags it as a warning — read your warnings.

Text

  • Write real validation messages. "Enter a Dutch postcode, for example 1011 AB" beats "Invalid value" on every form, every time.
  • Give dynamic tags a default value. "Thanks, !" is worse than no greeting.
  • Translate only what differs. Blank falls back to the default language, so there is no reason to duplicate identical text.

Before you publish

  1. Clear the health errors — you cannot activate with any.
  2. Read the warnings anyway. That is where rules that never fire hide.
  3. Walk the form in the preview, in every language, on a stepped layout if it has one.
  4. Open the real link with Open Form. The progress bar and split-image layout only exist there.
  5. If it prefills, test a real generated link — and set Valid For (Days) on links you send out.

Last updated: 2026-09-10