Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 53.1
edited by Erik Bakker
on 2023/03/03 08:57
Change comment: There is no comment for this version
To version 225.1
edited by Erik Bakker
on 2025/02/10 09:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -193 - Fan Out
1 +238 - Preparation Paraside
Content
... ... @@ -1,23 +1,12 @@
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 finishing the first iteration of our new eMagiz Mendix Connector and the first iteration of our new base image. We will first utilize the new eMagiz Mendix Connector to get an even better feeling of its performance, but you will notice a UI change straightaway. Once we have passed that hurdle, we will share more information about it and release it to a broader range of customers. Regarding the base image, we will now introduce this to our flow testing offering to see if anything unexpected happens. This is an additional safety measure we have put in place to reduce the chance of something breaking in your model once the new base image is released. 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.238 - Preparation Paradise.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +====Minor Changes====
6 6  
7 -* 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.V130.WebHome||target="blank"]].
8 -* 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.
9 -* 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)
7 +* ILM: We defined the systems labeled as “isMendix” with the “MX“ icon, making it easier to identify the Mendix system.
8 +* Create - Flow Testing: As we are finalizing the new eMagiz runtime image that will update the Spring version to Spring boot 3.4.1 and Java to 17.0.13, we are now bringing these latest updates to flow testing. This means that any flow test you execute will run on the base image your runtimes will run on after the release of the new eMagiz runtime image. If one of your test cases suddenly exhibits weird behavior that you think is due to the update, feel free to contact us via our [[support department>>mailto:support@emagiz.com]].
10 10  
11 -=====Minor changes=====
12 -
13 -* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
14 -* 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)
15 -* Manage - Error messages: Message history is sorted by timestamp descending.
16 -
17 17  ====Bug fixes====
18 18  
19 -* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming (#908)
20 -* Create - Migration: We fixed a third generation migration issue, where the legacy error handling flow components were not removed from the asynchronous routing flow.
21 -* 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.
22 -* Deploy - Release: We fixed an issue that caused images to not be built in specific situations when running in the new runtime generation runtime.
23 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)
12 +* Create - Add Integrations: Integrations using the entry/exit connector, using the same message type, can now be untransferred from the create phase. (#1591)