MaestroThe UI design product. | Form Builder | All versions This feature is related to all versions.
Component versions work similarly to Form Versions. Once an initial version of a component is built, new versions of this component can be created to keep track of any changes made to the component as it grows and matures.
You can use the Maestro editor and the Maestro Dashboard to manage component versions:
To create a new component version from the Maestro Dashboard:
Journey Maestro prior to v17.10 doesn’t use semantic versioningSemantic Versioning is a formal convention for specifying compatibility using a three-part version number: major version; minor version; and patch. The patch number is incremented for minor changes and bug fixes which do not change the software's application programming interface (API). The minor version is incremented for releases which add new, but backward-compatible, API features, and the major version is incremented for API changes which are not backward-compatible. For example, software which relies on version 2.1.5 of an API is compatible with version 2.2.3, but not necessarily with 3.2.4., so components version numbers are increased incrementally by whole values, for example: version 1, version 2, version 3, and so on.
Journey Maestro allows you to choose which component version to open. When you double-click an existing component in the Maestro Dashboard, the latest version of the component is opened. However, sometimes you may want to open an earlier version of the component. This is usually the case when there are bugs or issues with the current version of a component and you want to open the working version to compare the configurations or even revert the changes.
There are two methods to open an existing version of a component in Maestro:
Journey Maestro prior to v17.10 doesn’t use semantic versioningSemantic Versioning is a formal convention for specifying compatibility using a three-part version number: major version; minor version; and patch. The patch number is incremented for minor changes and bug fixes which do not change the software's application programming interface (API). The minor version is incremented for releases which add new, but backward-compatible, API features, and the major version is incremented for API changes which are not backward-compatible. For example, software which relies on version 2.1.5 of an API is compatible with version 2.2.3, but not necessarily with 3.2.4., so components version numbers are increased incrementally by whole values, for example: version 1, version 2, version 3, and so on.
Next, learn how to add a component.