E-Form Pages
Pages break a form into sections. A long form on a single page is hard to read and harder to finish; the same form split across four pages gives the user somewhere to stop, and gives you somewhere to put a natural break in the questions.
Pages are managed in the Pages panel at the foot of the designer's left-hand side. Selecting a page shows its settings in the properties panel on the right and shows its fields on the canvas.
Working with pages
The Pages panel offers seven actions, on the panel itself and on each page in the list:
- Add Page - Adds a new empty page at the end.
- Copy Page - Copies the page so it can be pasted into this form or another one.
- Cut Page - Removes the page and holds it for pasting elsewhere.
- Paste Page - Pastes the page that was copied or cut. It appears once something has been copied, both on the panel and on each page, so the page can be placed where you want it rather than always at the end.
- Duplicate Page - Places a copy of the page directly after it. The quickest way to build a second page that is mostly like the first.
- Merge with Previous Page - Moves this page's fields onto the page above and removes it. Use it when a split turns out to be unnecessary, rather than moving fields across by hand.
- Delete Page - Removes the page and everything on it.
Pages can also be dragged up and down the list to reorder them.
Page settings
Page Name - The name of the page. It is normally only seen in the designer. It is shown to the user when the form is set to display its pages as tabs, in which case the name is the tab's text.
Page Icon - An icon for the page. It is shown in the designer, and on the tab when pages are displayed as tabs. It is worth setting for a tabbed form that will be used on a phone: on a narrow screen a tab with an icon shows only the icon, so a tab with no icon and a long name is what makes a tabbed form awkward on mobile.
Field Spacing - The vertical space between the fields on this page, from 0 to 100. Leave it at -1 (Unset) to use the form's own spacing. Setting it here overrides the form for this page only.
Font Family, Font Size, Font Color and Background Color - Override the form-level settings of the same names for this page. Leave them alone unless a page genuinely needs to look different; a form styled page by page is difficult to restyle later.
Custom Container Style - Styling in object notation applied to the page's container, for what the settings above do not cover. Use it sparingly.
Lock When Form Locked - When a form is set to lock after saving, every page locks by default. Turn this off on a page that should stay editable after the first save. That is what allows a form to be completed in stages by different people - the applicant fills in and locks their pages, while the reviewer's page stays open.
Hidden When - Hides the page when a condition is met, using the same builder described in Field Conditions. A hidden page is shown with a line through its name in the designer, and for the user it is as though it does not exist: Next Page and Previous Page skip straight over it.
How users move between pages
By default the user moves through the pages with Next Page and Previous Page, which skip any page hidden by a condition.
A form can instead display its pages as tabs, set with Display Pages as Tabs in the designer's Quick Options. The pages then appear as a row of tabs across the top of the form, using each page's Name and Icon, and the user can move between them in any order. Choose tabs for a form whose sections are independent, and the default paging for a form worked through from beginning to end.
Scroll to Top on Page Change, in the form's Display Settings, returns the user to the top of the form when the page changes. It applies to the default paging, not to tabs.
Pages or a Tab Container?
Both split a form into sections, and they behave differently in one way that matters.
Pages are the real division: only the current page is on screen, the user moves between them with the form's own navigation, and a page can be locked or hidden on its own.
A Tab Container is a field that holds tabs inside a single page. Everything in it is loaded at once, so values from every tab are available to conditions and actions immediately - but fields inside a tab that is not showing are not computed, so a calculated field inside a tab must depend only on that same tab.
Use pages for the main structure of a long form, and a Tab Container for a group of related sub-sections within one page.