Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 43.1
edited by Erik Bakker
on 2023/01/18 11:41
Change comment: There is no comment for this version
To version 231.1
edited by Erik Bakker
on 2025/02/26 21:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +239 - Modern Talking
Content
... ... @@ -1,32 +1,18 @@
1 -The release finished many new improvements to our 3rd generation runtime offering and fixed various annoying bugs and minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
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.190 - Fast Forward.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=====
6 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
7 -* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your JMS server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
5 +====New Features====
8 8  
9 -=====Major changes=====
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.
9 +** We will publish the new module to the Mendix Marketplace on **February 28th.**
10 10  
11 -* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
11 +====Minor Changes====
12 12  
13 -=====Minor changes=====
13 +* 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)
14 14  
15 -* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes.
16 -* Create - Flow designer: sensitive information stored in property values is masked. (#790)
17 -* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions.
18 -* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
19 -* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
20 -* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828)
21 -* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
22 -* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
23 -* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
24 -
25 25  ====Bug fixes====
26 -* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
27 -* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793)
28 -* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
29 -* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
30 -* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
31 -* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
32 32  
17 +* 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)
18 +* 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)