Documentation
API
Q&A
Read
AnnouncementsArticlesWebsite tips
Learn
Getting StartedManagerMaestroAnalyticsExchangeWorkspaces
Resources
VideosDownloadsExchange PackagesRelease Notes
Ideas
Contact
Platform
Manager
Maestro
Exchange
Workspaces
Analytics
Springboard

Form Versions Overview

   Journey Manager (JM) The transaction engine for the platform.  |    Form BuilderPlatform Developer |  All versions This feature is related to all versions.

Manager offers a flexible mechanism to import, create and manage multiple versions of a form, which benefits in the following:

  • Allows users to switch between different form versions.
  • Allows controlled releases of new versions into a Manager environment.
  • Provides the ability to roll back a form version if it has a problem or a bug. When developing and deploying forms, occasionally challenges will arise making it necessary to revert to a previous version of a form. Form versions are also required to support the form A/B testing feature in Manager.

Although Manager provides the functionality to create a new form version based on the existing form, we recommend using Maestro for this purpose, because it provides manageable and clear approach to keep form versions in sync across both tools. Let's look at this in more detail.

You create a new version of a form in Maestro, edit it to add features and functionality and then build it in the Maestro editor to generate a JM Form Version ZIP file. This file is a new form version of the original form and you need to deploy it to Manager using the Import Form functionality.

We don't recommend creating many versions of a single form. Ideally, there should not be more than 10 form versions. This is not to clutter the environment.

Even though there can be many form versions of a form, there is always only one current version, which is used to server user requests for this form. You can't delete a current version of a form, but you can nominate another form version to be the current one by using the Make Current functionality. Manager also allows you to change the current form version automatically at a scheduled time.

After you have imported a new form version, you need to apply the following configurations to start using it:

Composer

It is not possible to create and maintain form versions in Transact Composer. Instead, Transact Composer users may choose to import the Transact Composer package, which is the published form, as a new version.

Form versions contain the actual form template file, the form data configuration, property and metadata values, attachments and other information.

Next, learn how to configure a form version.