Repeatable Sections for Mobile Forms
Repeatable sections allow for certain sections of a mobile form to be repeated seamlessly and can have multiple use cases.
- On one hand, they can be used to include a variable number of entries in a form for the same set of questions (also known as multiple line items, like as in a spreadsheet). For example, in a work order form, parts that need to be ordered can be added as multiple line items under the same question.
- Repeatable sections are also useful for data collection where there are one-to-many relationships. For example, building inspection forms can use repeatable sections by auto-filling the number of floors of each specific building, along with the number of units per floor.
- And when creating forms such as employee requisitions, repeatable sections can be used in areas where multiple sections require the same set of questions, such as training record (company name, certificate, description, etc.) for several different employees.
In the above examples, repeatable sections improve form building efficiency by allowing you to build a single copy of a set of questions and then quickly clone or re-use them.
Improving the User Experience with Repeatable Sections
Repeatable sections allow mobile users to collect data in a more structured way, while also providing more attractive-looking and efficient forms.
In many mobile apps, repeatable sections provide a clean and easily read template that includes important information such as:
- Form name
- Page name
- Repeatable section header
- Summary tables
- Summary table headers
- A footer
In the work order form use case, entered line items are also typically laid out in a summary, allowing mobile users to easily review forms and spot potential errors or omissions, or quickly review total costs and quantities.
Nested repeatable sections, which are essentially repeatable sections within other repeatable sections, can also be created. To return to the building inspection example, the number of floors per building is one repeatable section, while the number of units and types of unit per floor are nested within the floors section.
These nested sections are typically arranged as parent-child relationships. In the above example, units are a child record of floors, and floors are a child record of the building.