We noticed that JavaScript is disabled in your browser. We suggest enabling it for a better experience.
We noticed you're using an older version of Internet Explorer. We suggest you update to the latest version for a better experience.
Skip to main content

What's new in OpenForms

21 November, 2019

Track form performance with Analytics and Insights

We’re introducing some new tools to help you track the success of your forms and digital transformation projects: Analytics and Insights.


Enterprise plan

analytics (1).png

Each form you make in OpenForms now features an Analytics tab. Here you can see how people are using your forms. See where things are going right -- respondent numbers, time spent per form and per section, as well as completion rates. See, too, where things aren’t going as right -- track where people make errors and where they give up on a form.  


All plans



See the benefit of bringing respondents online with our new Insights page. This page, available from the dashboard, displays stats on all your organization’s forms. See the money transacted, the average time respondents saved, and the time and money you’ve saved by choosing OpenForms. Use this information to see how your digital transformation project is tracking, and plan future improvements.

Build better forms with powerful new features

We’ve introduced several new features to make forms easier to create, easier to use, and more effective. 

Answer piping

Pro, Business and Enterprise plans



Use answer piping to create dynamic, personalised forms by quoting information respondents provide earlier in a form in subsequent fields. Address respondents by their name, for example, or refer to each pet individually when someone's registering multiple animals. Answer piping can make forms friendlier and keep respondents focussed, resulting in a better user experience.

The Content field

All plans



We’ve consolidated the Heading, Paragraph, and List fields into a single field: Content. The Content field is a one-stop-shop for all form content that doesn’t require a response. It’s where you can explain a form’s purpose, for example, or outline the attachments respondents will need to supply. Use this field’s text editor to create and style all kinds of text: headings and paragraphs, lists, links, and piped answers.

We think grouping content fields together and giving you more control over the formatting of written content will make form creation quicker, easier and more powerful. Let us know what you think.

If you’re using the three superseded fields in existing forms, you can still see them in your form builder, but you won’t be able to add more from the toolbar (use the Content field instead). Likewise, if you access form details through the OpenForms API, those will still work. In the coming months, we’ll be phasing out the Heading, Paragraph and List fields.
We’ll be in touch about what to do when that happens. To get a head start, we recommend changing your forms over to the Content field and updating your integrations now.



A simplified version of the text editor is also now available within field and section descriptions, so you can add hyperlinks and piped answers to these fields.

Stop respondents from completing wrong forms

Pro, Business and Enterprise plans 


We’ve updated the display logic for form sections. Now you can add a criteria to form sections that, when triggered, prevent respondents from continuing further or lodging that form. Use this where a respondent’s previous answers indicate a form isn’t useful to them. (Trying to register a cat with a dog registration form, for example). Add text or links to point waylaid respondents in the right direction.

Plus some small improvements...

Data connections

Enterprise plan


We’ve expanded the way Enterprise users can use data connections to lodge and retrieve form data.


Data connections can now be triggered when a form loads. Use this to pre-populate fields such as a respondent’s personal details when that information is available (for example, when your form is hosted on a site that requires a login). We anticipate this will be a convenient feature for Intranets and other gated sites, such as job application portals. 

You can now also insert additional information into data connections with Headers. Use headers to append authentication data for external services, add custom filters for data parameters, or insert any other information that isn’t contained within a form itself.

A new payment gateway

Pro, Business and Enterprise plans


We’ve added Payment Express PxPay to our list of available payment gateways for form payments. Payment Express has also changed their name to Windcave, so you’ll see this new branding in your payment gateway settings.

… and bug fixes


Form builder 

  • Form authors can no longer save forms containing field sets that have been modified while the form was being edited. 

  • Fields that are referenced in subsequent smart logic have certain movement restrictions on them. This is intentional, to ensure smart logic triggers correctly. However, in some scenarios, movement restrictions were inconsistently applied (for example, referenced fields could be moved to the start of a section, but not back to their original position). This has been fixed.

  • Previously, a “saving form” popup would fail to display in Internet Explorer 11 when users confirmed changes in the form builder or form settings. This has been fixed.

  • Fields that are hidden by smart logic are now considered blank if used in subsequent smart logic.

  • Previously, users could navigate around disabled sections in form settings by using keyboard commands. This has been fixed and disabled sections are properly disabled.


  • When editing the formula of a calculation field, selecting “insert” without specifying a section or field would previously cause a rendering error, resulting in a blank page. This has been fixed. 

  • Fields that are hidden by smart logic are now ignored by calculations. 

  • In rare scenarios, calculation variables could fail to sync with certain fields. This has been fixed.

  • Previously, a form with a payment field that did not reference any fields in its calculation could be saved. This has been fixed, and payment fields must be set up properly for forms to be saved.

Form responses

  • We’ve expanded the criteria you can use to filter form responses. You can now search responses for addresses, transactions IDs, payment info, signatory names and the filenames of uploads. 
  • If a form respondent uploads more files, or a larger file, than the maximum value allowed by the form, this would previously trigger an unexpected error but allow the form to be saved and lodged. This has been fixed - a correct error message is now displayed and the form cannot be saved.
  • Previously, minimizing a section in the form builder would trigger a warning that the user is navigating away from an unsaved form. This has been fixed.

UI improvements

  • Previously, whenever a popup appeared, the content underneath would automatically scroll to the top of the page. This no longer occurs.
  • Previously, some non-Latin characters could render incorrectly in lists. This has been fixed.


  • Previously, users who access OpenForms via an OpenCities login were shown a potentially confusing error message if they tried to log in directly to OpenForms or tried to change their password. They are now directed to log in via OpenCities.
  • Unverified users who requested an additional verification email after a failed login attempt were previously sent an email containing incorrect wording. This has been fixed. 
  • Invoice emails for Enterprise users with a manual payment plan now include purchase order numbers.
  • Previously, when an Account Owner adjusted add-ons, navigated to the confirmation screen and then navigated back to the Change Add-ons screen, their new selection was forgotten. This has been fixed.

Printable PDFs

  • Previously, unusually long form titles could affect the placement of form logos on printable form PDFs. This has been fixed. 

Performance improvements

  • We’ve improved performance when viewing and searching for form responses.
Was this helpful?