Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 87.1
edited by Erik Bakker
on 2023/06/06 08:21
Change comment: There is no comment for this version
To version 23.1
edited by Erik Bakker
on 2022/11/21 13:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +188 - Close Encounters
Content
... ... @@ -1,19 +1,25 @@
1 -In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture, the store, security, and certificate management.
1 +The release brings several improvements to our 3rd generation runtime and the interaction with it. On top of that, we have several feedback items and bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.WebHome||target="blank"]].
4 4  
5 +=====New features=====
6 +* Design - Store: It is now possible to import Transformations and Data Models from the store into a model.
7 +** The Design Store can also be opened from the Mapping and Data Model screens.
8 +** The Design Store now offers search options for store items, including Transformations and Data Models.
9 +** When importing a Store item with a Transformation or Data Model, a new merge tool is available to link the Store Items data model to the users' data model or to add new attributes/entities to the user data model.
10 +** When importing a Store item with a data model that has been previously linked, the links are automatically restored, allowing for easy updating of store-based Integrations and easier installation of multiple Store items with the same data model.
11 +
5 5  =====Minor changes=====
6 6  
7 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
8 -* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899)
9 -* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately three months before event streaming users' access certificates expire.
10 -* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan.
11 -* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960)
12 -* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.
13 -* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.
14 +* Create - Flow Designer: Code mapping is now available for models migrating to the 3rd generation runtime
15 +* Create - eMagiz Mendix Connector exit: Download buttons are added for non-legacy eMagiz Mendix connectors.
16 +* Create - Overview: You will now see your errors within a flow but on the Create - Overview. To activate this, open your flow, and the number of errors you have in it, if any, will update so that next time, you don't have to navigate inside the flow to check how many alerts you have.
14 14  
15 -====Bug fixes====
16 16  
17 -* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864)
18 -* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937)
19 -
19 +====Bug fixes====
20 +* Design - Store: Importing store items from response messages doesn't cause issues anymore.
21 +* Design - Store: Importing response messages and transformation to API integration is possible.
22 +* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document. (#783)
23 +* Create - Flow Designer: Ensure that the copy and pasting experience works for all flows.
24 +* Create - Flow Designer - Store: We fixed the maintaining selection of flow fragments from the store.
25 +* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed. (#744)