Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 210.1
edited by Carlijn Kokkeler
on 2024/03/25 12:27
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 -217 - Template Tango
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,17 +1,25 @@
1 -In the last sprint cycle, we focused on improving the event streaming graph. Moreover, we have done some bug fixes. First of all, the validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected.
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.217 - Template Tango||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 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.
6 6  
7 -* Create - Flow Designer & Deploy: Copy to clipboard buttons have been added to various pages.
8 -* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce the ability to clean H2 databases from the portal. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 -* Manage - Alerting: The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger.
10 -
11 11  =====Minor changes=====
12 12  
13 -* Deploy - Architecture: For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note that only H2 databases that are registered under the standard eMagiz data folder will be removed. Moreover, it is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. Lastly, for on-premise runtimes, only a reset of the runtime is needed.
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 -* Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)
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)