| Version | Date Released | Features and Enhancements | Resolved Issues | Downloads |
|---|---|---|---|---|
| 18.05.15 | 23rd March 2021 | ✓ | ||
| 18.05.14 | 27th January 2021 | ✓ | ||
| 18.05.13 | 13 September 2020 | ✓ | ||
| 18.05.12 | 31st May 2020 | ✓ | ||
| 18.05.11 | 3rd February 2020 | ✓ | ||
| 18.05.10 | November 5, 2019 | ✓ | ||
| 18.05.9 | September 11, 2019 | ✓ | ||
| 18.05.8 | August 13, 2019 | ✓ | ||
| 18.05.7 | July 5, 2019 | ✓ | ||
| 18.05.6 | February 15, 2019 | ✓ | ||
| 18.05.5 | December 7, 2018 | ✓ | ||
| 18.05.4 | October 2, 2018 | ✓ | ||
| 18.05.3 | July 31, 2018 | ✓ | ||
| 18.05.2 | July 11, 2018 | ✓ | ||
| 18.05.1 | June 26, 2018 | ✓ | ||
| 18.05.0 | May 31, 2018 | ✓ | ✓ |
Overview
Transact Maestro 18.05.0 is a major release of Maestro introducing a number of significant new features and important bug fixes.
For more information, please see the official Transact Maestro Documentation.
What's New
The Maestro 18.05 release introduces several new features and expands on some existing features that were introduced in Maestro 17.10. Maestro 18.05 not only introduces support for shared domain models but also changes the way entities are configured and handled in a Maestro form. Domain models are composed of entities, and in Maestro 18.05 every new Maestro form is created with a default but separate JSON format domain model. Maestro 18.05 also streamlines the way translation files are handled and created in Maestro. Unlike previous versions of Maestro, translation files are now stored as CSV files that can be downloaded and edited outside of Maestro before being uploaded back into the Maestro from with updated translation values.
Maestro 18.05 extends the semantic versioning feature introduced in Maestro 17.10, adding support for semantic versioning of libraries. This allows new versions of Maestro libraries to be created, edited, uploaded and downloaded across multiple Maestro forms.
In addition to these features, the Card Content Template component has been added to the Maestro Palette. This component combines the functionality of both the Card Content and Card Selector components and has been developed to streamline card-based layouts.
Along with these features and improvements, the Maestro User Interface ushers in several name changes. The Structure panel has been renamed to View and the Entities panel has been renamed to Model.
Key Features
Semantic Versioning of Libraries
In Maestro 18.05, libraries support three-level semantic version numbers, just like forms and components. This support allows a new library version to be created, edited, imported and exported. Once a library version is created, it can then be designated as the active version of that specific library. An active library version is the version of the library that will be used by forms with access to the library.
Documentation on semantic versioning of libraries can be found in the Libraries section of the Maestro documentation
Translation and CSV
Maestro 18.05 now stores translation files as CSV files which allows translators to export language files and work on them outside of Maestro using tools such as Microsoft Excel. Once a translation file has been edited outside of Maestro, it can then be uploaded back into Maestro with the updated translation values.
Documentation on Translation and CSV files in Maestro can be found in the Working with Translation CSV Files section of the Maestro documentation.
Card Content Template Component
Maestro 18.05 adds the Card Content Template component to the Maestro palette. This component has been designed to simplify card-based layouts.
Documentation on the Card Content Template component can be found at Card Content Template.
Shared Domain Models
In Maestro 18.05, a Domain Model is created automatically when a new Maestro form is created. The structure of a Domain Model in Maestro is based on JSON schema. All Domain Models are made up of entities and entity properties. Maestro 18.05 stores all entities in the Domain Model rather than in the Maestro form. Domain Models can be shared to other forms via libraries. After a Domain Model has been shared via a library, it can be used by any form with access to that library.
Documentation on Domains and the shared domain models approach, can be found in the Shared Domain Models section of the Maestro documentation.
Changes to existing functionality and UI changes
Several new UI changes have been made to the Maestro interface. The Structure panel has been renamed to View - to better describe what is being displayed in the Maestro editor. Also, the Entities panel has been renamed to Model - to reflect that this panel shows more than just the entities themselves, such as the relationships between various entities.
The screenshot below highlights these changes.
Known Issues
1805 forms now support new es6 constructs. The Phantom receipt rendering engine will not render forms in Transact Manager unless they have been minified at build time. This build option is now the default.
Insights Support
Insights support for Transact Maestro 18.05 applications is only available with Transact Manager 18.05. If you still want to use Transact Maestro 18.05 but cannot upgrade to Transact Manager 18.05, please uncheck the Insights flag on the Application in Transact Manager.
Release Details
The following table details the individual bug fixes and defects that have been addressed in this release.
18.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.
18.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.
18.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.
18.05.12
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.
18.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.
18.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.
18.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.
18.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.
18.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.
18.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.
18.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.
18.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.
18.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.
18.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.
18.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.
18.05.0
Features and Enhancements
| Reference | Summary | Description | Feature |
|---|---|---|---|
| AVM-885 | Set default library version number |
Added ability to set the initial default value of a library version on the project details panel. This means that newly created library versions will default to this value. |
Library Semantic Versioning |
| AVM-259 | Ability to edit a library version | Added ability to edit an individual library version details. | Library Semantic Versioning |
| AVM-176 | Existing Library - Create a new version of an existing library | Added ability to created a new library version based on a previously existing library version. | Library Semantic Versioning |
| AVM-261 | Ability to export a library version | The library export function now takes library versioning into account. A user can select the version they wish to export from a list. | Library Semantic Versioning |
| AVM-522 | Ability to import a library version |
The import library function has been modified to take library versioning into account. Imports will not overwrite existing libraries with the same name and version number. |
Library Semantic Versioning |
| AVM-390 | Consolidate duplicate library names in dashboard |
The library tree structure will only show one instance of the library/version in its list. This is the version that is mapped to the project or organization. |
Library Semantic Versioning |
| AVM-258 | Ability to create a new library version | Added ability to create and add a new library version. | Library Semantic Versioning |
| AVM-169 | Introduce a new column for (library) versions at project level | Added display for library versions in the Maestro dashboard. | Library Semantic Versioning |
| AVM-260 | Ability to delete a library version | Added ability to delete a library version. | Library Semantic Versioning |
| AVM-302 | Display the library tree structure | Added ability to display all versions of a library in a tree structure. | Library Semantic Versioning |
| AVM-391 | Dashboard to perform operations on library versions | Added interface to create and manage library versions. | Library Semantic Versioning |
| AVM-173 | Store library version number in TM | Added ability to store library versions in Transact Manager. | Library Semantic Versioning |
| AVM-174 | Create a parent node to hold library versions | Added folder in the tree structure to hold multiple library versions. | Library Semantic Versioning |
| AVM-175 | Create a tree structure similar to form designs | Added tree structure to display library versions. | Library Semantic Versioning |
| AVM-253 | Drop down of versions choice for libraries | Added dropdown to select and map a library version to a library ( make a library version the 'active' version of the library. | Library Semantic Versioning |
| AVM-172 | Allow the publishing of assets to a library version | The publish Maestro assets function can now update a single library version. | Library Semantic Versioning |
| AVM-888 | Move delete and export functionality from Dashboard to Library Version level | Moved delete and export buttons from the Maestro Dashboard to the library interface. | Library Semantic Versioning |
| AVM-168 | Create a new modal dialog to create new library | Added modal dialog to create a new library version in the Maestro interface. | Library Semantic Versioning |
| AVM-171 | Ability to map library versions | Added ability to select an active version of a library. | Library Semantic Versioning |
| AVM-492 | Migrate existing multi-lingual forms to CSV format | Existing translation files can be exported as CSV files. | Translators workspace support |
| AVM-183 | Shared translation resources | Added SCM support for global translation files. | Translators workspace support |
| AVM-301 | Download CSV translation file | Added ability to download a configured language as a translation CSV file. | Translators workspace support |
| AVM-181 | Upload single language CSV translation file | Added ability to upload a single translation CSV file to a Maestro form. | Translators workspace support |
| AVM-304 | Import CSV translation file for additional multiple languages | Added ability to import multiple translation CSV files to allow a Maestro form to support multiple languages. | Translators workspace support |
| AVM-960 | Remove broken links icon from all components with auto-gen ids | Removed broken link icons from all components with automatically generated Component IDs. This change was made to coincide with the improvements made to entities and domain models. | Shared entity model |
| AVM-998 | Add warning when attempting to change shared model | Added a warning message that will display when a user makes changes to a model that has already been shared. This warning informs the user that their changes will not be reflected in the model that has already been shared. | Shared entity model |
| AVM-959 | Include JSON file in TM FAR file at publish | Added the Maestro form domain model JSON file (entities.json) to the TM Far file so that it can be used by TM users. | Shared entity model |
| AVM-1001 | Allow a JSON schema to be loaded from the Manage Models Panel | A JSON schema can be loaded to allow users to create a domain model based on the JSON schema. | Shared entity model |
| AVM-940 | Domain model editing | Added ability to edit a domain model. | Shared entity model |
| AVM-930 | Ability to import a data model for a form (XML or JSON) | Added ability to import a domain model based on an XML or JSON file. | Shared entity model |
| AVM-939 | Domain Model sharing | Added ability to share a domain model across a project or organization. | Shared entity model |
| AVM-933 | Ability to apply a model from a different library | Added ability to select a domain model that was shared with a library and apply it to a different form. | Shared entity model |
| AVM-641 | Extract the model from the manifest to a separate resource | Added ability to export a domain model as a JSON file. | Shared entity model |
| AVM-525 | Model change handling | Added ability to edit/update a domain model. | Shared entity model |
| AVM-524 | Ability to import data model for a form (XML or JSON) | Added ability to import a domain model into a Maestro form. | Shared entity model |
| AVM-986 | Make a change in the UI to show local copy of shared model | Added identifier when a domain model is local and not shared. When a domain model is local, it will display as, LOCAL. | Shared entity model |
| AVM-1066 | Highlight unbound model nodes in entity tree | Added a highlight to fields that have not been mapped to a domain model. | Shared entity model |
| AVM-1090 | Restrict sharing of domain models. | Added restriction to who has permission to share a domain model (only users assigned the Maestro Administrator role can share domain models). | Shared entity model |
| AVM-873 | Create new card component to simplify user experience | Added Card Content Template component to the Maestro palette. | Card layout enhancement |
| AVM-851 | Card Layout save card selection for save and resume | Added ability for the component to save the field that the user was last on when the form was last saved. | Card layout enhancement |
| AVM-850 | Card Layout error navigation | Added error messages to the Card Content Template component. | Card layout enhancement |
| AVM-912 | Legacy import button has been removed from users. | The import legacy project functionality is largely redundant. This function is now restricted by a permission. | General Updates |
| AVM-995 | Support new Open UX API functions | Added support for the following Open UX REST API functions.
|
Open UX API |
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.