Form Versioning


ActiveForms forms are versioned.

When you work on a form by changing its field, logic, or graphics you always work on a draft version. When your form is completed and tested, and you are convinced it works as expected, you can create a release version. If you want the form to be visible to users, you publish the release version.

A form is usually created as follows:

  • Click Create new form on the form list.
  • Enter the basic form data: its name and address.
  • Build your form. Open FormBuilder by clicking Edit. Remember that you are now working on a draft form. First time after create form, FormBuilder is open automatically.
  • Test your draft.
  • Repeat the editing and testing cycle as many times as necessary to achieve the expected results.
  • If you are happy with your version, create a release. In the description field, you may want to write what you changed.
  • The form is still not visible on the Web, because the release hasn’t been activated. Now you can show your release to other people who have access to ActiveForms for more testing and collecting feedback.
  • If the form requires corrections, edit the form, theme and layout always changing a draft.
  • Having made a number of changes, issue consecutive release versions. Repeat the cycle until everyone says it is perfect. The form is still not visible on the Web, because none of the created releases is active.
  • The principle is that you always edit a draft, and once a release is issued, it is unchangeable. Someone has come up with a good comparison: a draft is like a doc file, and a release is like a PDF. You can edit doc files in Word, but PDFs are read‑only.
  • When your form is perfect, click Activate for a release that contains all the latest edits. This means the selected form version is now active.
  • From now on, the form is published on the Web and can collect entries.

ActiveForms versions almost all form settings:

  • fields, validations, logical conditions—everything you edit in FormBuilder
  • layout (visualization)
  • PDF printout template
  • General Settings

The only items that aren’t versioned include:

  • basic form data: the name, code, URL, access mode
  • mail integration settings

Those aspects remain constant for all releases.

Finally, a few words of advice about working with releases:

  • Give releases meaningful names and descriptions—this will help you to read the form creation history.
  • Only one version of a given form can be active.
  • If your draft is a version that you don’t like and you want to return to a previous version, you can use the Edit as draft feature. This will copy the selected version to the draft but also delete everything that the draft contained.
  • Release activation and deactivation operations can be planned for the future. Watch this space.
recent posts
3rd Apr 2014
Faster than ever!
5th Dec 2013
Live validation!
2nd Dec 2013
Features distilled
12th Mar 2012
Flicking Channels
26th Jan 2012
Your Own Error Page
9th May 2011
Box Properties
15th Apr 2011
Grouping Fields
13th Apr 2011
Form Versioning
24th Feb 2011
Form Access Modes
22nd Feb 2011
Required Fields
4th Feb 2011