Version | Date Released | Features and Enhancements | Resolved Issues | Downloads |
---|---|---|---|---|
19.05.16 | 14 June 2022 | ✓ | ||
19.05.15 | 7 December 2021 | ✓ | ||
19.05.14 | 27 September 2021 | ✓ | ||
19.05.13 | 06 July 2021 | ✓ | ||
19.05.12 | 23rd March 2021 | ✓ | ||
19.05.11 | 27th January 2021 | ✓ | ||
19.05.10 | 11th January 2021 | ✓ | ||
19.05.9 | 13th September 2020 | ✓ | ||
19.05.8 | 31st May 2020 | ✓ | ||
19.05.7 | 3rd February 2020 | ✓ | ||
19.05.6 | 13th December 2019 | ✓ | ||
19.05.5 | 5th November 2019 | ✓ | ||
19.05.4 | 11th September 2019 | ✓ | ||
19.05.3 | 28th August 2019 | ✓ | ||
19.05.2 | 20th August 2019 | ✓ | ||
19.05.1 | 13th August 2019 | ✓ | ||
19.05.0 | 5th July 2019 | ✓ | ✓ | ✓ |
Overview
Journey Maestro 19.05.0 is a major release of Maestro that introduces a number of new features.
For more information, refer to the Journey Maestro Documentation.
What's New
Receipt Designer
Prior to 19.05, Maestro offered two approaches to receipt generation:
- Rely on the auto-generated receipt as the cost of flexibility.
- Build a more flexible but complex solution via Journey Manager.
With 19.05 though, it's possible to create receipts directly within the Maestro editor. This means you can use the tools you're already familiar with to create receipts that are completely distinct from the forms that generate them. As a result, receipts are both flexible and simple to create.
To learn how to create a custom receipt in Maestro, refer to the Receipt Designer in Maestro.
Offline Builds
By downloading the Maestro command-line tool (CLI), it's now possible to build Maestro forms outside of the browser, via the command line.
This allows developers to:
- Have more control over their workflow.
- Reduce the amount of time it takes to build large forms.
- Integrate the Maestro build process with a CI/CD pipeline.
This feature is currently in beta release. If you want to know more, contact your account manager.
Upgraded AngularJS to 1.7.2
We have upgraded the version of AngularJS that we use from 1.5.9 to 1.7.2. We are not aware of any significant changes caused by this upgrade there is one minor change that we are aware of.
In AngularJS 1.6.0 there was a change that the click event will trigger before the data model is updated and before the change event is triggered. Using a click event on fields that will change when the user clicks on the field will trigger the click event first and then update the data model which triggers the change if it is different and the change rule will have the new value available in the rule. This will impact widgets that have click events and change events that come from the same user action such as:
- Check boxes.
- Radio button group.
- Dropdowns.
Using the click event on fields is generally discouraged as other than checkboxes a click does not indicate any change has happened and with this upgrade it no longer has the correct version.
Release Details
19.05.16
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.15
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.14
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.13
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.11
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.10
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.9
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.8
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.7
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.6
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.5
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.4
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.3
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.2
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.1
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
19.05.0
Features and Enhancements
The following table details the individual features that have been included in this release.
Key | Feature | Description |
---|---|---|
AVM-1973 |
Dropdown Component with Option to Sort |
A simple addition to this component to sort the options alphabetically by display value. If Sort option enabled
If sort option disabled
If translation is enabled and sorting is enabled
|
AVM-1963 |
Remove Receipt Pane from dashboard when project < 19.05 |
As a user I do not want the receipt pane shown when my project has been downgraded from 19.05 or greater.This is because the receipt design functionality is not supported in 19.05 or less. |
AVM-1947 |
Stop build when Receipt has not been built |
As a user of receipt designer, I want to see my receipt design in the build receipt association dropdownbut an error needs to be thrown if the receipt design has not been built in TM.This will ensure that the associated receipt can be included in the build. |
AVM-1923 |
OFFLINE BUILD - Include Receipt into the FAR file as part of offline build process |
As a form developer I want to create and then publish a separate receipt in the Maestro FAR file.This will allow the interactive form to be separate to the receipt but share the same data model. The build process needs to be modified to include a receipt for where one exists. |
AVM-1920 |
Add new Receipt List Pane in Dashboard |
As a form developer, I want to see the receipt designs separately from the other designs so I can easily work with receipts. The management dashboard requires a new pane located after Forms, titled "Receipts". The buttons within this new pane will be the same as the Forms pane however all references to "Forms" needs to be replaced by "Receipts" |
AVM-1919 |
Receipt Version Screen |
As a user I want to have the same user experience for my receipt development as I do for forms so that I won't have to context switch. For the Versions screen it will look identical to the Form version screen except for the Receipts icon |
AVM-1902 |
In Receipt design editor pane change Preview options |
As a user I want to be able to preview my receipt design so I can determine progress of my work.The current options available in a form design will need to change to reflect whether the preview is HTML or PDF receipt only. |
AVM-1898 |
Add Receipt Folder in Dashboard Tree |
As a receipt developer I want to be able to have my receipt designs stored separately to my other designs so that I can identify these designs easily.The dashboard tree will be modified to add a new Receipts folder and designs of type Receipt will be found there.
|
AVM-1894 |
ONLINE BUILD - Include Receipt into the FAR file as part of online build process |
As a form developer I want to create and then publish a separate receipt in the Maestro FAR file.This will allow the interactive form to be separate to the receipt but share the same data model. The build process needs to be modified to include a receipt for where one exists. |
AVM-1861 |
Add New Build option - select a receipt |
As a Maestro user I want to be able to select a receipt version to associate to my form at Build time so that it will be include in the FAR file and be available in Manager. |
AVM-1806 |
Video Capture Component |
As a Maestro client, we want to be able to use a video capture component in our application so that we can verify the user's identity via a gesture. Acceptance Criteria Capture Video and Audio on the devices/browsers below:
Have rules that fire when:
|
AVM-1619 |
Package the CLI build system for release |
Determine and implement the approach for packaging and delivering the CLI tool to customers. Determine and implement the means of publishing and distributing the Maestro release libraries. |
AVM-1463 |
Create a receipt template |
As a maestro developer I do not need to see all the form components in the palette when I am designing a receipt, I would like the no relevant components removed from the palette so that they aren't used in receipts. |
AVM-1459 |
Add receipts folder to existing projects when upgraded to 19.05 |
As Maestro users we would like the receipts folder to be added to our existing projects when upgraded from any version to allow us to work with receipts. Acceptance Criteria
|
AVM-846 |
Implement Upgrade Angular to 1.7 |
Version 1.5.9 is being flagged with security vulnerabilities. Ensure we use the latest version. |
AVM-177 |
CALC - API methods documentation code snippet examples |
As a Maestro form developer, I would like to get more guidance when looking into the API methods documentation so that I would be able to learn about the methods better when looking how to use the code. |
Resolved Issues
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.
Downloads
You need to login to access this content. If you still don't have access after logging in, you can request it by posting a new question and selecting the access you need in the Type dropdown.