We recommend that you read the information below before you begin.
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.
resources, Applications, Forms, Flows, Spaces and more are referenced with opaque URLs. Use of opaque URLs eliminates security issues that may have been present with URLs that exposed a designer user's id. Opaque URLs replace the user id (…/user/user.id/…) that was used in the previous format with a universally unique identifier (uuid) …/u/user.uuid/… The uuid, is a randomly generated value that is stored in .
The Opaque URL feature provides:
An example of the opaque URL for a space named mycompany is shown below:
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
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.
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 to obtain the submission data.
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).
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.
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:
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
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.2.0 when upgrading.
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.
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.
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.
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.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.
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 .