Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 52.1
edited by Erik Bakker
on 2023/03/03 08:50
Change comment: There is no comment for this version
To version 229.1
edited by Erik Bakker
on 2025/02/25 08:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -193 - Fan Out
1 +239 - Modern Talking
Content
... ... @@ -1,21 +1,17 @@
1 -The release introduces REST/XML as option for your gateway operations as well as new features for our 3rd generation runtime, a new runtime image, and new cloud templates. Subsequently, we will release several minor feedback points and 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 to our community. With this release we will make available for all new Mendix systems in models running on the current-generation architecture. Subsequently we will implement 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.193 - Fan Out.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 -* Deploy - Releases: New release properties pop-up that shows all properties in your release, grouped by containers that they are assigned to. This pop-up can be accessed by pressing the wrench shaped icon, which becomes available once a release is set as active.
7 -* Design - Settings: We added XML support to API Management. To enable this feature, change the 'Default message format' in the Design settings section. You can change individual operations by changing the message format of your gateway message. Migrating existing operations requires a reset of the exit flow and a change in the catalog in Design. For more information see the release blog post. (#815)
5 +====New Features====
8 8  
9 -=====Minor changes=====
7 +* New Mendix connector: We will introduce a new eMagiz Mendix connector. This new connector delivers improved stability and a simpler setup process. The new connector is better integrated in 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 which allows you to easily and smoothly migrate your current legacy Mendix connectors to the new Mendix connector.
10 10  
11 -* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
12 -* Design - API Catalog: When you change a path in Design phase, your HTTP inbound gateways that use the changed path will also be updated in Create phase if you have edit rights. (#524)
13 -* Manage - Error messages: Message history is sorted by timestamp descending.
10 +====Minor Changes====
14 14  
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 view mode of the Flow Designer. (#870)
13 +
15 15  ====Bug fixes====
16 16  
17 -* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming (#908)
18 -* Create - Migration: We fixed a third generation migration issue, where the legacy error handling flow components were not removed from the asynchronous routing flow.
19 -* Create - Flow designer: when migrating a container’s flows from gen2 to gen 3, “global wire tap” components and their relevant components will be removed.
20 -* Deploy - Release: We fixed an issue that caused images to not be built in specific situations when running in the new runtime generation runtime.
21 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)
16 +* Create - Flow Creation: Payload root Qname support object for the API gateway infra is not containing duplicates now. (#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 [id].[system].[flow] convention, or when that value is longer than expected. (#1566)