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: #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
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 email@example.com.
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 Submissions Export to a CSV file as soon as possible.
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 on a Task List. Designers should carefully consider which fields in the form/flow to set up as Searchable fields. Specifying the form/flow fields that you want to use as search criteria can be helpful when searching submissions and Tasks.
Cloud customers can configure up to 10 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. Fields from your form/flow display on the Available Fields tab and supports drag and drop and left and right buttons for easy configuration when setting up the Searchable and Saved fields lists.
Saved fields are only used for the Export of submissions to Excel which is currently available from the Legacy Submissions view. However, the Export to Excel feature, along with the Legacy Submissions view will be removed in the next major release. The Saved fields tab will no longer display. Customers are encouraged to begin using the redesigned submissions view to become familiar with the new functionality and the export to a csv file as soon as possible.
The Task List search now has the capability to filter down the matching tasks for a form/flow based on the values of the configured searchable fields. This addresses the need to find tasks based on submission data in certain use cases.The Task List UI allows the selection of ONE form/flow then allows you to enter search criteria based on the configured Searchable fields for that form/flow.
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.
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.
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.
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 firstname.lastname@example.org BEFORE you begin the upgrade. v5 and v6 licenses will not work.
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.
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.
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.
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:
You do not have to restart the Insight server every time you restart .