Changes to the generation of AMM
- AMM files have been amended with storage options for all new configuration elements. They will be included if Save Configuration is selected in the AMM editor. Tags can be set for the new configuration elements, and they are listed for selection in the Find Meta-Model Objects for Deployment functionality:
- widgets defined for cards
- content areas
- data workbench report groups
- global filter parameters
- property groups
- UI groups
- UI themes
- global filter parameters
- The following additional configuration parts are stored in database tables and can be uploaded to an AMM file via the Reference Data tab of the AMM file editor:
- Data Quality Rule Groups
- Data Quality Rules
- Data Workbench Default Views
- Content Area Default Views
- Help Context Contents
In the Meta-Model Content tab, the option Save Icons should also be included to upload the images in the Help Content Images icon gallery relevant for the selected help context content. alternatively, the Find Meta-Model Objects for Deployment can be used to add individual icons to the AMM file.
- Assemblies are no longer stored in the database but in the installation folders of the components. In the editor for generation of an AMM file the Assemblies tab has been removed.
- Each Alfabet configuration has a name and version. This information is visible and editable in Alfabet Expand in the Admin tab as attributes of the Environment node. The information is by default added to AMM files and overwritten in the target configuration. It can be excluded with the new checkbox Include Configuration Name and Version in the Meta-Model Content tab of the AMM editor to maintain the configuration name and version in the target database.