We recommend that you read the information below before you begin.
Automatic Upgrade for Live Forms Online (Cloud Hosted) Customers
Live Forms Online cloud hosted customers will be 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.
Migration Considerations for Cloud and In-house Customers
The Opaque URL feature provides:
- URLs that do not include a user's id
- Backward compatibility for URLs that contain a user's id - they will continue to work.
- A reverse lookup function of the opaque URL that can be used to locate a form/flow in a user's account for troubleshooting purposes. This capability is only be available to administrators, tenant administrators and users with the designers or publishers roles in the same tenant.
An example of the opaque URL for a
OLD SPACE URL: http(s)://<server>:<port>/frevvo/web/tn/mycompany/user/designer/space/mycompany NEW SPACE URL: http(s)://<server:port>/frevvo/web/tn/mycompany/u/8aa27da6-4bef-427c-92e3-6ad8d58e506a/space/mycompany
New version of PVE Connector
A new version of the PVE Connector - v5.4 is now included in the frevvo tomcat bundle. Version 5.4 of the connector is primarily a bug-fix release. Refer to the PVE Connector Release Notes for the issues fixed.
The new version of the PVE connector will be installed when the frevvo cloud is upgraded to v7.2. In-house customers can simply replace the existing pve.war file with the new one which is included in the
v7.2 tomcat bundle.
Change to Doc URI format when initializing a form from submission xml
You may have forms that you want to populate with data from a submission so that your users see the data, edit it if needed and submit again to create new submission. One way to initialize a form from a submission is to use the form submission xml link and the Doc URI wizard. Changes were made to ensure that cookies and secure sessions are used for the http get back to
The <host:port> section of the form submission xml link must be changed in the Doc URI wizard to "frevvo://" to take advantage of this change. Refer to the example in the Initializing Forms with XML Documents topic for the details.
Existing upload controls on existing forms will behave as they always have after this change is made. This is true as long as the configuration relative to this feature is not changed by the designer. In other words the default configuration for this feature will cause the system to use the uploaded file's name as the attachment name as it always has.
Legacy submissions with attachments will not have 'origFileName' in their contentTypes, so need to set the re-directed attachment name (that is used for the save as name) to the filename from the content type (if origFileName is not present).
Migration Considerations for Live Forms In-house Customers
Changes to Supported Platforms
Java 1.7 is no longer supported. In-house customers should upgrade to Java 8 before installing
v7.2. Please review Supported Platforms for a complete list.
New version of the Database Connector
A new version (v2.5) of the Database Connector now included in the frevvo tomcat bundle. Version 2.5 of the database connector requires Java 8.
In-house customers must upgrade to
v7.2 to use the Database Connector v2.5. There are 2 options:
- Copy the configuration from your previous installation and the connector will continue to function as it did before. The DB v2.5 connector runs seamlessly with the DB Connector v2.4 configuration files.
- Read the documentation for new configuration instructions to take advantage of the new features.
Review the DB Connector Release Notes to help you decide.
#18662 - CF : Form/flow submission should be edited by users as per ACL permissions.
#16318 - 5.3.3 ACL behavior in confluence
Just a Reminder for In-house Customers
v7 License Key Required if you are upgrading from a version prior to Live Forms v7.x
Request a v7 license by emailing firstname.lastname@example.org 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
The Insight Server and Service (Batch job) MUST be configured to take full advantage of the Reporting and the v7.2 Submission view 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
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.2.0 server.xml file. Do not replace configured sections from a frevvo.xml from a previous release into the v7.2.0 server.xml. file.
Email Configuration and 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
You do not have to restart the Insight server every time you restart