| Section | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Column | |||||||||||
| Section | |||||||||||
|
...
- whether the control's value appears in the form/flow submission document,
- whether you can use it in an Optional Section
- whether or not you can use it in a business rule
...
The Message and Link controls still support the "value" property. All existing rules will work unchanged. Note the Save Value property must be checked for there to be a value and have is accessible in a rule.
Message
...
Controls in Repeats
Message, Link, Image and Form Viewer controls can now be dropped into a Repeat control.
...
Message Controls and Optional Sections
If this the Save Value property is unchecked, a Message controls can now be included inside a section control. If this section control is referenced in a business rule that changes the sections properties (optional section), you will no longer be prevented from submitting the form or completing the flow.
...
Preconditions are typically used in workflows to perform/skip a step based on control values in prior flow steps. They can also be used to generate/not generate mapped PDFs. Preconditions use the same logic as Business Rules. In previous releases, designers had to type the JavaScript in the Precondition property of the workflow step or when setting up mapped PDFs. A modified version of the Visual Rule Builder is now available in v7.3 as a Precondition Rule Builder to help designers with preconditions. The Editor can be invoked in two modes:rule builder mode and code entry mode. Selecting the rule builder mode presents the editor where you can build your precondition statement by selecting form fields and conditions from dropdown lists. Of course, you can still enter the JavaScript manually in code entry mode. Refer to the Precondition topic for all the details.
Flows migrated from earlier versions (or uploaded) will have all existing preconditions shown in code entry mode with the manually entered code displayed. This also applies to PDFs with preconditions for migrated forms and flows.
...
Static Checkbox, Radio and Dropdown selection control options can be typed into the Options property in the form/flow designers. You can now populate Dynamic Options for Dropdowns, Radios, Checboxes and the ComboBox from a REST web service such as the frevvo Database Connector using control properties. The frevvo Database Connectorextract the values returned from the service
The Dynamic Options feature is now available to configure these selection controls to pull values from a Rest Web Service and dynamically populate the options without the need to write a business rule.The designer need only provide the:
...
Existing forms/flows that contain the ComboBox control will have the value of the Options URL property in the Options Src field after upgrading. For example: if the Option URL was set to /frevvo/web/tn/tenant.id/users?match= in the previous release it will be changed to frevvo Users. If . For example: if the Option URL was set to /frevvo/web/tn/tenant.id/roles?match= in the previous release it will be changed to frevvo Roles. Lists of Users and Roles can only be retrieved for the current tenant.
If the Options URL was empty in the previous release, the upgrade code defaults it to frevvoUsers.
Check this with Nancy- 20988 - Completely removed the userRoleTenant from comboBox control (type) and removed it from the design time ui. Internally, the url for frevvo users/roles is constructed with the template {form.tenant.id} so that it is dynamically determined as the current tenant at runtime. Because of this, any forms/flow previously built using 7.3 will not pick up this change unless the combobox options src property is changed and the form re-savedusers?match= in the previous release it will be changed to frevvo Users. If the Option URL was set to /frevvo/web/tn/tenant.id/roles?match= in the previous release it will be changed to frevvo Roles. Lists of Users and Roles can only be retrieved for the current tenant.
If the Options URL was empty in the previous release, the upgrade code defaults it to frevvoUsers.
{task.perform .url} template is the new default for Task Notification Emails
...
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.2.4+ to use the Database Connector v2.5.2. There are 2 options:
...
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.
...
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><dbhome>\\Dbconnectordatabaseconnector-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.
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 the details about the connector logs.Excerpt
| hidden | true |
|---|
Embed script change
Embed code for forms/flows now contains container=false by defaultin 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.
| Info |
|---|
frevvo only supports/certifies frevvo connectors running in the Apache Tomcat container. Refer to our Supported Platforms for the list of Application Servers and databases supported/certified by frevvo |
Document Action Failure Emails
In v7.3.+, users with the tenant admin role 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).
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 releaseparenthesis as well as curly braces. However, if you are embedding the Task List in your website, change the markup to use parenthesis (). Support for curly braces {} will be dropped in a future release.
Embed script change
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
Form/Flows embeded embedded in mobile pages may not display properly when rendered on mobile devices. frevvo offers these tips to resolve the issue. Note the default behavior for showLink is now set to false which will show the form in a frame. A true value will show the form/flow as a linktrue value will show the form/flow as a link.
Captcha
Live Forms 7.3.6+ incorporates Invisible reCAPTCHA for the Live Forms Captcha feature required because Google is shutting down the reCAPTCHA v1 API used in previous releases.
Migration Considerations for Live Forms In-house Customers
...
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
...
JMX Monitoring Enabled in the frevvo tomcat bundle
JMX (Java Management ExtensonsExtensions) is enabled by default in the v7.3 tomcat bundle. Information can be accessed with jConsole, or a similar tool.
...
Changing string name/value pairs in the default file found in the <frevvo-home>\tomcat\webapps\ frevvo.war displays the new English version of the string on the UI. This is mainly for OEM partners and resellers, but it will work for any in-house customer. Modifications to the strings in this file can be used to change the labels in the Form Designer e.g. change Palette to Palette Controls or change the text of a message such as "Access denied. Authentication required" to something more user friendly. To access the default file, the frevvo.war must be unzipped, then rezipped after the changes are made. Refer to the Customizing Runtime Messages and Labels in the Designers topic for the step by step instructions.
topic for the step by step instructions.
Geolocation
New in-house installations now require a Google Map API key if you want to embed a Google map in your forms/flows. See the Geolocation topic for instructions to obtain the key. This change does not apply to Cloud customers.
You May Notice...
A New SharePoint Connector
...
Visual Guided Tours and Page Help are available for Cloud customers. When you install a Template Application, a Guided Tour is automatically launched if one is available. Guided Tours and Page Help can be invoked on–demand by clicking the appropriate button. In-house customers can configure Guided Tours and Page Help by enabling the appcues.enabled parameter in the frevvo.xml file. These features require the purchase and installation of the APPCUES code tool.
| Note |
|---|
You may notice that the correct elements are not highlighted or scrolling is not working properly when participating in a Guided Tour using the IE 11 browser. This is a known APPCUES issue. |
...
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 3+ when upgrading.
| Warning |
|---|
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. |
...
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.
...
| Warning |
|---|
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 3+ server.xml file. Do not replace configured sections from a frevvo.xml from a previous release into the v7.2.0 3+ server.xml. file. |
Email Configuration and custom configuration parameters are still configured in the frevvo.xml file. Excerpt
Start the Insight server before Live Forms
| 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:
You do not have to restart the Insight server every time you restart . |
...