Skip to main content
Version: 1.28 (Current)

Forms 2.0 - Section

caution

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

A Section groups related fields under a title and gives them one value: a JSON object with the values of all the fields inside it. Use a Section for a block of the form that belongs together, such as Billing Address or Emergency Contact.

forms-2-0-form-builder-build-section-render.png

A Section differs from a Layout Container in four ways:

SectionLayout Container
Has a valueYes - a JSON object of its fieldsNo
Prefixes the names of its fieldsYes - [Section:Field]No - fields keep their own name
Shows a titleYes, unless Show Title is offNo
Can be a Validation ScopeYes - Parent ContainerNo

Use a Layout Container when you only want to arrange fields. Use a Section when the fields form a unit you want to read, save, or validate together.

Adding a Section​

Drag the Section tile from the field palette onto the Canvas, then drag fields into it. See Build for more on adding and arranging fields. The Section's Label is its title.

Parameters​

Only Section-specific parameters are listed below. See Common Field Settings for the settings shared with other field types.

FieldDescription
Show TitleWhen on (the default), the Section's Label is shown above its fields.
Layout ModeVertical (the default) and Horizontal arrange the fields automatically. Manual allows free placement and resizing in a mosaic layout. Can be set per form width.
ColumnsOnly shown in Manual mode. The number of columns in the mosaic layout. Default 4.
AlignmentOnly shown in Horizontal mode (Top/Middle/Bottom, default Bottom) or Vertical mode (Left/Center/Right, default Left). Can be set per form width.
GapSpacing between the fields: Inherit (the default, uses the parent container's gap), Compact, Normal, or Loose. Can be set per form width.
PaddingThe padding around the fields, in CSS units. Default 8px 0px. Can be set per form width.
Root CSS ClassesOne or more CSS class names, separated by spaces, applied to the field's root element only. Supports Tokens.

Settings that change with the form width​

Layout Mode, Alignment, Gap, and Padding can have a different value for each form width. Click the device icon next to the setting to switch it to responsive values, then set a value for Narrow (under 768 px), Medium (768 to 1199 px), and Wide (1200 px and over). The setting's title shows which width you are editing, for example Layout Mode (Narrow width). The width is the form's own width, not the browser window's, so a form in a narrow column uses its Narrow values even on a wide screen. Click the icon again to go back to one value for all widths.

Field names inside a Section​

A field inside a Section is addressed by its full name: the Section's Name, a colon, and the field's Name. If a Section named Billing holds a field named City, that field's token is [Billing:City]. Use the full name everywhere you refer to the field: in tokens, conditions, actions, and the JavaScript APIs.

Names nest. A Section Address inside a Section Billing gives its fields names such as [Billing:Address:City]. Layout Containers and Dynamic Containers in between don't add anything to the name.

Because of the prefix, two Sections can each hold a field with the same Name, for example [Billing:City] and [Shipping:City].

Common settings that apply to Section​

A Section supports these Common Field Settings:

  • General (Label and Name - Section does not support Hint)
  • Active
  • Visibility settings
  • Enabled settings

Hiding or disabling a Section hides or disables every field inside it. A Section that isn't Active isn't included in the form, and neither are its fields.

Section does not support Field Automations or Field Validators. Validation runs on the fields inside it.

Tokens​

TokenDescription
[SectionName]A JSON object with the values of all the active fields inside the Section, keyed by each field's own Name (not the full name). A nested Section appears as a nested object. Fields inside a Layout Container in the Section appear directly in the Section's object.
[SectionName:FieldName]The value of one field inside the Section.

For example, a Section Billing with the fields Street and City, and a nested Section Contact with the field Email, gives:

{
"Street": "1 Main St",
"City": "Cluj",
"Contact": { "Email": "ana@example.com" }
}

The whole form's values are available as [FormData], in which each Section appears as a nested object in the same way.


Last updated: November 18, 2026