Build inspections, intake, and service requests into your own product. Design visually, show the right questions, and send answers into your process.
WCAG 2.2 AA support, built in.Supported out of the box in reviewed Form Builder configurations.View Form Builder accessibility status
For OutSystems teams: replace standalone tools and repeated custom development inside the platform you already use.
Bring connected site inspections and maintenance checks into your OutSystems app. Try this form: flag an issue to reveal the follow-up question.
A separate tool for collecting field data.
A form connected to your existing records.
Try the live Form Renderer playground.
Interactive sample · Answers stay on this page.
Reuse one OutSystems builder and renderer for IT requests, supplier onboarding, and customer intake. Store form definitions as data and share entities and APIs where your design allows.
A separate form screen, entity and API method for each questionnaire.
Shared OutSystems screens and services, different form definitions.
Embed a guided request or registration flow in your OutSystems portal, then connect submissions to your own service and confirmation process.
Send visitors to an unrelated form service.
A consistent journey from first visit to request.
With BluKavantUI, reuse one screen and one entity across your forms. Connect a generic API or service action to handle submissions and email.
WITHOUT BLUKAVANTUI · PER FORM3 AOs per form × $180–$200 per AO$540–$600 per form, per licence period.
Explore BluKavantUI for OutSystemsNew forms are records, not new screens. Keep the complete definition in one RawJson Text field and load it by FormId.
Store OnSaveRequested.DefinitionJson in RawJson, then acknowledge the save.
Load RawJson into DefinitionJson on the same FormRenderer. Pages and conditions travel with it.
FileUpload fields support drag/drop and Browse. One shared upload endpoint returns durable file references for ValuesJson.
Read the OutSystems save, reload & attachment guide →
The definition contains the form layout and rules; ValuesJson contains answers and attachment metadata. File bytes stay in your application's storage. Configure UploadUrl on the renderer, authorize each upload and response, and acknowledge saves only after they complete.
The published native demo stores definitions, answers and actual file bytes in OutSystems. Its shared Binary upload endpoint returns a durable Id after storage; Multipart remains the default for existing integrations. New form definitions reuse the same screen, entity and integration; shared platform objects still count under your licence.
Download the complete OutSystems setup and event mappings ↓
Visual composition
Multi-page forms
Conditional questions
Validation rules
Reusable renderer
Drag-and-drop uploadsForm Builder and Form Renderer provide visual design, conditional questions, and a web answering experience. Your app provides storage, authentication, and workflows. FastField also offers offline mobile collection; offline sync, native device features, dispatch, and report generation need separate implementation and validation for a replacement.
Compare FastField mobile capabilitiesTry the component, explore the source, and connect your own process.