Why Upgrade?

v7.1 contains new features that improve usability and makes designing forms easier. Here are a few of the top reasons to upgrade:

New Features:

On This Page:


We recommend that you read the information below before you begin.

The Legacy Submission View and the submissions Export to Excel will be removed in the next major release. The submissions Export to Excel feature has been replaced by the Download Submissions to CSV feature. Please begin using the redesigned submission view as soon as possible.

Automatic Upgrade for Live Forms Online (Cloud Hosted) Customers

Live Forms Online cloud hosted customers were automatically upgraded on TBD. The automatic cloud upgrade will be seamless. Cloud customers should review these topics to prepare for the new version of :

If you have any questions, please email support@frevvo.com.

Migration Considerations for Cloud and In-house Customers  

v7.1.0 was released on TBD for in-house customers.

New Submissions View

The New Submissions View provides the ability to search submissions by fields in your form/flow, metadata fields or logical expressions that you create. The UI makes it very easy to specify search criteria. The Legacy Submissions view is also available in this release but...

The Legacy Submission View and the submissions Export to Excel will be removed in the next major release. The submissions Export to Excel feature has been replaced by the Download Submissions to CSV feature. Please begin using the redesigned submission view as soon as possible.

For now, Cloud customers will see icons for both views on the Forms/Flows Home pages, the Shared Items Home Page and the Shared Items option in a space.

Forms/Flows Home Page

Shared Items tab on the Application Home Page

Shared Items from a Live Forms space

 

 

Customers using Confluence will only see the new submissions view. Logging directly into your Confluence tenant will provide access to the legacy Export to Excel feature if it is needed,

Searchable Fields

Saved and Key fields have been replaced by Searchable Fields. Searchable fields configured for a form or flow are the fields that can be used to filter submissions or tasks. When selecting Searchable Fields, select the controls that you feel your users would use as search criteria.

You will see columns for the controls in your form/flow designated as Searchable fields in the Submissions table. Searchable Fields are downloaded into the Submissions Download to a CSV file along with the submission default columns.

Cloud customers can configure up to 20 Searchable fields while the maximum number of fields can be configured in an in-house installation.

 If the Legacy submissions view is configured, designer users will see Searchable and Saved field tabs when the link to Setup Searchable Fields is clicked. The v7.1 upgrade automatically displays previously configured Key fields on the Searchable field tab and any configured Saved fields on the Saved fields tab.

Saved fields are only used for the Export of submissions to Excel which is currently available from the Legacy Submissions view. However, the Legacy Submission View and the submissions Export to Excel will be removed in the next major release. The submissions Export to Excel feature has been replaced by the Download Submissions to CSV feature.

Submission Download to CSV file feature

The submissions Export to Excel feature has been replaced by the Download Submissions to CSV feature. The csv file is easily opened in Excel. Customers currently using the Export to Excel feature can still access it by clicking on the  Submissions(legacy) icon.  

The Legacy Submission View and the submissions Export to Excel will be removed in the next major release. The submissions Export to Excel feature has been replaced by the Download Submissions to CSV feature. Please begin using the redesigned submission view as soon as possible.

Repeating Data

Forms/Flows containing repeat or table controls setup as Searchable Fields do NOT generate multiple rows in the Download Submissions to CSV file as it did in the legacy Export to Excel. Instead, when you upload the csv file into Excel, it will look like the image below:

The Download Submissions to CSV file topic covers all the details about how the new feature works.

Designer ACL

Form and flow owners (designer users that created the form/flow) can give other users (designers/non-designers) the capability to edit the form/flows. This is particularly helpful if a designer user takes a leave of absence or leaves the company. The "backup designer" has the ability to make changes to the form/flow without having to download the form/flow(s) from the owner's account to the "backup designer's" account. When given the View and Edit permissions, the "backup designer" also has access to any related submissions.

The designer ACLs feature is only available for form and flows. It may be expanded to other design types (applications, spaces, schemas, styles etc) in a the future release.

Users with or without the role of frevvo. Designer can be assigned the permission to edit forms/flows.

Search Submissions and the Task List using Fields in your form/flow

Fields in your form/flows can now be used to search and find submissions and tasks. The fields that you want to use as search criteria must be configured as Searchable Fields.  

The new Task List Search UI:

The new Submission Search UI

The Submissions chapter provides a complete explanation of the new submissions search function and the Searching the Task List topic discusses the details for the new Task List search.

Translation of strings containing a colon with ISO-8859-1 encoding

