Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 162.1
edited by Carlijn Kokkeler
on 2023/11/22 15:02
Change comment: There is no comment for this version
To version 230.1
edited by Erik Bakker
on 2025/02/25 08:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +239 - Modern Talking
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,33 +1,17 @@
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.
1 +In the last sprint, we focused on testing the eMagiz Mendix Connector and solving internal feedback on the process and the connector itself. With that behind us, we are ready to launch the new eMagiz Mendix Connector in our community. With this release, we will make it available for all new Mendix systems in models running on the current-generation architecture. In a future release, we will bring a migration wizard aiding a simple and smooth migration to the new eMagiz Mendix Connector. On top of that, we have some minor updates to improve the quality of the platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.239 - Modern Talking.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +====New Features====
6 6  
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.
7 +* New Mendix connector: We will introduce a new eMagiz Mendix connector. This new connector delivers improved stability and a simpler setup process. It is better integrated into your eMagiz models and will receive full support. The connector can be used for new systems and will be enabled by default for new models.
8 +** A migration wizard will be released later, allowing you to quickly and smoothly migrate your legacy Mendix connectors to the new Mendix connector.
10 10  
11 -=====Minor changes=====
10 +====Minor Changes====
12 12  
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 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
15 -* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
16 -* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
12 +* Create - Flow Designer: The view button that can be found by navigating to the right panel of the Flow Designer and choosing the Support Objects tab opens a pop-up that shows a list of all support objects that can be added. This button is accessible only in the view mode of the Flow Designer. (#870)
17 17  
18 18  ====Bug fixes====
19 19  
20 -* 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.
21 -* 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.
22 -* 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.
23 -* 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.
24 -
25 -====Infra and image changes====
26 -
27 -* Infra: New logging feature enabling us to make better choices in encryption standards.
28 -
29 -
30 -
31 -
32 -
33 -
16 +* Create - Flow Creation: When creating the corresponding infra and entry flows belonging to a system that will host a SOAP endpoint, we fixed a bug causing two support objects to break upon creation. (#1517)
17 +* Manage - Dashboard: The manage phase dashboard no longer breaks when an error occurs in a component with an id that does not follow the {{code}}[id].[system].[flow]{{/code}} convention, or when that value is longer than expected. (#1566)