Forms and workflows
Design reusable forms, conditional experiences and server-backed workflows without a bespoke front end for every page.
Form definitions are application assets
A form definition contains the component tree and Tailwind candidates. Form metadata controls its name, type, anonymous access, data mapping, action chains and future lifecycle configuration. The Designer edits the definition; the Viewer renders it through the shared Vue runtime.
Input, layout and collection controls
Use text, number, date and date-time inputs, checkbox, radio, dropdown, AsyncSelect, Tree and file controls for data. Use Div, Form Group, tabs, pagination and GridLayout for layout. Use DataGrid and ItemRenderer for collection data, including cursor paging and search where supported.
Validation and rules
Required validation and custom validation are separate. Error CSS classes apply to the failing control, while custom validation messages can be positioned independently. Rule settings provide one place to review visibility, read-only, required and hidden behavior. Validation runs at deliberate interaction points and text inputs are debounced.
Actions and navigation
Events invoke client action chains or approved server actions. The runtime receives form data, route, user and stable application context. Submit actions can redirect to a newly created record or a configured target. Hidden controls are not submitted.
Learn how fields reach database columns in data models and ORM, or use the developer guide to build a first workflow.