frevvo latest - This documentation is for frevvo v11.1. Not for you? Earlier documentation is available too.

Planning for v11.1

Automatic Upgrade for frevvo Online (Cloud Hosted) Customers

frevvo Online cloud-hosted customers receive a seamless automatic cloud upgrade. If you have any questions, please email

New Features 

Anonymous Save

Forms and workflows can now be saved by anonymous users. When Save/Load is configured, the Save button will appear to all users whether they are logged in or not. For logged in users, the behavior will remain the same, saving the form or task to their Task List. Anonymous users will now see a prompt to enter their email address. The form or step is assigned to their email, and they will receive an email notification with a link to return to the form. Workflow steps will send the Task Notification email configured for that step. Standalone forms send a generic message with the subject "You have a new task for <form name>." and body "You can access your task by clicking here". There is currently no way to customize the email sent for a standalone form. Once the user has entered an email, subsequent Save clicks will continue to save the form/step to the same email address, and it can continue to be accessed by the original task notification link.

Workflow steps assigned to an email may also be saved, and the user can return to the task by using the original task notification link.

Sequence Number Generator

Many customers use frevvo to build workflows such as Purchase Orders or Invoices that require a sequential number identifier. v11.1 introduces a built-in Sequence Number generator that can be used to populate these numbers in your forms automatically.

You will start by creating a Sequence Number. Then, use business rules to populate a control with that Sequence Number (and any associated formatting) at run time. See the Sequence Numbers documentation for details.

Task Notification "From" Address

In past versions, the task notification "From" address was always the Tenant From Email Address, and it could not be customized by workflow or step. With the v11.1 release, designers may now add a static email or a template to the "From Address" field on task notifications. The "From Address" can be customized on each step of the workflow.

Rejection Email CC List

You will see a new “Email CC List” property on the workflow step properties Rejection tab. Enter static or dynamic (templates) email(s) to send a cc of the rejection notification.

Label and Value Alignment

Many controls now support setting the label and/or value’s alignment to center, left or right.

Please see Label and Value Alignment for a list of which controls support each alignment property.

New Rule Property to Check for a Value

In past versions, the isFilled function in the rule builder would use a boolean check on the ‘value’ property of a control to determine if there was a value. However, the value property for number controls always returned a ‘0' when it had no value (this was required for calculations.), so it was not possible to determine via the rule if a number control had data entered or not. v11.1 introduces a new ‘empty’ property on controls to check for a value entered at run time. This property is read-only, meaning it should only be used in a condition. The ‘isFilled’ and ‘isEmpty’ functions of the Visual Rule Builder now use the ‘empty’ property instead of the ‘value’ property. Existing rules will not change (and will continue to work as they did previously), until/unless the rule is edited using the Visual Rule Builder.

Google Connector: Select documents in Save to Google Drive Wizard

You can now select which documents to send to Google Drive in your document action. The designer can configure the Save to Google Drive Wizard to send any combination of the form/workflow snapshot (PDF, PNG, JPG), Data (the submission.xml), Attachments uploaded by the user, and mapped PDFs. This wizard is now consistent with other document action wizards.

Azure Security Manager User and Group Filters

You can now apply All Groups and/or All Users Filters in your Azure Security Manager settings. By default, frevvo will read all users and all groups. To apply a filter, you should have knowledge of the specific user/group properties and the correct syntax; please see this Azure filter documentation for supported operators and functions. There is no filter validation on the Edit Tenant page. For example, if you have groups specific to frevvo workflows that begin with "frevvo" you can set your groups filter to startsWith(displayName, 'frevvo'); if you want to limit frevvo users to only your domain, your users filter could be endsWith(userPrincipalName,''). 

Rename Tenant / Rename User

In the past, tenant and user ids could not be changed. This meant that changes (such as a user’s last name changing or the business name changing) required moving resources to a new user or a new tenant. In this release, frevvo is providing admins with the ability to change the tenant id and user ids as needed. Please see the Rename Tenant/Rename User documentation for details.

Users CSV Upload

The Users CSV upload process previously required you to validate the csv file, then click Load to upload it. If there were errors and a new file needed to be added, a bug existed that required the admin to return to Manage Users and click Upload CSV again. We’ve corrected this behavior and also streamlined the process. The button on the Upload Users page is now “Validate and Load”. If validation encounters errors, they will be displayed. If there are no errors, the users will automatically be loaded.

There is no change to the API batch user upload process.

Purge Old Submissions

*On Premise Only

