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

Tabs on a laptop become a scrolling form on a phone. Saved changes reach users the next time they open the screen.

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

Build your first app free

Up to 10 users. 30 days to build, then 30 days live after go-live.

Updated 30 September 2026