LogoLogo
Getting StartedDevelopersDeployment GuideGet Help
  • Quick Links
  • Welcome to Form.io
    • Getting Started With Form.io
    • Launch a Form
    • Overview of Form.io
  • Developer Tool Ecosystem
    • PDF Solution
    • Enterprise Form Builder
    • Form View Pro
    • The Security Module
    • Accessibility Compliance Module
    • Developer License
    • SQL Connector - Deprecated
    • Integration Libraries
    • Form.io CLI Tool
  • User Guide
    • Introduction
    • Form.io Developer Portal
    • Teams
    • Projects
      • Project UI
      • Project Settings
      • Stages
      • Multi-Tenancy
    • Resources
      • ResourceJS
    • Forms
      • Form Creation
      • Form Types
      • PDF Forms
      • Embedding a Form
      • Form Revisions
      • Form Settings
    • Form Building
      • Form Builder UI
      • Form Components
        • Component Settings
        • Basic Components
          • Resource as Select Component Data Source
        • Advanced Components
        • Layout Components
        • Data Components
        • Premium Components
          • Nested Forms
        • Custom Components
      • Logic & Conditions
      • Existing Resource Fields
      • Actions
    • Submissions
      • Accessing Submissions
      • Importing Submissions
    • Form.io eSignature - Coming Soon
    • Form.io Reporting Module
    • PDF Template Designer
    • Form View Pro
    • Form Manager
    • Enterprise Form Builder Module
  • Developer Guide
    • Introduction
      • Application Development
      • API Documentation
    • Form Development
      • Form Renderer
      • Form Builder
      • Form Embedding
      • Form Evaluations
      • Form Templates
      • Custom Components
      • Translations
    • JavaScript Development
      • JavaScript SDK
      • JavaScript Frameworks
      • JavaScript Utilities
    • Authentication and Authorization
      • SAML
      • OAuth
      • LDAP
      • Resource Based Authentication
      • Email Authentication
      • Two-Factor Authentication
    • Roles and Permissions
      • Field Match-Based Access
      • Field-Based Resource Access
      • Group Permissions
    • Integrations
      • Email Integrations
      • File Storage
      • Google Developer Console
      • eSign Integrations
      • Relational Databases
    • Modules
    • Fetch Plugin API
    • CSS Frameworks
    • Offline Mode
    • Audit Logging
  • Deployments
    • Self-Hosted Deployment
      • Local Deployment
        • Local File Storage
      • Kubernetes
      • Cloud Deployment
        • AWS Deployment
          • AWS Lambda
          • Form.io/AWS Elastic Beanstalk End-To-End Encrypted Deployment
        • Azure Deployment
          • Azure App Service
            • Azure MSSQL Connector - Deprecated
          • Azure Virtual Machine
          • Azure Kubernetes Service
          • Set up the DB
        • GCP Deployment
          • GCP Cloud Run
      • On-Premise Deployment
      • Enterprise Server
      • PDF Server
    • Deployment Configurations
      • DNS Configuration
      • Load Balancer Configuration
    • Licenses
      • License Management
      • Library Licenses
    • Portal Base Project
      • Portal SSO
      • Portal Translations
    • Maintenance and Migration
      • Changes to Premium Libraries
  • FAQ
    • FAQ
    • Tutorials & Workflows
      • Password Reset
      • Dynamic Select Filtering
      • Approval Workflow
      • SSO Email Token
      • Embedding A Video
      • Data Source Validation
      • Select Data Source Options
      • Nested Form Workflows
        • Nested Wizard Forms
      • Save as Draft
      • Role-Based Conditions
      • Custom Component
      • Dynamic Radio and Select Box Values
      • Override CKEDITOR
    • Errors
    • Examples
    • License Utilization Checks
  • Contact Us
Powered by GitBook
On this page
  • Accessing Submissions
  • Importing Submission Data
  • Submission Revisions
  • Enable Submission Revisions
  • View and Updating Submission Revisions
  • Submission Revision Log
  • Submission Collection

