We recommend that you read the information below before you begin.
The Legacy Submission View including the Export to Excel feature will be removed in the next major release. Please begin using the redesigned submission view as soon as possible.
Migration topics for v7.1: New Export to Excel feature #19973 Message elements cannot be edited #19913 Strings containing ':' does not get translated when ISO-8859-1 encoding checkbox is checked while uploading the locale file. #19788 Long names of uploaded attachments causes submission failure Old and New Submission Views - in-house can turn off the old view - see bottom of spec Up to 5 fields on this tab be marked with an asterisk - indicating that these will be key fields for that form/flow to in the legacy view. if you create a new form you will only see the searchable fields tab #20141 - Documentation: For Release 7.1
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 firstname.lastname@example.org.
During the cloud upgrade, the Insight Data Batch job will run on ALL production tenants. This is necessary to create Insight documents for all existing submissions. Your submission data is now available for Reports and the new Submissions View.
v7.1.0 was released on TBD for in-house customers.
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 will be removed in the next major release. Users are encouraged to begin using the redesigned submissions view as soon as possible.
For now, Cloud customers will see icons for both views on the Forms/Flows Home pages, the Shared Items tab on the Application Home page and the Shared Items option in the Important Items dropdown in a space. Remember, you must have the proper ACL permissions to view/edit/delete submissions.
The export of submissions to Excel has been replaced by an export to a csv (comma separated values) file. 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. However....
The Export to Excel feature will be removed along with the legacy submission view in the next major release. Users are encouraged to begin using the redesigned submissions view and the Submisisions Export to a CSV file as soon as possible.
Saved and Key fields have been replaced by Searchable Fields.
Key and Saved fields have been simplified into a single concept for Submissions View 2.0. The single concept is named Searchable Fields and technically is a rename and extension of the old Key Fields functionality. The searchable fields configured for a form or flow are the fields that may be use to filter submissions in the submissions view.
The screen below illustrates the edit mode administration dialog that is available when the user clicks the "setup Searchable Fields" link in the form or flow editor. The "setup Searchable Fields" link replaces the old "setup Key/Saved? Fields" link.
The administration of searchable fields is very similar to the legacy administration of saved fields. It supports drag and drop and left and right buttons similarly to the saved fields ui in order to added searchable fields.
There is a configured max number of searchable fields supported (see section 3.4). When an attempt is made to add a searchable field in excess of the maximum configured number of searchable fields, the user will see an error message ("Maximum Number of Searchable Fields Exceeded!"). The message will appear on the lower right of the screen illustrated below and will disappear after a short time. Any fields in excess of the max configured will not be allowed.
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.
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 email@example.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:
2 gigahertz (GHz) 64-bit (x64) processor with 4 cores
5 gigabyte (GB) of system memory
100 GB hard drive
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
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.
When you configure your database, make the changes in the v7.0.1 server.xml file. Do not replace configured sections from a frevvo.xml from a previous release into the v7.0.1. server.xml. file.
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.
Email Configuration is still done in the frevvo.xml file. Custom configuration parameters that were added to the frevvo.xml file in previous releases are still configured in the frevvo.xml file.
Start the Insight server before Live Forms
requires Insight software for the Reporting 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:
You do not have to restart the Insight server every time you restart .