Submitted forms consultation and export
All user submissions are available in the submitted forms area. This section acts as a centralised history, allowing teams to review responses, view details, remove test records and export data for external analysis.
Overview
The submitted forms area works as a central operational history. Its value depends directly on the quality of the form architecture, internal naming and the way fields were designed for reading and export.
Submission review
History, detail and triage
Submission consultation view, with operational list, history, and reading of sent records.
Reading the submissions list
- Each record shows the form name, submission date and available actions.
- This view should be used as an operational triage panel.
- The visible columns in this table should have been defined earlier in the form setup.
- Test records should be removed so they do not pollute the history.
Detail view
- When opening a submission, the team can see the values entered in each field.
- This view is useful for validation, follow-up and confirming attachments.
- Quick reading depends on the quality of internal names and selected columns.
Search, filters and pagination
Triage in high-volume scenarios
With many submissions, the ability to search, filter and paginate becomes essential. Even with a simple interface, triage depends on the team’s understanding of form naming and the key fields being monitored.
Excel export
Reporting and external analysis
Exporting makes it possible to analyse data externally, generate reports, share with teams or integrate with other workflows.
- Unclear machine names result in files that are difficult to interpret.
- Redundant or poorly structured fields compromise reporting.
- Free-text values reduce comparability.
- Hidden fields and query parameters can be extremely useful when properly documented.
Data maintenance best practices
History and export quality
Before publishing
- Always test exports in critical forms before publishing.
- Define a naming convention before building complex forms.
In daily operations
- Clean up test submissions in environments where the team performs real triage.
- Ensure that anyone consulting the backoffice understands the meaning of each exported column.