Versions Compared

Old Version 105

changes.mady.by.user Former user

Saved on

compared with

New Version 106

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column

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:

Column
width400px

On This Page:

Table of Contents
maxLevel3


...

New version of the Database Connector

A new version (v2.5.23) of the Database Connector is no longer included in the v7.3 frevvo tomcat bundle. It is also 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.
 If you are running the Database Connector on your in-house server, customers must upgrade to v7.3  to use the Database Connector

The Database Connector v2.5.2. There are 2 options:

...

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.

  1. Read the documentation for new configuration instructions to take advantage of the new features.

...

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.


Although the connectors will function with configuration files from previous versions, they 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.

...

Document Action Failure Emails

In v7.3.1+, any users with the tenant admin role now receive email notification if a Document or Activity Document action fails to reach the intended destination. If a workflow has flow admins configured then they will receive the email instead of the tenant admin(s).

...

Embed code for forms/flows now contains container=false by default. This change should not affect existing embedded forms which have container parameter set to true. If you need the container value to be set to "true", change this setting manually for  newly embedded forms/flows going forward.

Tips for Embedded Forms/Flows viewed on Mobile Devices

...

Java 1.7 is no longer supported. In-house customers should upgrade to Java 8 before upgrading to v7.3+.  Please review Supported Platforms for a complete list. 

You must install the Oracle Java Development Kit (JDK) or the Java Runtime Environment (JRE) before installing Live Forms. Although Live Forms will run with either JAVA package, the Insight Server requires the JAVA_HOME environment variable so set it to the installation directory for the Java package that you install. Refer to  JDK or JRE Prerequisite for configuration details. 

Tomcat version Upgraded

The version of tomcat used in the frevvo bundle has been upgraded to now uses Tomcat  8.5.16. Tomcat 7 is not supported for 7.3.0.

Override _data properties in Configuration Files

...

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.

...

Excerpt

 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:

Section
Column

 Windows:

  1. 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:



  2. 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:

Warning

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.

Column

Linux:

  1. Ensure that the scripts are executable: chmod 755 <frevvo-home>/tomcat/bin/*.sh
  2. Navigate to <frevvo-home>/solr-5.4.1/bin. Run this command to make the solr startup file executable:

    chmod +x solr
  3. Navigate back to the solr-5.4.1 directory.
  4. Start the Insight server by typing:

    bin/solr start - this starts the Insight server in the background, listening on the default port 8983.
  5. 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 .

 

...