A data-aware detective anchor hyperlink that looks like standard underlined body text by default, pulling specific row criteria parameters to compute dynamic page transfers.

• Navigating users dynamically to specific record detail views by extracting unique row variables from the current screen context (e.g., clicking a specific product row to go to its unique page).
• Building smart, data-aware text links inside tables, list rows, or informational cards that require identifier parameter interpolation.

Requires binding a relational query name source, choosing the underlying primary target identifier column, and passing an active evaluation expression to capture runtime row values.

A read-only single row duration string that outputs individual segmented time measurements separated by unit letters based on configuration toggles.

• Displaying specific time durations or elapsed period chunks (e.g., ‘3y, 5m, 3d’) cleanly in the interface.
• Rendering structured ISO 8601 duration intervals parsed from technical database columns into human-readable segmented blocks.

Accepts a raw ISO 8601 interval duration text string (e.g., ‘P3Y5M3DT3H3M3S’) or an expressional codebase script returning equivalent data logs. Alternatively can be hardcoded manually using individual numeric inputs across six chronological time parameter buckets.

A read-only interactive code viewer tree containing collapsible object nesting hierarchies and visual type-specific markers.

• Presenting structured data payloads, complex nested records, or configuration logs in a clean, expandable tree structure.
• Providing developers or administrative users with readable debugging viewports that indicate property data types (string, number, boolean) explicitly.

Sourced strictly through custom expressions capable of invoking direct structural data objects, dynamic API queries, or active field value references.

A short static caption, used to title a group of elements that have no heading of their own.

• Naming a section of a form or a block inside a Grid.

• A ‘Shipping address’ caption above an address block.

• Using it to label a single input — inputs carry their own label, and a second one is read twice by screen readers.
• Using it for values that change; it holds fixed text.

Use instead

A scrollable stack of repeated row cards (each built from one shared grid template), with optional row selection and a pagination footer.

• Browse many records as custom row cards — each row is a grid layout you design, not fixed columns.
• Build a selectable list that drives a detail panel, form, or chart from elements.<listId>.selected.
• Show compact work queues, catalogs, or pickers where a freeform row layout beats a dense table.

Requires a Data Source view/query name. Set Identifier Name whenever selection or per-row actions must address a specific record. Build the visual layout inside the single row → default_grid template.

A launcher button that opens an overlay with a title and close control.

• Open a secondary flow (edit dialog, confirmation, wizard step) without leaving the current page.
• Show a form, chart, or summary in an overlay launched from a button.

• A layout container for nested forms, charts, or confirmation content.

• A button that opens a medium dialog to edit related sub-form fields.
• An icon-only button that opens a full-screen analytics overlay.

• Nesting modals inside modals, which confuses focus and navigation.

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 compact, read-only numerical data text block that displays formatted integers or decimals alongside units, percentages, custom currency markings, and contextual error accent highlights.

• Displaying a read-only numeric value, score, index, metric, or currency value within user interfaces.
• Rendering financial tracking fields or statistical values that require explicit prefix/suffix symbols (e.g. £, €) or dynamic highlight gating for losses.

• A dashboard tile rendering a database revenue cell formatted with a currency prefix and bold red styling triggered on negative margins.
• Displaying a precise fractional calculation summary clamped cleanly via decimal precision configurations.

• Using to capture user numerical entries, use a form-bound number input control element instead.
• Allocating massive grid canvas dimensions, keep this small indicator element sized to 1 row tall and 1 or 2 columns broad.

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 button that calls a database function or procedure directly, for work that belongs in the database rather than in the page.

• Triggering server-side logic that would be wrong to express as a sequence of page actions — a batch recalculation or a state transition with its own rules.

The function must exist in the database and be callable by the signed-in user’s role; arguments are supplied from the page.

A dropdown whose options are typed into the configuration rather than loaded from the database.

• A short, stable list that is not worth a database view — a status, a priority, a yes/no/unknown.

• Priority: Low, Medium, High.

• Hard-coding a list that already exists as a table, which then has to be maintained in two places.
• Using it for long lists; without search the user has to scroll.

Use instead

A section of a parent form that edits a nested part of the same record, such as a JSON column or a related row, using its own child inputs.

• Editing a nested object inside one record, where the inputs should read and write below a shared field path rather than at the top level.

Binds to a field path on a parent Form. The inputs placed inside it address paths relative to that field, so they do not each need the full path.