Form.io's core is open source, which includes:
Our Enterprise subscription includes E-mail support. All email support inquiries are reviewed twice per day with the development team. We respond as soon as possible with response times typically being same day.
In the case that the inquiry requires support that cannot be provided via email, we offer support packages to connect with a senior developer via Online Call at your convenience.
All software updates are included with the subscription. When a new release comes out, and a tag is published on Docker Hub, our customer base is notified by email with all the information regarding the release changes.
Follow along in our Enterprise Release Changelog to watch for new releases as they come out here: Form.io Enterprise Change Log.
Form.io contains e-sign integrations that allow you to request e-signatures on submitted forms. For more information, we recommend reviewing our documentation:
The Security module is a new optional add-on module that we have grandfathered in all customers for the existing subscription period and moving forward, if you wish to have access to these features, we can add the module to your subscriptions. Else, if you are not using these features, we will set the license to not include the module and the features will no longer be enabled.
The following features are part of our Security Module:
Advanced Audit Logging
The server now has the ability to produce audit logs of all user activity on the system. This will produce an auditable trail of user session events, and access and modification of all entities in the system. These audit logs will be output to the standard out for the docker container and can be routed into a log aggregation system.
Submission Revisions allow visibility 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 incarnations while safeguarding all submission data.
Enables the storage of submission data within a separate database collection, which can be configured on a per-form basis. For read-heavy applications, a database index can be set on fields that are used often for application performance improvements.
Field Level Encryption
Allows encryption of specific fields within a form that contains sensitive information. Limits access to the submission data, which requires the use of APIs to access submission data maintaining full database encryption. Field Level Encryption provides only API access to the data, and DB access is fully encrypted.
It is safe to swap out licenses for existing deployments. Using a fresh license will not affect your existing forms, resources, or data in any way. It will simply register within your License Manager as a new installation under that license.
A Project spans across environments with the Stages Functionality. Stages are utilized to connect to the other remote Environments via an API. More than one stage can be pointed to a single environment.
This enables a seamless Project JSON / Forms JSON promotion to match your software development lifecycle all within the Developer Portal UI. When deploying the API Server following the Deployment Guide, you will enable the Portal Application for the designated environment.
There is no limit to the number of fields you can add to the form. The renderer performs very well with large amounts of fields and we have only seen performance dips at the 2000 field mark.
Form.io forms are compatible with the latest versions of all modern browsers. Because our forms are embedded into applications, we recommend reviewing the browser compatibilities for the front-end frameworks such as Vue, Angular, React, Vue, etc. which have a browser list in their respective package.json.
Both applications can be customized and white-labeled to offer a custom UI on a per-tenant basis. To configure the logo, Title, nav bar, and more, the Public Configurations settings can be modified. View the User Guide: Form Manager.
Yes, you can translate most areas of our platform as well as any front-end field UI setting. Configure a Language resource within your project as described here to setup the translations.
In addition to offering our hosted PaaS, we commonly deploy our form-building portals and API servers into our customer environments (on-premise or private cloud) where they have total control of their apps, their forms, and their form data submissions.
Form.io is then out of scope with respect to related security and compliance regulations.
Think of us as:
What is your recommended deployment strategy?
We recommend taking advantage of Docker Containerization as this manages the containerization of all the dependencies needed. Please see the node.js deployments documentation.
When the module is turned on, the USWDS template is enabled on the form builder, which looks different than bootstrap, with colors that follow best practices for accessibility.
It also eliminates any components from the builder that are not compliant when the form is rendered in an application, keeping the user who is building the form in line with accessibility compliance best practices for the forms they are building.
Accessibility Compliance Module Overview
Restricts non-accessible components and options in order for a user who is building a form to create fully accessible forms.
Form rendering module handles the following:
Form.io USWDS template module OR Form.io Bootstrap template module handles the following:
When using Form.io»s SaaS solution, you will need to set up your own transport for the email action. Here's an easy-to-follow integration guide from our help documentation.
CORS will lock down the portal if the CORS domain has been misconfigured. To resolve this, use an API tool like Postman:
FormView Pro is an Enterprise level feature and is only available with an Enterprise subscription. This is also used to mitigate the problem of hosted anonymous forms being used by bad actors as phishing tools.
Your application needs to include the premium component module in order to renderer Premium components. Premium components are included with the Enterprise Subscription, follow the instructions here to setup the module.
This guide details project migration to different environments, including environments on different server versions.
Form.io is a rest API platform so it can integrate with any third-party platform or API. More information on integrating third-party applications / APIs using webhooks can be found at:
While you can copy forms into Resources, there is not a user-interface to change the form type. You can however use an API tool like Postman to programmatically change the type:
Use Project Template Exports within the Portal Application to migrate your project. Click here for instructions.
Use the Form.io CLI migration tool to accomplish this. View the CLI documentation. More information regarding the migration of submissions can be found here.
Migrating the PDFs from portal.form.io to a remotely deployed configuration is a manual process. Importing & Exporting will involve everything stored within the Project Template JSON.
Because PDF background files are uploaded to the file storage provider of your choice, these are not automatically migrated. You may see the backgrounds when you import the forms into your remotely deployed environment, but they will still be pointing to the Form.io file servers, and when you render the forms, the files will not be accessible.
To make sure all PDF First forms are pointing to the correct PDF background file, click the "X" next to the PDF in the builder, and re-upload the file, which will then be stored in the file server that you have set up upon initial deployment.
Your project ID is a numeric identifier enclosed in the URL.
Your Project Live Endpoint is a URL that can be found in the top right corner of the project screen, right below the Teams and Project settings buttons.