Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 56.1
edited by Erik Bakker
on 2023/03/03 11:35
Change comment: There is no comment for this version
To version 288.1
edited by Erik Bakker
on 2025/10/21 10:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -193 - Fan Out
1 +255 - Fine Form
Content
... ... @@ -1,24 +1,21 @@
1 -The release introduces REST/XML as an option for your gateway operations and 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 +This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready. Additionally, we will release a new **[[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]]** for selected customers and on our flow testing engine. On top of that, we will release new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** to allow specific customers to run on our MAM functionality.
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>>doc:Main.Release Information.Release Blogs.255 - Fine Form.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 learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V130.WebHome||target="blank"]].
8 -* 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)
9 -* 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 +* General - Runtime: A new [[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]], for selected customers, and our flow testing will be made available.
8 +* General: The user can now see the names of deactived users again across the platform (i.e. flow history, Q&A). (#1163)
9 +* Deploy - Releases: We have updated the editing release behaviour for the Event streaming pattern. You now have more flexibility for you to add or remove either Event streaming processor flow(s) or Event streaming Mendix connector flow(s) in the release.
10 +** Additionally, we have also fixed the issue where adding or removing event streaming flow(s) resulted in incorrect flow(s) being included or excluded. This update ensures that the correct Event streaming flow(s) are now properly managed during release editing.
11 +* Create - Add Integrations: Users can un-transfer event streaming integrations that have the default message type messaging by using the ‘Create/Settings/Transfer settings from design/ES Integrations’. (#1485)
10 10  
11 -=====Minor changes=====
13 +==== Bug fixes ====
12 12  
13 -* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
14 -* Design - API Catalog: When you change a path in the 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 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
16 -* Manage - Error messages: Message history is sorted by timestamp descending.
15 +* Design - Model Designer: Changed “align top“ and “align left“ to “align horizontally“ and “align vertically“ to be consistent with similar functionality in the Flow Designer. (#1611)
16 +* Create - Settings: The SOAP settings tab allows syncing the SOAP settings of systems in Design and Create. (#1569)
17 +* Create - Transformation: Updated the pattern used in dateTime transformations for the +HH:mm format. These used to fall back to +HHmm instead (dropping the ':'), this has now been resolved. (#1368)
18 +** Existing transformations are not automatically updated, but if you are using a custom XPath to do the transformation right now, you can now use the default functionality again.
19 +** The updated pattern (using XXX instead of ZZ) does not work on the previous generation runtime. If you are still using the previous generation runtime, and you have edited the specific part of the transformation, you can instead use the custom XPath where you use the pattern that is composed when using the dropdown menus, and replacing the XXX at the end with ZZ
17 17  
18 -====Bug fixes====
19 19  
20 -* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming. (#908)
21 -* Create - Migration: We fixed a third-generation migration issue where the legacy error handling flow components were not removed from the asynchronous routing flow.
22 -* 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.
23 -* Deploy - Release: We fixed an issue that caused images not to be built in specific situations when running in the new runtime generation runtime.
24 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)