A read-only typography block formatting timestamps into absolute patterns or descriptive human-readable relative timelines.

• Presenting a read-only date, timestamp, or temporal string formatted cleanly for user viewports.
• Displaying historical records or future milestone markers utilizing relative time statements (e.g., ‘6 years ago’).

• ISO timestamps, Date objects, or string representations processed dynamically via custom expressions.

• Displaying a record creation timestamp as ‘dd.MM.yyyy HH:mm’.
• Rendering audit track histories using relative phrase transformations like ‘3 days ago’.

• Attempting to capture or mutate dates, use input-based date selectors instead.
• Enabling both ‘Is Relative’ and specialized absolute ‘Custom’ formats simultaneously, as relative processing completely overrides layout format specifiers.

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 single-select option group outputting a string, rendered as a list of circular radio indicators or interactive toggle buttons aligned vertically or horizontally.

• Allowing users to select exactly one option from a small, clear set of mutually exclusive choices.
• Presenting discrete categorical choices visually using classic radio indicators or segment toggle buttons.

Deactivated by default until a default_form is present on the page layout. Requires a valid Data Source connection (Element ID and Field Path) to store the selected option string.

A button that deletes the record it is bound to, optionally behind a confirmation dialog.

• Removing the record shown by the surrounding form, or the row it sits in inside a table body.

Needs a record to act on: either the parent form’s record, or the row it is placed in when used as a table body element.

An interactive draggable thumb slider moving along a horizontal or vertical line track, featuring optional value tooltips, customizable step increments, and mark indicators.

• Allowing users to select a numeric value smoothly along a bounded continuous track by dragging a handle.
• Providing intuitive numeric controls for adjustments like volume, distance, budgets, or percentage scale settings.

Disabled by default until a default_form is present on the page layout. Requires a valid Data Source pairing (Element ID and Field Path) to store the numeric output.

An interactive underlined text hyperlink that routes the user to a targeted external web address upon click. It can optionally be visually transformed to look exactly like a standard platform action button.

• Navigating users away from the current platform application to external domains, websites, or foreign reference pages.
• Providing links to external support portals, external documentation, or static downloadable web assets.

• An underlined text link pointing out to a vendor’s external terms of service dashboard.
• A button-styled link redirecting administrators directly to an external server management console.

• Navigating to another page inside the exact same app workspace — use internal link buttons or routing options instead to preserve application state.
• Omiting required transfer protocols (such as http:// or https://) inside the Destination property string, which causes broken or dead paths.

Use instead

An editable grid of related records inside a parent form — the way to manage a one-to-many relationship without leaving the page.

• Editing the many side of a relationship in place, such as the lines of an order, where rows are added and removed alongside the parent record.

Binds to a field path on a parent Form that holds an array of rows. Rows are saved with the parent record, not independently.

A form layout for one record, with Back, Reset, and Save in the bottom bar.

• Create, edit, or show a single database record with inputs bound to its fields.
• Provide the data context that child inputs bind to via Element Id and Field Path.

Needs a Data Source (query name). Edit and detail also need Identifier Name and Identifier Value.