Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Automatic Upgrade for frevvo Online (Cloud Hosted) Customers

frevvo Online cloud-hosted customers receive a seamless automatic cloud upgrade. If you have any questions, please email

New Features 

frevvo v10.2 contains many new features and enhancements to improve the workflow design experience, improve viewing and downloading submission data, and some under-the-covers enhancements that will streamline runtime performance. v10.2 also introduces Dashboards, an exciting new feature that will provide key business insights to your stakeholders with the same visual design and logic features you love in forms and workflows. 


  • Updating a Schema will no longer automatically update all affected forms and workflows. Instead, frevvo will flag all forms/workflows that need to be updated and the designers must edit the form/workflow, refresh the data sources and then save. At this point, the designer always has the choice of canceling. The form will continue to work based on the old schema until the designer refreshes it. You will no longer see a yellow warning that controls are unbounded after a schema update.

  • There is a new "Refresh data sources" option in the form/workflow's upper right-side action menu. Click this to refresh that form/workflow's data sources.
  • Form/Workflow uploads containing schemas:

    • When the project does not contain the schema, the upload will always add the schema from the zip.

    • When the project does contain the schema in question, the upload will ask whether the user wants to replace it. If the schema is replaced, all forms/workflows in the project will be checked and flagged when incompatible. Otherwise, if the schema is not replaced, then only the uploaded form/workflow will be checked for incompatibilities against the existing schema.

  • Compatibility will only be checked for the top-level elements (i.e. DocumentTypes) used in a form/workflow. If a top-level element is not used, then the form/workflow will not be incompatible.

  • You will no longer see the _types.xsd alongside .formtype files in the database or when downloading forms/workflows. The information that used to be in the _types.xsd file is now stored inside the .formtype file.


See also Migration Considerations: Schemas as you may need to take action after the upgrade to refresh existing schemas.


All forms/workflows from schema that also include XSD annotations (frevvo:label, …) will display a warning icon on the Forms/Workflows home page after the upgrade to 10.2. This is a result of an underlying model change that improves performance and reduces incidents of project/form/workflow corruption. The warning occurs because the calculation that checks for an updated schema does not have the existing annotations, and detects a mismatch. It does not impact the function of the form/workflow, so your users can continue to use the form/workflow without any issues. The designer can edit the form/workflow and refresh data sources to clear the error. In most cases, you will not need to make further edits to the form/workflow.


The "Using Forms and Workflows" topic combines and reorganizes information that was previously under separate "Using Forms" and "Using Workflow" topics. This change consolidates and streamlines the information you need to test and share your  resourcesfrevvo resources. You may need to update your bookmarks to point to the newly organized topics.


Planning Your On Premise Upgrade

**Hidden - v10.2 is Cloud Only**

On Premise customers should review the topics below, the instructions in the Upgrade Guide and Supported Platforms before migrating.  frevvo recommends that you perform a full installation of of frevvo v10.2 when upgrading. 

v10.0 License

titlev10 License Key Required

A v10 license key is required for this version of  if of frevvo if you are upgrading from a prior version. Request a v10 license by completing this form before you begin the upgrade. 

Before you begin the migration process: