Learn how to configure the Boolean component in Praxsuite forms to collect yes/no or true/false responses. Customize labels, display modes, default values, and validation while storing structured boolean data in your associated table.

The Boolean component is used to collect binary responses, meaning answers that have only two possible values such as Yes/No, True/False, Approved/Rejected, or Active/Inactive.

This component is commonly used in approval workflows, confirmation fields, eligibility checks, and operational flags.

Boolean values are stored in the associated table as true/false data, which makes them useful for filters, automation rules, and dashboards.

Basic configuration

Associated Table

Selects the table where the form submission will be stored.

Associated Column

Defines the table column where the boolean value will be saved.

This column must be a boolean-type column in the associated table.

Label

Defines the field name displayed in the form.

Example:

Approval status

Description

Optional helper text displayed below the field to explain the meaning of the selection.

Example:

Select Yes if the request meets the approval criteria.

Font

Defines the typography used by the component in the form.

Boolean value labels

Label for “True”

Defines the text displayed when the value is true.

Example:

Yes

Label for “False”

Defines the text displayed when the value is false.

Example:

No

These labels can be customized depending on the workflow.

Examples:

Display mode

The Display mode setting defines how the boolean choice appears in the form interface.

Available options include:

Single toggle

A single switch that toggles between true and false.

Separated toggle

Two separate toggle options representing each value.

Single checkbox

A checkbox representing the true value when checked.

Separated checkbox

Two independent checkboxes for each option.

Selector

A selector-style input allowing users to choose between the two values.

The appropriate display mode depends on the form design and user experience requirements.

Field behavior settings

Visible field

Controls whether the field is visible in the form.

When disabled, the field is hidden but may still be used internally.

Allow clear

Allows the value to be reset to null or undefined.

This creates a third possible state beyond true or false.

Has default value

Enables setting a default value that appears when the form loads.

Example default values:

True
False

This is useful when most submissions start with a predictable value.

Required field

When enabled, the user must select a value before submitting the form.

This ensures the field cannot remain empty.