Skip to main content
Version: 1.28 (Current)

Forms 2.0 - Settings

caution

This page is preliminary and subject to change as Forms 2.0 continues to be developed.

The Settings tab of the Form Builder holds form-level configuration - as opposed to the Build tab's per-field settings.

forms-2-0-form-builder-settings.png

General​

  • Active Condition - a server-side expression controlling whether the form is active at all (for example [HasRole:registeredUsers|true]). Supports Tokens.
  • Initially Visible - whether the form renders directly on the page (Inline, checked) or stays hidden until something opens it, such as a button action or the Javascript APIs (Popup, unchecked).
  • Form CSS Classes - one or more CSS class names, separated by spaces, applied to the form's root element. Supports Tokens.
  • Show Loading Animation - shows a loading animation while the form initializes.
  • Debug Mode - shows the form's compiled configuration and additional debug logging, for troubleshooting.
  • Enable Auto Save Drafts - see Autosave and Drafts below.

forms-2-0-form-builder-settings-general.png

note

A form's steps aren't set up on this tab. The step navigation settings, such as Step Mode and Allow Users To Navigate, are on the form's root container on the Build tab. See Navigation settings.

Localization​

Enable Localization is available once the form has been saved, and only on sites with more than one language. Once checked, it unlocks:

  • Download POT - exports a template of the form's translatable text (labels, hints, and other localizable text).
  • Download <language> PO - exports the current translations for a given site language.
  • Load PO - imports translations from a PO file. Imported translations are staged and only saved when you save the form.

Once localization is enabled, a language switcher appears in the Canvas toolbar on the Build tab, letting you preview the form in any site language and flagging fields with missing translations. See Localization on the Overview page for the end-user-facing behavior.

forms-2-0-form-builder-settings-localization.png

Events​

Three panels let you attach a stack of Actions to run at different points as the form loads. Each panel offers Add Action, Paste, and Import Action to build up its list of actions. For the full order of events and what each can do, see Lifecycle.

Some actions aren't offered in these events, because they only make sense after the form is on screen. The refresh actions and Ask for Confirmation are only available on buttons, and the Dynamic Fields actions only in On Preinit.

note

There's no separate "on submit" event here. Submission logic - what happens when a user submits the form - is attached to a Button's On Click Handler, not configured on this tab.

On Page Load​

Runs on the server when the page containing the form loads, before the form's fields exist. Use it to redirect the user, for example to a login page. Its tokens aren't available in the later events.

forms-2-0-form-builder-settings-on-page-load.png

On Preinit​

Runs before the form's fields are initialized - use this to load data you want available while fields are being set up.

  • A token created here with a field's name becomes that field's starting value, replacing its Initial Value. For example, a token Email fills the Email field. A field inside a Section uses its full name, such as Billing:City.
  • The list named in a Repeater's Initial Entries is read after this event, so create it here.
  • The Dynamic Fields actions, which add fields to a Dynamic Container, only work here. See Dynamic Forms.

Also offers a Persist data for submit checkbox with a Data Keys list, to carry specific pieces of data from these actions through to the form's submission. List one token name per line. The tokens are kept in the form's encrypted state, so the user can't read or change them. See Keeping data until submit.

After Fields Initialization​

Runs after the form's fields have been initialized. Every field's starting value is available as its token, for example [Email].

Also offers a Persist data for submit checkbox with a Data Keys list, to carry specific pieces of data from these actions through to the form's submission.

Autosave and Drafts​

Enable Auto Save Drafts (in General above) turns on automatic saving of a user's in-progress answers to a draft, stored in their browser, as they fill out the form - see Autosave / Drafts on the Overview page. It's off by default. If you enable it, also add a Clear Draft action (typically on successful submission) so completed submissions don't leave a stale draft behind. Only a Cancel button removes the draft on its own. See Saving Drafts for how drafts work and their limits.

Migrating an existing form​

When a Forms 2.0 form is created via the classic Form module's Migration Plan (see Migrating from the classic Form module on the Overview page), opening it in the Form Builder shows a banner reminding you to review the migrated settings before saving.

Use the original Migration Plan report as your checklist: anything marked Migrated carried over as-is, but anything marked Migrated with warning, Transformed, or Skipped should be double-checked here in Settings (and on the Build tab for fields) before you rely on the new form. See Migration from Action Form for the full process.

Javascript APIs​

Forms 2.0 exposes a JavaScript API (paa.form.show/hide/reinit) for showing, hiding, and reinitializing a form from your own scripts - useful when a form's Initially Visible setting is set to Popup. See Javascript APIs for the full API.


Last updated: November 19, 2026