A Submission is a JSON object whose values were submitted to a form or resource. These can be thought of as “objects” within the system and operate very much like them. A typical submission JSON object looks like the following.
These properties are described as follows.
The MongoDB ID of the submission
The values of the form that were submitted.
Additional metadata that is added to the submission, such as timezone information.
The state of the submission. "draft" for draft submission, and "submitted" would mean it has been submitted.
The Form ID for this submission.
The Project ID where this submission resides.
The date this submission was created.
The date this submission was modified.
The ID of the "user" who created this submission.
If this submission is used as a "user" submission, these are the roles that are added to that user.
Access configurations for this submission. This is used when field based resource access is used to establish permissions to the submission.
You can access submissions of a form through the API interface of the submission.
There are also a number of interfaces that can be used to visualize and export the submission data of a form. These are as follows.
The submissions of a form can be seen by clicking on the Data tab on a form within the Developer Portal.
Think of the submissions view as administrative access to the database. This should not be used for typical interaction with the application and is not designed for end user use.
The Submissions page gives you an administrative overview of submissions to your forms.
You can see a table view of the fields that had “Table view” selected on them. To add or remove fields from this display, edit the field on the Form Edit page and uncheck “Table View”
From the Submissions overview page you can also view, edit and delete individual submissions to your forms. Use the icons on the right to perform these actions.
Use the two buttons at the top of the submissions list to export all of your data for a form. These operations are streamed from the database which means they should start very quickly and will work on very large datasets without having to write everything out to the server before starting the download.
CSV is Comma Separated Values and data is squashed down to rows of values with commas between them. This may not work well for complex data structures as it is essentially a flat file. CSV files can be opened by spreadsheet applications like Excel.
Submission Versioning allows to see who has updated a submission, when a change was made, and any notes associated with the update. Additionally, Submission Versioning can be used to revert to previous incarnations while safeguarding all submission data. Submission Versioning is limited to Enterprise level projects. Users without an Enterprise level project can still experience versioning via any Trial level project.
Enable Submissions Versioning
To get started, create or enter an existing form.
In the Revisions section, on Submission Revisions block expand the select dropdown menu and select Enable option.
After adding these settings on the tab, each time you make a change to the submission, a new version of it will be created.
View and editing Submission Revisions
After adding settings Edit submission tab has the following form:
You can add comment to new submission revision in Revision Note field. Pay attention that new revision will not be created if no changes in submission are made.
The list of submission revisions can be seen at the Revisions tab.
To view submission revision data, use View button.
To return to a specific version of the submission, use Restore button.
Submission Revision Log
It's also possible to add a log of changes in revisions of submission to display submission as pdf. You can add required settings on Form Settings tab.
In the PDF Settings block check Show Change Log option.
After adding these settings, submission pdf file will contain information about user, who updated submission, data and time of the update, submission revision note and list of changes made.