comes with a built-in submissions repository. The repository can run on top of most SQL databases. By default, your form data is stored in the repository and can be viewed from the Submissions page.

Filter your submissions using form data. Create Logical expressions to narrow the search for particular submissions. Fields in your form/flow, set up as Searchable fields by the designer, can be used as criteria when searching submissions. Once your Searchable fields are defined, re-indexes existing submissions so you can search them using the same fields.

Additional default fields such as: error, error description, submitter id, lock user id, started date, etc. can also be selected as filters.

The Submissions view works well on mobile devices and is easily embedded in a web page and wikis such as Confluence. Customers running with Confluence will not see the legacy submissions view from the Confluence Screen. It is only available when you log into your Confluence tenant.

The Insight Server and the Insight service must be running for the Submission view to work.

Cloud customers will see an icon for the Submission View and another icon for the Legacy submissions view. The Submission View Configuration Parameters topic discusses the ability to hide the Legacy view among other options for in-house customers.

The Export of submissions to Excel feature has been replaced by Download to CSV. You can still use the Export to Excel feature by accessing it from the Submissions Legacy view. However, the Legacy Submissions view and the Export to Excel may be removed in a future release.

The various items on the Submissions page are explained below.

Browser not supported