An interactive input that can render as a checkbox, a switch, or a button with custom text labels, colors, and layout placements.

• User needs to toggle a binary value (true/false) or select a tri-state value (true/false/null) inside a form.
• Providing toggle switches, checkbox inputs, or toggle button behaviors for boolean form parameters.

Requires a parent Form context (default_form) on the page to resolve the Data Source connection (Element ID and Field Path).

A dynamic circular pie or donut chart visualizing categorical proportional shares, complete with slice value labels, customizable empty state colors, theme palettes, and interactive toolbox utilities (image export, clear selection, data view table).

• Visualizing proportional distributions, parts-of-a-whole relationships, or percentage share compositions.
• Displaying dynamic categorical datasets where each slice’s volume contributes to a total 100% sum.

Requires an active Source Query. Select a valid column property for Label (defines pie slices) and a numerical column for Value (defines slice volume). Every label field must map to a valid numeric value.

A read-only checkbox representing the output evaluation of a boolean expression.

• Presenting simple binary flags or states (true/false) to users.
• Evaluating conditional dynamic expressions that resolve to a boolean or null value.

• Displaying a read-only checkbox representing an active/inactive record state.
• Evaluating checkmark UI indicators using conditional true/false/null backend logic.

• Using for interactive form inputs where users need to check or uncheck a box to submit data, use boolean_input instead.
• Allocating large layout grid dimensions (e.g., spanning multiple rows or wide column blocks), keep this compact display element restricted to 1 row height and 1 to 2 grid columns.
• Writing complex string or object expressions in the booleanExpression textbox instead of resolving directly to boolean values (true, false) or null.

Configure these in the Application Designer property panel. Group headings mirror the editor where possible. Data Source is where the element gets its rows or field binding (a view/query, a connector operation, or a parent form field). References appear only for view-backed sources and map foreign-key ID columns to readable labels from another view.

A code editor bound to a form field, with syntax highlighting for the configured language.

• Editing a stored snippet, template or query where indentation and highlighting matter.

• Editing an email template stored on the record.

• Using it for structured JSON that should be validated — a JSON Input reports parse errors.
• Using it for short single-line values, where the editor chrome outweighs the benefit.

Use instead

A image display viewport with support for direct uploads, storage path resolution, custom URL expressions, click-to-expand full size previews, frame borders, and image fitting modes.

• Displaying static or dynamic images sourced from internal storage, uploaded files, or external URLs.
• Presenting visual assets with fit scaling controls (e.g., scale to fit, adjust to width/height, stretch) and full-size click-to-expand preview capabilities.

• Image URLs, relative storage paths, file system asset keys, or custom dynamic image expressions.

• A profile overview tile rendering a user avatar retrieved dynamically from internal storage paths with click-to-expand preview enabled.
• An image gallery asset display loading an external HTTPS image path with scale-to-fit formatting and frame borders.

• Squeezing image displays into tiny layout boxes — allocate at least 3 rows high and 6 columns wide for comfortable image viewing.
• Using as a file upload input element — use the storage_file_input component instead to allow user file selections.

Use instead

A row of buttons rendered as one connected control, so a set of related actions reads as a single choice rather than scattered buttons.

• Two or more actions that belong together and share styling, such as Save / Save and close / Cancel.

• The action bar at the foot of a form.
• A group of filter shortcuts above a table.

• Mixing unrelated actions into one group — the shared framing implies the buttons are alternatives to each other.
• Putting a single button in a group; place the button directly instead.

Pairs well with

A clickable colored input block covering its container area that launches a full popout color picker selection window when clicked. If configured, a plain uncolored label is rendered adjacent to the color block.

• Allowing users to pick a color visually using an advanced popup color picker panel.
• Binding user-selected colors as hex string data values within database records.

Deactivated by default. Requires an active connection to a parent default_form element via Element ID and Field Path attributes.