In previous releases of , labels in forms/flows that contain a colon were not translated if the ISO-8859-1 encoding checkbox is checked when uploading the locale file. Colons must be escaped when used in a locale file property name.  Newly downloaded default translation files will now escape a colon with a '\'. Previous translation files with strings containing colons will have to be re-uploaded with the colon properly escaped.

Migration Considerations for Live Forms In-house Customers

Hide the Legacy Submissions View

In-house customers can turn off the Legacy Submissions View by setting the frevvo.deprecated.submissions.view.enabled configuration parameter. Other parameters are available to hide the Delete button on the Submission Table, disable the Edit link in Submission Details and set the maximum number of Searchable fields. If the Legacy Submissions view is not configured, the Saved Fields tab does not display when the Setup Searchable fields link is clicked and the Export to Excel feature is not available.

Configure the Maximum Number of Searchable Fields

The maximum number of fields can be configured in an in-house installation by adding the  frevvo.max.searchable.fields parameter to the <frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml file. displays an error message ("Maximum Number of Searchable Fields Exceeded!"), if the number of Searchable fields configured exceeds the maximum. The message will appear on the lower right of the screen and will disappear after a short time. Any fields in excess of the maximum number of fields configured will not be allowed.


Just a Reminder for In-house Customers

In-house customers should review the topics below, the instructions in the Upgrade Guide and Supported Platforms before migrating. It is recommended that you perform a full installation of  v7.1.0 when upgrading. 

v7 License Key Required if you are upgrading from a version prior to Live Forms v7.0.x

Request a v7 license by emailing support@frevvo.com BEFORE you begin the upgrade. v5 and v6 licenses will not work. 

Hardware and Memory Requirements for your Live Forms Server

The minimum recommended hardware configuration for your Live Forms server is:

However you must size your hardware platform to your specific form usage characteristics. As the number of concurrent users and forms/flows increases so must the system memory. Refer to the memory configuration topic for the details.

Insight Server Memory Requirements

The Insight Server and Service (Batch job) MUST be configured to take full advantage of the Reporting and New Submission views and search capability. Do NOT disable it in the <frevvo-home>\tomcat\Catalina\localhost\frevvo.xml file.

It may be necessary to increase heap size for the Insight server, when reporting on/indexing a large number of submissions. Refer to the memory configuration topic for the details.

Database Configuration moved to server.xml file

The database configuration that was done in the <frevvo-home>\tomcat\conf\catalina\localhost\frevvo.xml file has been moved to the <frevvo-home>\tomcat\conf\server.xml file. Also, note that the datasource in the server.xml file has been renamed to jdbc/sharedfrevvoDS so that it can be shared by and the Insight server.



Configuring the database has not changed. The difference is that it is now done in the server.xml file and not frevvo.xml as in previous releases. When you configure your database, make the changes in the v7.1.0 server.xml file. Do not replace configured sections from a frevvo.xml from a previous release into the v7.1.0 server.xml. file.

Email Configuration is still done in the frevvo.xml file. Custom configuration parameters are still configured in the frevvo.xml file.

Start the Insight server before Live Forms

 requires Insight software for the Reporting and Submissions View feature. The Insight software is included in the tomcat bundle. The Insight server MUST be started BEFORE starting . Instructions for Windows and Linux operating systems are listed here:

 Windows:

  1. Open a command prompt. Navigate to <frevvo-home>\solr-5.4.1.Type bin\solr.cmd start to run the Insight server in the background, listening on the default port 8983.

    You will see this message:



  2. Browse http;<your server:your port>/solr to verify the Insight server is running. The <server:port> default values are localhost:8983. Change <your server>  to the server name and <your port> to the port the Insight server is running on if they are different than the defaults. Do not include the angle brackets <>. You will see the Insight server (Solr) dashboard with the current status:

If you close the Insight server (Solr) startup window, the server will stop running. Leave the window open or set up Live Forms and the Insight Server to run as Windows services.

Linux:

  1. Ensure that the scripts are executable: chmod 755 <frevvo-home>/tomcat/bin/*.sh
  2. Navigate to <frevvo-home>/solr-5.4.1/bin. Run this command to make the solr startup file executable:

    chmod +x solr
  3. Navigate back to the solr-5.4.1 directory.
  4. Start the Insight server by typing:

    bin/solr start - this starts the Insight server in the background, listening on the default port 8983.
  5. Browse http;<your server:your port>/solr to verify the Insight server is running. The <server:port> default values are localhost:8983. Change <your server>  to the server name and <your port> to the port the Insight server is running on if they are different than the defaults. Do not include the angle brackets <>. You will see the Insight server (Solr) dashboard with the current status:

   

  You do not have to restart the Insight server every time you restart .