Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
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 239.1
edited by Erik Bakker
on 2025/04/04 08:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -193 - Fan Out
1 +2411 - Wild West
Content
... ... @@ -1,21 +1,10 @@
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 this additional unplanned release, we have corrected two problems within the platform that were causing problems for our customers. On top of that, we updated our infrastructure in light of a recently discovered vulnerability in one of the underlying platforms we use.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.193 - Fan Out.WebHome||target= "blank"]].
3 +====Bug fixes====
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 +* Overall - Feedback: Since our previous release, it has been impossible to issue feedback on our platform due to a tightened security policy. This problem has been fixed with this release.
6 +* Deploy - Releases: Due to our newly introduced feature regarding comparing properties, we lost performance when activating releases in models containing Mendix systems. As a result, users experienced delays in waiting for eMagiz to finish this process. This problem has been fixed with this release.
8 8  
9 -=====Minor changes=====
8 +====Remarks====
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.
14 -
15 -====Bug fixes====
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)
10 +* In light of a vulnerability discovered in one of the underlying platforms we use, we took proactive actions to safeguard our infrastructure against this even better.