Skip to Content

Changes for page 270 - Round Round

Last modified by Erik Bakker on 2026/06/15 10:37
From version 46.1
edited by Erik Bakker
on 2023/01/31 14:51
Change comment: There is no comment for this version
To version 340.1
edited by Erik Bakker
on 2026/06/15 10:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +270 - Round Round
Content
... ... @@ -1,53 +1,21 @@
1 -The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
1 +This release includes improvements to our certificate rotation mechanism, which are relevant to all customers using our event streaming offering. On top of that, new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** are released. Furthermore, additional accelerants for all integration developers are here. This includes improvements in how we assist users in Capture, Design, and Create at the system level. Subsequently, we introduced a fix to improve the stability of interacting with Create via the flow designer and when adding and removing integrations. Enjoy reading our latest updates on the platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.270 - Round Round.WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -* Deploy - Architecture: We added the possibility to register network shares in your container volume settings. This enables the use of network shares without having to mount them manually on the host machine and then again on container level. This option is only available for 3rd generation runtimes that run on-premises.
7 -* Deploy - Containers: In Deploy containers a ‘Debug’ option is added for flows on the 3rd generation eMagiz runtime.
8 -** This option will temporarily be available for users on the next generation runtime. It allows to easily wiretap messages from channels in a flow to a queue, which can the be browsed using the queue browser. One flow can be wiretapped at the time, per container.
9 -** To use this option, the model must be fully migrated to Gen3, including the JMS which also needs to be reset. Additionally only flows in a container that has the Gen3 Debugging components inside of the associated container infra flow can be debugged. For more information on how to setup debugging on Gen3, please consult the documentation.
10 -* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
11 -** Error Message is to evaluate the headers of the original message which resulted in an error.
12 -** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
13 -** Queue Consumers is to configure for queues where more than 1 consumer is expected.
14 -** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
15 -** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow.
5 +==== Minor Changes ====
16 16  
17 -=====Minor changes=====
7 +* General - Environment Templates: New **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** are released. Make sure to update before **August 15th, 2026**.
8 +* General - Event Streaming: Managing the rotation of customer intermediate certificates before they expire to keep the environment operational.
9 +* Design - System: On API-related systems, we stop activating the “OpenAPI” checkbox by default, as it was not used often enough to warrant the default behavior. (#1794)
10 +* Design - System: When activating the “OpenAPI” option and neglecting to supply any operation, you are confronted with a message specifying what you forgot when pressing Save. (#1794)
11 +* Design - System: Fixed an inconsistency in Event Streaming systems regarding the selected default message format. As a result, we will no longer alter the default message format when saving the corresponding system in Capture. (#1794)
12 +* Create - Add Integrations: A more informative message is shown to the user if and when an automated flow configuration has failed. Additionally, the SOAP integrations can be recreated and edited. (#1377)
13 +* Create - Add Integrations: Fixed a specific case where changing a system to be a Mendix connector in the design phase did not correctly influence the deploy phase.
14 +* Create - Overview: We allow users to open (and reset) connector infra flows for on-premises API systems via the context menu. This makes the navigation to these connector infra flows consistent across patterns. (#1297)
15 +* Create - Flow Designer: A JMS outbound channel adapter can be saved without getting an alert when using a destination expression.
16 +* Create - Flow testing: XML test messages created based on a message definition will now contain randomized data.
17 +* Deploy - Releases (Swagger UI): Ensure that when you click the “Swagger UI” button in Deploy Releases, you are always redirected to the corresponding Swagger UI page, not the home page of our platform. (#1797)
18 18  
19 -* Data-Limit: Set data limit per environment.
20 -* Login page: Login page /login.html now redirects to the real login page /p/login. (#671)
21 -* Create - Flow designer: Removed the unnecessary refresh button from the component creation pop-ups. (#858)
22 -* Create - Flow designer: Properties in the property overview pages are sorted as Test/Acceptance/Production. (#804)
23 -* Create - Flow designer: We improved validation and help text on Wss4J interceptors components. (#733)
24 -* Create-Flow testing: Improved the help text when adding a header type for a test message. It now clearly states which types of Java classes can be used along with some examples. (#742)
25 -* Deploy - Releases: Setting a release as active by pressing the deploy button creates an entry in the deploy history. (#823)
26 -* Deploy - Releases: We improved the notification popups of failed machine deployments.
27 -* Deploy - Releases: We added column sorting to the popup showing the missing properties. (#860)
28 -* Deploy - Architecture: New cloud slots have their auto-upgrade value set to true by default. (#841)
29 -* Deploy - Architecture: A docker container's status is more visible when you open detail page of the docker container.
30 -* Deploy - Architecture: On the detail page about an instance, the state of the instance is now visible. (#699)
31 -* Deploy - Architecture: We changed the wake-up time of cloud slots on Fridays to 6:00 UTC, so that they no longer fall within our regular deployment windows. (#559)
32 -* Deploy - Architecture: We added runtime memory checks to ‘Apply to environment’, to prevent invalid deployments. (#719)
33 -* Deploy - Properties: We improved runtime selection when copying properties. (#796)
34 -* Manage - Explore: Improved the displayed error message when a message could not be loaded in the message redelivery screen. (#696)
35 -* Manage - Explore: “Save as test message” button opens a pop-up that allows you to edit your test message’s name, description, content and headers before saving it.
36 -* Manage - HTTP statistics: Fixed a typo in HTTP statistics dashboard. (#856)
37 -* Manage - Alerting: By default, no filter is applied to Status when navigating to Notifications, or resetting the filters on Notifications. (#486)
19 +==== Bug fixes ====
38 38  
39 -
40 -====Bug fixes====
41 -
42 -* Design - Solution design: We hide systems without functional integration now. (#714)
43 -* Create - API Gateway: Security header case insensitive
44 -* Create - Flow designer: Enabling redelivery for you integration is applied after resetting your offramp and exit flow. Before this change, you needed to remove and add the integration to Create phase to apply this setting.
45 -* Deploy - Containers: Applied styling to the error pop-up with the list of reasons why a runtime can’t be deleted to make it easier to read. (#546)
46 -* Deploy - Architecture: Deploying your model to the cloud for the first time, required you to press ‘Apply to Environment’ twice. This is no longer the case. (#508)
47 -* Deploy-Volumes: Network volumes visible when container not deployed.
48 -* Manage - Monitoring: Fix typo in Event Proccessors Metrics. (#835)
49 -
50 -====Remarks====
51 -
52 -* Mendix Runtime has been upgraded to Mendix 9.21.0.
53 -
21 +* Create - Flow Designer: A fix has been implemented to resolve an issue where an error popup would occasionally appear when opening the Flow Designer. (#1644)