MaestroPreviously known as Transact Maestro.
In this topic, we're going to design a receipt using Maestro's Receipt Designer feature (available from v19.05). Creating a receipt in Maestro is very similar to creating a form, so only a basic understanding of form development is required.
To begin, create a form with "First Name" and "Last Name" text fields.
To make the form submittable without any further configuration, select the Maguire - Default Form template when creating the form. This isn't strictly necessary though, as we can use a Receipt Test Harness to test the receipt without navigating and submitting the form.
In the same project as the form:
In a real-world project, we recommend creating and publishing a custom receipt template based on an existing receipt template. Functionally, receipt templates are identical to form templates, so all standard templating practices apply.
After the receipt opens in a new window, drag two text fields into the receipt.
For the data from a form to appear in the receipt, the fields need to have the same XML path. To accomplish this, we suggest creating a domain model and sharing it between the receipt and form. In this topic however, we'll just manually ensure the component IDs are the same.
Change the ID of the first text field to "firstName" and the ID of the second text field to "lastName". Their labels should automatically regenerate.
By default, XML names are auto-generated based on component IDs. If this option is disabled via the Integration properties, you'll need to manually set the XML names rather than the component IDs.
So far we've recreated the form in the receipt, but typically, receipts will look different from their forms.
Here is one example of how to approach this:
return data.firstName + " " + data.lastName;
This code concatenates the first name and last name into a single line of text.
To see this, switch to the Preview tab and fill out the First Name and Last Name fields. The Name field will update with the combined result of these values.
Finally, click Build to make the receipt available to the form.
Multiple forms can use the same receipt.
Whether or not a custom receipt has been designed in Maestro, the process of deploying a form to Journey Manager is the same.
Rather than testing the receipt by repeatedly submitting the form, use Manager's Receipt Test Harness feature:
The receipt, as shown below, contains the data from the form:
This is a simple receipt, but it does demonstrate:
With these fundamentals, it's possible to create more complex receipts.