After publishing a form, you will often find that you need to make changes to the form. Once a form is deployed and form instances have been submitted, you still have the ability to make changes to the form without invalidating previously completed form instances.
PerfectForms™ provides a version control mechanism that allows repeated changes to the form without invalidating its existing form instances. Changes made to the form can then be tested in draft without affecting the data collected in previously published versions.
Major version numbers are incremented as whole numbers when forms are published. Any version number ending in 0 indicates a published form. For example, if your latest version number prior to deployment was 3.1, this will generate a version 4.0. When you edit a form and save your changes, the decimal numeral is incremented. For example, if you have opened a published form for editing, made and saved your changes and returned to the Dashboard, the version number would be 1.1.
By default, new instances of a form are always created using the latest published version of a form. However, the form designer (and users with design permissions for the form) can change the version setting to Published or Draft.
To learn about versions, complete the following steps:
|
|
For more information on the Draft option, see the Testing Your Form Using Draft Instances topic.
For more information on the Published option, see the Reverting to a Previous Version of a Form topic.
Video Tutorial: Version Control |
|
|
Updated: 17/04/2012
Page url:
http://www.perfectforms.com/Documentation/manual/html/?fl_working_with_form_versioning.htm
PerfectForms™ -- forms software, workflow software, and business process management