frevvo v6.2 contains new features that improve usability and makes designing forms easier. Here are a few of the top reasons to upgrade:
- Easy way to keep your forms/flows in sync.
- Several new built-in methods for business rules.
- Support for WebLogic.
- Java 8 and Microsoft SQL Server 2014 certification
for cloud/in-house tenants.
- Android smartphone & tablet certification running the latest version of Chrome are now supported.
- New palette control
- Support for Topaz Electronic Signature Pad devices
- Anonymous users can save/sign their forms/flows and continue later.
See the frevvo v6.2 release notes for more reasons to upgrade.
On This Page:
The v6.2 migration is automatic, however, we do recommend that you read the information below before you begin.
Just a reminder that the IP address for http://app.frevvo.com/ is 184.108.40.206. Customers that use firewall white listing for http://app.frevvo.com/ must add this IP address to your white list . This is applicable for outgoing HTTP POSTs to connectors. For example if your forms are posting to the frevvo database connector or any other connector you installed behind your company firewall.
Automatic Upgrade for Live Forms Online (Cloud Hosted) Customers
Live Forms Online cloud hosted customers (SaaS) will be automatically upgraded on October 31, 2015. If you have any questions, please email email@example.com.
Migration Considerations for Live Forms Online (Cloud Hosted) & In-house (On-Premise) Customers
Online and In-house customers should review the topics listed below:
You will notice changes in behavior for the following frevvo features:
If a user performing step 1 of a flow also has the role assigned to step 2, the behavior in prior releases immediately navigated the user to step 2. The flow was not saved to the submission repository. No notification emails were sent and the task did not appear on the Task List for all the users with specified role. In effect, the steps in the workflow became part of a screen flow rather than a workflow step as the designer intended.
The new behavior always creates a pending task if the next step has a role assignment. The flow is saved to the submissions repository. Task notification emails are sent to the user(s) when configured.
This can be useful when you have two or more steps assigned the same role in a sequence but you don't want the same user to perform them. In this case you want a new task list item created for each step.
This change only applies to roles. You will see this behavior:
- For workflows designed with individual steps and linked steps.
- When you use templates or hard coded roles for navigation
- When a summary step is in between 2 workflow steps.
When navigating back using the navigation bar, the behavior is the same as that of a screen flow.
For example, imagine a two step workflow where Step 1 is assigned the role of Employee and Step 2 is assigned the role of Manager.
User John has the roles of Employee and Manager. Users Jerry and Jim have the role of Manager. When John completes step 1 of the workflow:
- The flow is saved to the submissions repository and can be .
- Users will see the default "Your request is being processed." display message or your text if you customized it.
- A task appears on John, Jerry and Jim's Task List for further processing
- Task notification emails are sent to John, Jerry and Jim.
The image shows John's task List and the associated Audit Trail after step 1 of the flow has been performed.
Public forms/flows with Save/Load or Digital Signatures
Anonymous users can now access public forms that include the save/load feature or digital signatures. These features require a login. When the anonymous user clicks to save or sign, they will be prompted with the login screen.
Anonymous Steps in a flow
In previous versions of frevvo, once an anonymous step in a screen flow was performed, the user would see this error message if the link in the email sent to the anonymous user was clicked a second time.
This behavior has changed. Workflows consisting of multiple sequential anonymous steps (aka screen flow) now support the anonymous user clicking the link in the anonymous step email again.
For example, imagine a New Listing Agreement workflow where the Real Estate agent can elect to send an email to the seller (anonymous user) to collect the property details. In this scenario, the agent fills in steps 1 and 2 of the flow supplying the Seller's email address. The Seller receives an email with a link to the first anonymous step (Seller Information). The Seller clicks on the email link, completes the Seller Information and Property Information steps then the flow is routed back to the agent for review.
In the designer, the flow would look like this: Notice the Seller and Property information steps represent a screenflow since they are both filled out by the same person (Seller).
Let's say the Seller completes the Seller Information step then closes the browser. When the seller clicks on the link in the email again, the Seller will be directed to the Seller Information step instead of seeing the error described above.
If the Save on Navigate property is checked for this workflow then the anonymous user is brought back to the flow at the current/latest anonymous step (Property Info) when they click the email link a second time.
Audit Trail and Submission UI Improvements
form.unload Behavior Change
The special identifier, form.unload, used in a rule, executes the rule when the user clicks on the Submit button but before the form is submitted. If you have a rule in your form that changes any control(s) after clicking Submit, thereby making the form invalid, the form will no longer be submitted and the invalid form will redisplay.
- Form and Document actions will not execute when the form becomes invalid.
- PDFs are not generated.
- Invalid controls become highlighted as expected.
- form.unload output displays in the debug console.
This change avoids creating an invalid xml for a successful submission.
This feature is implemented for Forms only.
Migration Considerations Live Forms In-house Only Customers
Please review the instructions in the Upgrade Guide before migrating.
Support for MySQL 5.1 database is dropped in this version of frevvo. If you are using MySQL 5.1, then please upgrade to MySQL 5.5 or MySQL 5.6 before upgrading your frevvo version.
LDAP/Active Directory Security Manager Configuration
frevvo in-house (on-premise) customers should be aware that the configuration of the LDAP/Active Directory Security Manager is now done using the Add/Edit Tenant user interface LDAP configuration properties that were previously included in the frevvo.xml file can be managed via these frevvo screens. Click here for more information on this topic.