Changes for page 243 - Migration Magic
Last modified by Erik Bakker on 2025/06/02 09:33
From version 82.1
edited by Erik Bakker
on 2023/05/22 15:19
on 2023/05/22 15:19
Change comment:
There is no comment for this version
To version 231.1
edited by Erik Bakker
on 2025/02/26 21:03
on 2025/02/26 21:03
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 - 198-GreatMigration1 +239 - Modern Talking - Content
-
... ... @@ -1,27 +1,18 @@ 1 - Anothercouple ofweeks havepassed,soitistimefor a newrelease. Wehavefocusedin thisperiod on improvingthemigrationprocesswards thenext-generation architecture as well ashowtheuserexperienceandinteractionwiththe next-generation architectureworks.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. 198-GreatMigration.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.239 - Modern Talking.WebHome||target="blank"]]. 4 4 5 -==== =Newfeatures=====5 +====New Features==== 6 6 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.** 7 7 8 -==== =Minorchanges=====11 +====Minor Changes==== 9 9 10 -* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete. 11 -* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too. 12 -* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component. 13 -* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not. 14 -* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes. 15 -* Deploy - Architecture: You can apply your changes to environment without having an active release. 16 -* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing. 17 -(control tower, so Gen3 only) 18 -* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments. 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) 19 19 20 20 ====Bug fixes==== 21 21 22 -* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models. 23 -* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information. 24 - 25 -====Remarks==== 26 - 27 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2. 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)