Was this helpful?

  1. User Guide

Submissions

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:

{
    "_id": "123456789012345678901234",
    "data": {
        "firstName": "Sally",
        "lastName": "Thompson"
    },
    "metadata": {},
    "state": "submitted",
    "form": "123456789012345678901234",
    "project": "123456789012345678901234",
    "created": "2021-05-24T13:51:43.414Z",
    "modified": "2021-05-24T13:51:43.415Z",
    "owner": "123456789012345678901234",
    "roles": [],
    "access": []
}

These properties are described as follows:

Property

Description

_id

The MongoDB ID of the submission

data

The values of the form that were submitted.

metadata

Additional metadata that is added to the submission, such as timezone information.

state

The state of the submission. "draft" for draft submission, and "submitted" would mean it has been submitted.

form

The Form ID for this submission.

project

The Project ID where this submission resides.

created

The date this submission was created.

modified

The date this submission was modified.

owner

The ID of the "user" who created this submission.

roles

If this submission is used as a "user" submission, these are the roles that are added to that user.

access

Access configurations for this submission. This is used when field based resource access is used to establish permissions to the submission.

Accessing Submissions

All form submissions can be accessed through the Developer Portal UI, programmatically through the API, or exported in different formats. Since submissions are JSON objects, they are easy to use across the entire application environment and elsewhere within the Form.io Platform. The standard nature of JSON makes submissions easily interoperable with many other data management tools and processes.

Importing Submission Data

While all submissions against forms will generate submission objects in that project, many customers may need to migrate data from one project to another, or import data from other systems or elsewhere in their environment.

Submission Revisions

Submission Revisions are a feature that provide audit logging of who has updated a submission, when a change was made, and any notes associated with the update. Additionally, Submission Revisions can be used to revert to previous versions while safeguarding all submission data. The Submission Revision feature was introduced in API Server Version 7.4.0. Please note: Submission Revisions are not needed to edit submissions, it is an audit logging capability to track changes that were made. Please note: Submission Revisions are not needed to edit submissions, it is an audit logging capability to track changes that were made.

Enable Submission Revisions

To get started, create or edit a Form or Resource.

In the Revisions section, in the 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 Updating Submission Revisions

After configuring Submission Revisions, the settings, the Edit submission tab has the following form:

Use the Revision Note field to add a comment to a submission revision.

A Submission Revision will not be created unless a change is made to the submission

Click the Revision tab to review all revisions for the submission.

Click the View button to review a specific revision.

Click the Restore button to revert the submission back to that specific version.

Submission Revision Log

Generate a PDF output report of all Submission Revision changes made to the submission. To activate the Submission Revision Log, access your Form Settings.

Scroll down to the PDF Settings block and check Show Change Log option.

After this configuration is set, downloading a PDF of the submission pdf file will contain information such as the Revision ID, the User who updated the submission, data and time of the update, submission revision note related to the change, and a list of all revision changes made.

Submission Collection

For read-heavy applications, a database index can be set on fields that are used often for application performance improvements.

Compliance requirements - Ensure data separation between collections.

Enable Submission Collection

To configure this feature, navigate to the Form or Resource you want to configure the Collection for and click the form settings button.

If you have an active Security and Compliance package, you will see the Submission Collection field enabled within your settings. Set the collection folder from your database and save your settings.

Once active, all data submitted with this Form or Resource will save in the specified database collection.

PreviousActionsNextAccessing Submissions

Last updated 8 days ago

Was this helpful?

Refer to the subtopic for greater detail.

Refer to the subtopic for greater detail.

This feature is included in the package. Follow the link or contact sales@form.io for more details.

Enables the storage of submission data within a separate . These collections can be configured on a per-form basis.

This feature is included in the package. Follow the link or contact sales@form.io for more details

Accessing Submissions
Importing Submissions
Security and Compliance
database collection
Security and Compliance
Revision list for the submission
Submission Revision PDF output log
Submission Collection field in Form Settings