Skip to content
Flux Forms

Home / What's new

What's new in 0.7.0

Form Health with a publish gate, conditional branching, drag fields across sections, and a standalone Brand Builder.

Flux Forms 0.7.0. Highlights first, then the smaller changes.

Form Health, and a real publish gate

A new Health section at the bottom of the Form Builder sidebar checks a form before it goes live, with live Errors and Warnings counts.

You can no longer activate a form that has errors. The Activate button stays disabled and tells you how many to fix. The same check runs on the server, so it holds outside the builder too.

Warnings cover reachability problems that used to fail silently — a field set to start hidden with no rule that could ever show it, a condition comparing against an option that no longer exists, an empty section. Clicking a row jumps you to the scope where you can fix it, and the Data and Translations scopes highlight what is missing.

See Form health.

Conditional logic can now branch

Three new rule outcomes steer where a visitor goes rather than changing a field:

  • Go to section — jump forward, skipping the sections in between.
  • Submit the form — end the form early.
  • Block (go to end screen) — a dead-end for a visitor who does not qualify. Nothing is submitted.

These are also evaluated on load, so a personalised link that already determines the outcome does not make the visitor click through first.

Rules are now reorderable by drag or keyboard, which matters because order decides conflicts: for field effects the lower rule wins, for flow actions the first match wins. Conditional action labels are consistent across the editor.

See Flow actions.

New condition sources

Conditions are no longer limited to field answers. A rule — in Conditional Logic or End Screens — can now test:

  • Language — the language the form is shown in
  • Branding — the b value on a brand-specific link
  • URL parameter — any other value on the link

So Language Equals Nederlands → Require the VAT-number field is now a rule you can write.

These read values the visitor can edit. Use them to present a form, never to protect anything.

Drag fields across sections

Field drag-and-drop is no longer confined to one section. Drop a field on another section's field to place it there, or anywhere in that section's body to append it — which also works for an empty section. The field keeps its label and its conditional-logic rules when it moves.

See Sections and fields.

A standalone Brand Builder

Branding has moved out of the Form Builder into its own Brand Builder, reached from the Brand List tab or Manage brands. It works the same way as the Form Builder: scopes on the left, editor in the middle, live preview on the right.

  • The Brand List now shows each theme's Name, a default tag, and its Last Modified Date, with row actions for Edit, Set as default, Duplicate and Delete.
  • The preview has a Form layout dropdown, so you can check a theme against the stepped wizard chrome — step indicator, Back and Next — without touching a form. It only affects the preview.
  • Open Form (previously named differently) is now a shared dialog used from both builders: from the Brand Builder the theme is fixed and you pick the form; from the Form Builder the form is fixed and you pick the theme.

See Brand Builder.

Dynamic tags

Your wording can now show a value the visitor entered. Insert field value in the editor footer adds a tag to end-screen headings and messages, section titles and descriptions, and field labels, help text and placeholders — with an optional default for when the field is empty.

Section descriptions, help text and end-screen messages are now rich-text fields (bold, italic, lists, links; no images).

See Dynamic tags.

Data mapping: prefill lock

A field mapping's lock is now an explicit Enabled / Disabled picklist rather than a toggle, so it is clear whether a prefilled value is the visitor's to change. Disabled shows the value locked and read-only.

See Data mapping.

Smaller changes

  • Conditional operators are gated by field type, so a date field no longer offers text operators.
  • Language picker labels are friendlier for locales that have no display name of their own.
  • A theme's corner radius now drives every surface consistently, and a logo is pinned to the top of the form.
  • Picklist placeholders are translatable, and a default value must be one of the field's own options.
  • Fixed: a multi-option checkbox field could crash the preview.
  • Builder layout polish: section cards and the progress indicator are spaced properly in the preview, and image-picker button rows line up with their field labels.

Last updated: 2026-09-10