In order to reclaim database space and comply with data retention policies, customers need the ability to delete old submissions. The Purge Submissions feature (available to the server admin for On Premise customers) now provides an option to delete submissions older than 'n' days. This process will delete submissions in all forms/workflows and in all tenants, whether or not they were already deleted in the submissions view.

Retired Features 

Role Property on Section Controls

The security "Role" property was once used to set section visibility, typically for approval workflows. This property has been deprecated for some time, and is removed in the v11.1 release.

Customers who have sections in their workflows and are using the Role property to set visibility should set it to null (select the blank option at the top of the list) and replacing it as described below prior to the upgrade. 

frevvo recommends using show/hide rules based on the workflow step name as a more reliable method that works in every use case. Show/Hide rules are easily created using the Visual Rule Builder. Refer to this example: Show/Hide Approval Sections on Workflow Steps.

Contact your account manager (or if you'd like our services team to help you with this.

Migration Considerations

Role Property

The Role Property is retired in v11.1. Customers who have sections in their workflows and are using the Role property to set visibility should set it to null (select the blank option at the top of the list) and replacing it as described below prior to the upgrade. 

frevvo recommends using show/hide rules based on the workflow step name as a more reliable method that works in every use case. Show/Hide rules are easily created using the Visual Rule Builder. Refer to this example: Show/Hide Approval Sections on Workflow Steps.

Contact your account manager (or if you'd like our services team to help you with this.

SharePoint Connector Token Refresh Required

The SharePoint Connector is upgraded with v11.1 including an upgrade of the OAuth library. This upgrade will automatically expire existing connection tokens. Customers using the SharePoint connector must refresh their token after the upgrade. If you do not refresh your token, your forms connected to SharePoint will not send files and you will see submissions errors.

To refresh the token, follow these steps:

  1. Log in as the designer/owner of your form/workflow connected to SharePoint.

  2. Edit the form/workflow

  3. Click Settings

  4. Click Document Actions

  5. You will be automatically redirected to a SharePoint page asking you to trust the frevvo app. Click Trust It. (This refreshes the token.)

  6. You will be redirected to your form/workflow. Save and close.

Typically, this only needs to be done for one form/workflow to refresh the connection token for all. If your existing forms produce an error when clicking Trust It, try clearing your browser cookies and then create a new form, go to Settings/Document Actions and select Send to SharePoint. This takes you to the same Trust It page - click Trust It to create a new token. If you have continued errors, please open a support case at

Save to Google Drive

The Save to Google Drive wizard has been updated to allow you to configure which attachments are sent. In past versions of frevvo, all attachments were sent to Google Drive (PDF snapshot, XML, Uploaded files, Mapped PDFs). After the upgrade, the same files will continue to be sent - no changes required. However, the next time you edit your Save to Google Drive document action, you may notice that the Send Snapshot field is blank and the Data field is checked. At that time, you will need to set a value (e.g. PDF) in the Send Snapshot field and, if desired, uncheck the Data checkbox prior to saving the form/workflow.

Form/Workflow Action Error Behavior

v11.1 introduces asynchronous post processing, which will improve form and document action performance and pave the way for future enhancements in this area. Previously, the Form Action Success action would be executed if the doc action succeeded and the Error action otherwise. However, with this change the Form Action will now be executed before Document Action(s). This means that a Document Action Failure will not be able to trigger the Form Action Error message to the end user. An admin notification will still be sent in the case of Document Action failure. Form Action Error settings will no longer be executed.

SAML Security Manager

Customers using the SAML security manager may have trouble logging in after the upgrade. This issue appears to be only for some IDPs, and was caused by updates to the OAuth library which change the service provider metadata slightly. If your tenant is impacted, follow these steps to update the service provider metadata:

  1. Generate the Service Provider metadata. Please follow the steps in this documentation.

  2. Add the service provider metadata into your IDP configuration (if required). See this documentation.

  3. Log in as the built-in admin. Edit the tenant, and add the new metadata (without the xml prologue) to the Service Provider Metadata property.

Message Control Alignment

If your forms used the “Center” property on Message Controls, you will find that after the upgrade the new “Label Alignment” property is blank, and your message is no longer centered. To correct this, please select “Center” from the Label Alignment property.

SQL Server Database URL Property

*On Premise Only
With v11.1 the built-in SQL Server JDBC driver is updated. In the newer version, TLS encryption is enabled by default. The property trustServerCertificate=true has been added to the jdbc url in the server.xml file. Do not remove this property when transferring your database url settings during your upgrade.

If you are using integrated authentication, please install the auth dll from here.