THIS PAGE IS UNDER CONSTRUCTION!!!
Why Upgrade?
v7.3 contains new features that improve usability and makes designing forms easier. Here are a few of the top reasons to upgrade:
New Features:
Ability to display a customized warning message when a user tries to delete a repeating section or table row.
- System Metrics to monitor Platform Stability / Performance - (Cloud Only)
- Version 2 of the Visual Rule Builder now supports functions/expressions. This added functionality greatly enhances the rule builder's ability to create more powerful rules reducing the need to manually add JavaScript.
- frevvo.war now uses springboot to standardize server framework
- Spaces generate menu item url's using parentheses instead of curly braces
- The Fields list dropdown in the Rule Builder no longer 'wraps' when using up/down arrow to select
- Rule Builder: Support for mapping a data structure
- The Insight Server is now included in the frevvo.war file. In-house customers using the tomcat bundle. You will no longer see an insight.war file in <frevvo-home>\tomcat\webapps. Log entries for the Insight Server are now captured in <frevvo-home>\tomcat\logs\frevvo.YYY-MM-DD.log
- An unsaved changes warning displas when the form/flow browser window/tab is closed without saving or submitting and changes have been made to the data
- Customization of in-house installations is done in a single properties file named <frevvo-home>\conf\frevvo-config.properties
- Global configuration property to disable the unsaved changes warning for in-house customers
- Configuration Property to turn on json logging for the frevvo log
On This Page:
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 support@frevvo.com.
Migration Considerations for Cloud and In-house Customers
Visual Rule Builder v2
New version of the Database Connector
A new version (v2.5.3) of the Database Connector is no longer included in the v7.3 frevvo tomcat bundle. It is available in a separate download. You can download it here. The database.war does not extract after startup. You will not see a database subfolder in the <frevvo-home>\tomcat\webapps directory if you are using the tomcat bundle as in previous releases.
The Database Connector v2.5.3 requires v7.3.2 . The v2.5.3+ database connector datasources are now defined in the new <frevvo-home>\tomcat\conf\frevvo-config.properties files. The v2.4.* database connector datasources were defined directly in configuration.xml. This upgrade requires you to move your datasource configuration out of configuration.xml and into a configuration properties file.
- Read the documentation for new configuration instructions to take advantage of the new features.
Review the DB Connector Release Notes for a complete list of the enhancements to help you decide.
New version of the Google Connector
Version 2.3.0 of the Google connector is a small patch release with enhancements for logging and configuration. This version was deployed to the frevvo cloud on September 2, 2017. The connector will be released for in-house customers on TBD. frevvo recommends that you use this version of the connector with Live Forms versions v7.3+ to take full advantage of the improvements.
Logging and Configuration Enhancements
The Database, Google and SharePoint connectors now generate their own logs in the <frevvo-home>\tomcat\logs directory in the tomcat bundle. The Standalone version of the Database Connector creates the logs C:<dbconnector-home>\\Dbconnector-2.5.3-SNAPSHOT\logs\logs. The log files are named <connector name>.YYYY-MM-DDDD. Generating separate logfiles make it much easier to search for errors when troubleshooting connector issues.
frevvo Connectors are now designed to use the frevvo-config.properties file. This file contains global properties that apply to frevvo connectors including the frevvo.war. Creating this file is the recommended approach going forward.These changes are already in place in the frevvo Cloud.
In-house customers should refer to Tomcat Logfiles topic for information about turning on DEBUG for the frevvo log and to the Connector Logging topic for more details
Support for curly braces in Share Link URLs
Tomcat 8.5 doesn't allow curly braces in URLs since they are not valid URL chars and deemed a security vulnerability. currently supports parenthesis as well as curly braces. However, if you are embedding forms, flows or the Task List in your website, change the markup to use parenthesis (). Support for curly braces {} will be dropped in a future releases
Migration Considerations for Live Forms In-house Customers
frevvo-cofnig.properties
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.3+ 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 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:
- 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 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.
Email and 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 and Email has not changed. They are now both configured in the v7.4 server.xml file.
Insight log
This is intentional and a byproduct of integrating the insight.war into the frevvo.war. The messages formerly in the insight logs are now in the frevvo logs.
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:
- 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:
- 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:
- Ensure that the scripts are executable: chmod 755 <frevvo-home>/tomcat/bin/*.sh
- Navigate to <frevvo-home>/solr-5.4.1/bin. Run this command to make the solr startup file executable:
chmod +x solr - Navigate back to the solr-5.4.1 directory.
- Start the Insight server by typing:
bin/solr start - this starts the Insight server in the background, listening on the default port 8983. - 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 .
You May Notice...