An interactive text input box that converts typed string entries into removable chip tags upon pressing Enter. Supports deleting individual tag chips or clearing all tags simultaneously.

• Capturing a collection or list of text strings (e.g., tags, keywords, email lists, categories) within a single interactive input field.
• Allowing users to type text strings, commit them as chip/tag tokens via the Enter key, and manage them individually (single deletion) or collectively (bulk clear).
• Binding array-of-strings schema properties to form data models.

Disabled by default until a default_form is present on the page layout. Requires selecting a valid Form Element ID and a Field Path targeting an array property (e.g. [’tags’]).

A robust, highly searchable dropdown input supporting multi-select chips, selection checkboxes, highlighting matching search terms, and virtualization for long option lists.

• User needs to select a single or multiple values from a long, searchable list of options.
• Populating form fields with dynamic options fetched via query operations (e.g., list of users, products, categories).

Requires binding configuration to a parent Form via elementId and fieldPath. Options are populated either through a dynamic backend query (requiring queryName, identifier, and label fields) or through static option definitions.

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 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 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.

An interactive date input text box featuring an inline calendar icon button that opens a visual popup date picker menu layer to capture user selections.

• Allowing users to select or enter a specific date, time, or complete timestamp within an interactive form.
• Configuring bounded calendar dropdown selectors with explicit past or future validation constraints (Minimum/Maximum dates).

Disabled by default until a valid default_form component is present on the page layout canvas. Requires pairing via Element ID and Field Path attributes.

An interactive, grid-based Geographic Information System. workspace dashboard featuring zooming dials, layers drag handles, polyline/polygon drawing anchors, and interactive element deletion triggers.

• Allowing users to draw, edit, and capture spatial map structures (points, lines, regions) within form views.
• Binding geographic coordinates or feature vectors directly into database records via standard GeoJSON structures.

Locked by default until paired inside a form frame context. Connection opens when clicking the ‘+’ data trigger to establish Element ID and Field Path references.

A comprehensive row layout containing six individual numerical text input boxes representing structural time blocks, accompanied by custom visual prefix or suffix icon adornments.

• Allowing users to explicitly input precise time durations or chronological spans broken down by individual units (years, months, days, hours, minutes, seconds).
• Capturing structured interval properties within a form grid context to update backend database columns.

Disabled by default until a default_form container exists on the page. Requires a valid Data Source pairing (Element ID and Field Path) to map selection variables back to form states.

An interactive code input interface container panel outfitted with structural workspace controls to append property objects, clear array items, edit dictionary keys, and copy data configurations.

• Allowing users to interactively construct, edit, and manipulate complex hierarchical JSON datasets inside a form context.
• Providing an interface for creating dynamic structural payloads where keys can be added, nested arrays built, or values assigned on the fly.

Deactivated by default until a default_form is present on the page layout viewports. Requires establishing a connection path linking Element ID and Field Path references.

An interactive multiline text input text box topped by a comprehensive horizontal toolbar containing visual shortcuts for H1/H2/H3 headers, bold, italic, strikeout text, hyperlinks, quotes, code text blocks, and embedded images.

• Allowing users to compose long-form prose with rich formatting tools (headers, lists, blockquotes, code blocks) inside forms.
• Gathering detailed user document descriptions, policy inputs, or technical comments that require rich shorthand markdown representations.

Deactivated by default until a parent default_form is established on the page layer. Requires explicit mapping references linking Element ID and Field Path attributes.