Changes for page 237 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 21.1
edited by Erik Bakker
on 2022/11/08 09:01
on 2022/11/08 09:01
Change comment:
There is no comment for this version
To version 163.1
edited by Carlijn Kokkeler
on 2023/11/23 08:56
on 2023/11/23 08:56
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 187-Integration Sponsor1 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,29 +1,29 @@ 1 - ThereleasebringsthenextstepoftheDesign storeto the publicandreleasesa newversionofthe eMagizMendixConnectorthatunlocksthoseusingit to migratetothe nextgenerationruntime.Ontop ofthat, wehave several feedback items and bug fixes.1 +In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 187-Integration Sponsor.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]]. 4 4 5 -===== Runtime Release Notes ===== 6 - 7 -The 6.0.0 release of the eMagiz Mendix connector (EMC) is here. This eMagiz Mendix connector (EMC) version is compatible with the 3rd generation runtime. On top of that, it includes updates on most of the userlib libraries to have the latest security fixes in place. For specific information, please check out this link to the [[release notes>>Main.Release Information.Runtime.eMagiz Mendix Connector - 600.WebHome||target="blank"]]. 8 - 9 9 =====New features===== 10 -* Design - Store: It is now possible to import Transformations and Data Models from the store into a model. 11 -** The Design Store can also be opened from the Mapping and Data Model screens. 12 -** The Design Store now offers search options for store items, including Transformations and Data Models. 13 -** 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. 14 -** 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. 15 15 7 +* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. 8 +* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 9 +* All - The next generation architecture is the default now. New models will use this generation as default. 10 + 16 16 =====Minor changes===== 17 17 18 -* Create-Flow Designer:Improved thehelptexts of theKafkacomponentstoexplain specificperformanceandload-balancingconsiderationsbetterand added detailed information onhowmessages(includingheaders)areconvertedto/fromKafka records.19 -* Create -eMagiz Mendix Connectorexit:Downloadbuttons areaddedfor non-legacyeMagiz Mendixconnectors.20 -* Create -Overview:You will now see yourerrors within a flowbutontheCreate- Overview. Toactivatethis, open your flow, andthe number oferrorsyouhavein it, if any, willupdateothatnexttime, youdon'thavetonavigateinsidetheflowto checkhow manyalerts you have.13 +* Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 14 +* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps. 15 +* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server. 21 21 22 - 23 23 ====Bug fixes==== 24 -* Design - Store: Importing store items from response messages doesn't cause issues anymore. 25 -* Design - Store: Importing response messages and transformation to API integration is possible. 26 -* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document. 27 -* Create - Flow Designer: Fix bugs when copying and pasting components in the G3 configuration. 28 -* Create - Flow Designer - Store: We fixed the maintaining selection of flow fragments from the store. 29 -* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed. (#744) 18 + 19 +* Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas. 20 +* Create - Flow Designer: We added a migration step to set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false. 21 +* Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. 22 +* Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture. 23 + 24 + 25 + 26 + 27 + 28 + 29 +