Inflow.aiDocs

Optional technical reference. This material is for developers, integration specialists and platform administrators. For the consultant lesson, read the practical guide.

Preserved from source baseline d4587c7c0e073e58c2d430342f65ac55dd701bf4; source/static examples retain their stated scope. They are not new runtime verification or required consultant setup steps.

3. The control library

Select a control by its job and contract

Layout controls organize; inputs capture typed answers; data controls need an executable source/adapter; display and tracking controls explain admitted values; navigation/actions express deliberate intents. The generated Node reference contains the current authorable properties/defaults/events. Its closed wire-vocabulary appendix also lists structural/compatibility types that are not standalone palette choices.

A sample design seed is useful for arranging a page. It is not an employee's real task, a saved record or a certified analytic result. Choose a concrete business interaction first, then confirm its binding, data shape and permission behavior.

Example UIAI-CH03-01 — Choose typed answers for the leave form

Scenario and inputs. Mohammad must enter two calendar dates and a reason; Sara will later review them through a separate task. Nadia owns the form draft and knows the target rule expects separate startDate, endDate and reason fields.

Procedure. Choose Date, Date and TextArea rather than three generic text boxes. Give each an understandable label, bind it to the declared compatible destination and configure required validation. Compare DateRange only if its actual structured value shape matches the downstream contract. Use a Select for a controlled leave category when the admitted category list is explicit, retaining stable values separately from translated labels.

Expected result. The captured types and field identities match what the later rule expects. The control reference explains available options instead of suggesting that any property can be attached to any node. A changed answer does not automatically execute a data mutation or complete the manager's task.

Failure and recovery. Repair incompatible destinations or unsupported option values through the native property editor. Do not quietly coerce a structured selection into a display string or submit a translated label where a stable key is required. A missing category source stays unavailable until its actual owner/configuration is admitted.

Sources. Typed control/property selection, binding compatibility/catalog, closed vocabulary.

Example UIAI-CH03-02 — Separate a task list from the task work surface

Scenario and inputs. Sara should see admitted assigned work and open a real leave-review task. Nadia has configured the current task source and has the actual selected task ID. A generic table row or copied task title is not sufficient authority to perform work.

Procedure. Use a supported data/list adapter for task discovery, then place a native TaskViewer in the intended supported composition. Supply taskId from the actual selected result and choose perform or readOnly deliberately. Let the authenticated host and task row select the form, participants and output constraints. Keep authored children and arbitrary form/workspace overrides out of the opaque viewer.

Expected result. Discovery and performance are separate contracts. A readOnly viewer shows metadata rather than a disabled-looking executable form. A perform viewer admits claim/input/completion only where the current person is allowed, and actual completion is observed through its canonical receipt/event path.

Failure and recovery. If the task disappears or participation is revoked, preserve unavailable behavior and avoid unauthorized detail requests. Do not render a fake form, change taskId to a guessed value or turn a model's recommendation into a completion. Diagnose actual task/source ownership with the responsible operator.

Sources. TaskViewer authoring properties, runtime-owned task host, task events.

A guide to the Toolbox groups. The tables below illustrate common controls; the additional choices listed in each group also ship in the current palette. For the maintained detailed inventory, see Toolbox controls. The Node type reference is regenerated from the current authorable property/default/event contract.

Tip: hover any toolbox item for a live preview and a one-line description. Use the search box at the top of the Toolbox to filter by name.

Layout

Containers that arrange other components.

Control What it does
Stack Lays children in a row or column with a gap.
Grid A multi-column grid; set the number of columns.
Columns Splits its children into side-by-side columns.
Section A titled group of components.
Card A titled, bordered surface.
Tabs Tabbed panels.
Toolbar A horizontal bar for actions.
Divider A horizontal rule.
Spacer Blank space for breathing room.

The current Layout group also includes Accordion, Stepper, Modal and Drawer. A layout container is a node inside an interface, not the retired Container screen kind.

Controls (inputs)

The typed fields a user fills in.

Control What it does
Text A single-line text field.
Text area A multi-line text field.
Number A numeric field with optional min/max.
Select A dropdown of choices.
Checkbox A single on/off toggle.
Date A date picker.
File upload Upload one or more files.

Additional current inputs: Rich text, Email, URL, Phone, Password, Search, Integer, Decimal, Currency, Percentage, Slider, Multi-select, Radio group, Checkbox group, Segmented control, Combo box, Toggle, Time, Date and time, Date range, Tree select and Image upload. Their validation, formatting and data-access constraints remain control-specific.

Data

Controls that show or edit collections and records.

Control What it does
Data grid / Editable grid A grid of rows over a data source (read-only / editable).
Lookup Pick a related record (a record picker).
Tree grid / Pivot grid Hierarchical / pivoted grids.
Repeater Repeats a template for each item in a collection.
Table A simple table with defined columns and rows.
Record view Shows the fields of a single record.
Chart A line / bar / area / pie / scatter chart.
Metric A single headline number with a label.
Subform Embeds another form’s fields.

Document browser uses the governed Documents library. Advanced Visualization has its own visualization contract. Their presence in the Data toolbox does not make them generic rule-result consumers. Connect data enables only the sources and operations supported by that control; a catalog category is not execution permission.

Display

Read-only presentation.

Control What it does
Heading A section heading.
Prose A paragraph of text.
Image An image.
Badge A small status/label pill (50+ presets).
Control What it does
Nav menu A navigation menu. Only shown on App Shell interfaces.

The Navigation group also includes App header, Target area (ContentOutlet), Embedded interface and Task viewer. A Task viewer opens an authorized existing task and its pinned form; it does not create a second task lifecycle or grant access.

Actions

Control What it does
Button A button (primary / secondary / danger / quiet variants).
Link A hyperlink.

Tracking

Read-only components that visualize process/task status. They render immediately with sample data and can be bound to a real process, task, or data source. See Tracking controls for details.

Progress Bar · Step Progress · Timeline · Status Badge · Current Step Card · SLA Indicator · Task Assignment · Process Summary · Approval Trail · Tracking Table · Tracking Header.


Next: Properties & data →

Try “document generation”, “integrations” or “first form”.