Changes for page 243 - Migration Magic
Last modified by Erik Bakker on 2025/04/22 14:08
From version 239.1
edited by Erik Bakker
on 2025/04/07 09:25
on 2025/04/07 09:25
Change comment:
There is no comment for this version
To version 232.1
edited by Erik Bakker
on 2025/02/26 21:08
on 2025/02/26 21:08
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 42-Stability Score1 +239 - Modern Talking - Content
-
... ... @@ -1,18 +1,18 @@ 1 -In the last sprint, we have releasedseveralitemsmproving thestabilityof theplatformacrossthevariousILMphases.Thebiggestchange wehaveisanew[[cloudtemplate>>doc:Main.ReleaseInformation.CloudTemplates.WebHome||target="blank"]]allowingmodels running onourcurrent-generation architecturetobetterutilizetheirCPUwithin thecloudmodels. On top of that, wereleasevarious improvementsinthe platformregarding clarity and stability.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.2 42-Stability Score.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 5 ====New Features==== 6 6 7 -* Cloud - Templates: We have implemented a feature for Cloud models to be able to consume an unlimited amount of CPU burst on their production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]. 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 28.** 8 8 9 9 ====Minor Changes==== 10 10 11 -* Store - Overview: Statistics tab in Store item details shows the number of imports and the models where a store item has been imported to, which is only visible to store admins. (#799) 12 -* eMagiz Connector - Softcrow: Softcrow restoration is added for the eMagiz Connector. 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) 13 13 14 14 ====Bug fixes==== 15 15 16 -* Create - Transformation: In the Transformation tab of the Create phase. Newly created attribute operations of type aggregator can freely switch positions with a destination filter using the move left or move right buttons. (#1307) 17 -* Create - Flow Designer: Updated help texts and documentation references that pointed to Joda time with the relevant Java DateTimeFormatter options to reflect the current state of libraries supported in the runtime images. 18 - 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)