Form Versions Overview
Journey Manager (JM)
The transaction engine for the platform. |
Form Builder
Platform Developer | 17.10
This feature was updated in 17.10.
Manager offers a flexible mechanism to create and preserve 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.
You usually create a new form version in Maestro and then build a form version of the form and publish it in Manager.
This is the recommended approach as it is more manageable and easier to keep the form versions in sync across Maestro and Manager.
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.
To start using a new form version, you need to apply the following configurations to:
- Form version details
- Form version functions
- Form version services
- Form version attachment rules
- Form categories
- Form design info
- Job properties
- Job info
You can change the current form version at any time, whether to roll out a new release or roll back to an older version. The current form version is used whenever a user requests the form.
Next, learn how to configure a form version.