MaestroPreviously known as Transact Maestro. | Form Builder | 21.11 This feature was updated in 21.11.
Maestro allows you to build a form as a TM Form Version ZIP file, which includes a FAR file and all related form's assets, so you can easily deploy it in a form space in Journey Manager. You develop and build the form in the same tool - the Maestro editor, which is handy and saves you time.
If the form containing multiple brands, you can build the form using one or many brands available to the form.
If you don't need to deploy a TM Form Version ZIP file right away, you can build and review it first, and import it into Manager later , when you need to. Usually, you import the TM Form Version ZIP file to Test and UAT environments, then you promote a form to a production environment by exporting and importing it using Manager's functionality.
To build the TM Form Version of a Maestro form:
Enter a new TM Form Version name in the TM Form Name field, in case you want to change it from the default name, which is the existing name of the form.
Specify Build Options to build the form according to your requirements:
This limits the list of available services you can configure for your form version, but you can configure Transact functions from the Functions tab in Manager, which becomes available, as shown below.
You can see whether the Transact function are available in a form when you configure a form version in Manager.
Transact functions require Journey Manager 17.10 and higher.
Code minificationMinification is the process of removing all unnecessary characters from the source code of interpreted programming languages or markup languages without changing its functionality. functionality has been enhanced in the following Maestro versions:
app.js and then minified, but not transpiledTtranspiler is a source-to-source translator, source-to-source compiler, transcompiler, which is a type of translator that takes the source code of a program written in a programming language as its input and produces an equivalent source code in the same or a different programming language..
Reducing the code makes it difficult to read it, so you have to consider deselecting the Minify Code checkbox when debugging the form.
When Maestro builds the form, it doesn't rebuild the receipt form. It simply takes the latest version of the receipt that has been built and checks whether the last update time on the receipt is after the last built time on the receipt or not. If the receipt has been changed since its last built, Maestro shows a warning that the receipt needs to be republished.
If the form containing multiple brands, Maestro gives you additional options to choose which brand, or all of them, to use to generate a TM Form Version.
Select the Build Specific Brands (no updates to the published form in JM. Built forms will be downloaded to the local file system) checkbox to see the the list of brands available to the form.
You can't the Build Specific Brands (no updates to the published form in JM. Built forms will be downloaded to the local file system) checkbox if the form has only one brand.
Specify Brands to build the form using specific brand or brands:
Click Build to build the form. Check the build result and perform some actions as described below.
Once a TM Form Version is built, you can download it at any time from the Maestro Management Dashboard using the Download JM Form Version option.
When building the TM Form Version, you may encounter some common errors, which you can resolve yourself.
Next, learn how to update TM Form Version.