DynamicForm Start free trial
Step 8 of 15 · Render Engine · topic 2 of 3

How it works

How does the Render Engine work?

One definition, two screens

The mobile renderer interprets the shared screen configuration. Fields stack vertically, and panels and tab sections become expandable sections. Repeating entries and nested sections remain connected to their parent entry. The presentation changes to suit the device.

Drawn for the step and the person

The same screen shows sections as editable, read-only or hidden depending on the process step and the user's role.

Checked before go-live

Desktop and mobile preview, an Issues list that blocks broken saves, and a Test condition panel for rules.

Protected on the server

Every submission is re-checked, so a changed or outdated form cannot save data it is not allowed to.

Works without signal

On mobile, forms are stored on the device, queued and sent when back online, with a receipt for each submission.

One screen, three views, set by role and stepThe same three-section case screen seen by a sales officer, a credit officer and an approver: sections are editable, read-only or hidden for each.Sales officerApplicantFinancialsHiddenCredit officerApplicantFinancialsCredit memoApproverApplicantFinancialsCredit memoEditableRead-onlyHidden
The same screen through three coloured lenses — three roles — each revealing different sections.
Problems are caught before anyone uses the screenAn Issues list with two problems — a missing field code and a rule pointing at a deleted field — is fixed and turns into 'Ready to save'; a condition test below reports a match.Issues (2)!Missing field codeCo-applicant · Mobile!Rule refers to a deleted fieldGST number · RequiredfixIssues (0)Ready to saveTest conditionGST registered = YesMatches
An Issues list with two red items fixed and turning green; a condition test showing 'matches'.
Field work continues without signalA field officer fills a form, loses signal and the forms wait in an outbox; when the signal returns they are sent and each gets a receipt.No signalBack onlineOutbox3 waiting1 · Fill the visit form2 · Saved to the outbox3 · Sent, with receipts
A phone losing signal, forms stacking in an outbox, then syncing with receipt ticks.
Example · Customer Loan Origination

In the loan example, the credit memo is hidden from field sales, editable for the credit officer and read-only for the approver — one screen, three views.

See the full loan example

How the mobile interpretation works

Sections and entries

The current Flutter renderer presents panel and tab sections as accordions, with fields stacked vertically. Repeating sections provide add/remove actions; child sections are rendered within the relevant parent entry.

Rules and calculations

The mobile runtime evaluates configured visibility, required-field and read-only rules, portable calculations and dropdown dependencies. Your team should preview and test the configured behaviour on both devices, especially when using technical extensions.

Planning and rendering

AI Core proposes web and mobile layouts as part of the reviewed application design. The mobile runtime interprets the published screen configuration; a proposed layout is not a guarantee that every planning option appears unchanged on the phone.

Embedded content

Yes. Technical teams can use an embedded-content container and a lifecycle script to mount a specialised component in a web screen. This extension requires technical configuration. Android renders HTML content and links; it does not automatically run the same web component scripts.

Build your first app free

All platform features, hosted by us for 120 days. For testing and evaluation, subject to our Fair Use Policy.

Explore DynamicForm

Compliance · Rules and calculations

Updated 16 November 2026