Tagged (locked version) Form Version Overview

   MaestroPreviously known as Transact Maestro.  |    Form BuilderPlatform Developer |  17.10 This feature was introduced in 17.10.

A tagged version of a form is a read-only form version that prevents any changes from being saved to the form. A tagged version is an effective way of keeping a clean, final record of a form. It is recommended that you create a tagged version each time a form is deployed to an environment. For instance, while you are developing a form, you should be using the "1.0-develop" form version; once this version of the form is ready for production and deployment to an environment, it is time to create a tagged version of the form. Once a new tagged version of a form has been created, it is possible to create new form versions based on a tagged version.

Since v17.10, the Journey platform follows open source semantic versioning conventions. Following this convention, all new form version names are recommended to start at version 1.0-develop until they reach production. In versions of Maestro prior to 17.10, form versions are incremented by whole numbers (for example version 1, version 2, version 3, etc.).