Skip to Content

Changes for page 249 - Amendment Avalanche

Last modified by Erik Bakker on 2025/07/14 08:06
From version 260.1
edited by Erik Bakker
on 2025/06/02 09:55
Change comment: There is no comment for this version
To version 271.1
edited by Erik Bakker
on 2025/07/14 08:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -246 - Preparation Paradise
1 +249 - Amendment Avalanche
Content
... ... @@ -1,17 +1,35 @@
1 -In our previous release, we released functionality to increase the stability of Windows runtimes. This time, we followed that up by adding additional safety measures on the runtime level. Additionally, we have several pieces now available to prepare for pending changes to our event streaming offering. Furthermore, we introduced several minor improvements to the platform.
1 +This release is characterized by many updates to our platform, both from a user perspective and from a technical perspective regarding our backend services. This sets us up to allow all users to prepare their Mendix systems for a migration to DSH (if applicable). Furthermore, it enables us to assist our users more effectively as they develop within the platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.246 - Preparation Paradise.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.249 - Amendment Avalanche.WebHome||target="blank"]].
4 4  
5 -====Minor Changes====
5 +==== New features ====
6 6  
7 -* Deploy - General: Updated the Java arguments applied to Windows containers to align with the container limits, thereby improving the stability of these containers.
8 -* General - Runtime: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V333.WebHome||target="blank"]] is available.
9 -** This adds support for consuming Kafka topics based on a ‘topics’ pattern instead of a fixed list of topic names.
10 -** This updates our Java runtime version from Java 17.0.13 to Java 17.0.15. This is primarily a security update.
7 +* General - License Tracker: You can now see licensed flows on the model level alongside the company level after we have registered the correct configuration. (#859)
8 +* Event Streaming - DSH Connection: The eMagizConnector base image has been updated as preparation to support event streaming integrations on DSH. This allows all users to prepare their Mendix systems to connect to DSH.
9 +** Note that all users running the new eMagiz Connector will receive this update with their next release. **If you already have a running eMagiz Connector, you need to restart the application to retrieve the latest information after the new release is prepared for you. **
11 11  
12 -====Bug fixes====
11 +==== Minor changes ====
13 13  
14 -* Create - Flow designer: We have fixed a bug where you could not add a new entry flow to a ‘SOAP Entry Connector’ enabled system.
15 -* Manage - Error Messages: The non-working download button for payload content files now displays a more descriptive error message text. (#886)
16 -* Manage - Explore (Queue Browser): Updated styling for the action buttons related to the debug functionality. (#1653)
17 -* Q&A Forum - General: You will no longer receive an email notification about your comments on posts in the Q&A forum. (#1462)
13 +* Event Streaming - User Management: When adding new event streaming integrations that link to an **existing** event streaming processor, you **must** transfer them to the Create phase via the adding integrations tooling in the Create. This will trigger eMagiz to update the Deploy user management accordingly.
14 +** This functionality applies to both the old and new event broker.
15 +* Design - Message Definition: The overview of the attributes shown in the entity overview of the data model (i.e., CDM) and the system message now also shows the description of the attribute. (#1671)
16 +* Create - Flow Designer: The circuit breaker option under the request handler advice chain can now also be filled with a property placeholder. (#1619)
17 +* Create - Flow Designer: The overwrite option of the headers of a standard header enricher is now placed in the 'Basic' tab instead of the 'Advanced' tab. (#1666)
18 +* Create - Flow Testing: When creating a new test message and selecting the option "from existing file", the default option is now "Create" instead of "Capture". (#1659)
19 +* Create - Flow Testing: Each trace entry in the "Traces" overview now contains a timestamp. (#1661)
20 +* Capture - Overview: Deleting systems/integrations/tenants in Capture now shows a progress bar. (#1665)
21 +* Deploy - Unused Properties: For the unused properties functionality on the Create Phase Release, it is adjusted so that only the properties that are not used in any of your releases across environments are shown. They can be deleted without impacting any of the existing releases. (#1244)
22 +** Context is added to guide users through the following actions.
23 +** Performance has improved significantly. As a result, the process takes less time than before.
24 +* Deploy - Releases: Promoting a release to the next environment does not trigger the auto-delete behaviour of releases anymore. (#1318)
25 +* Deploy - Containers: Only the active containers are updated when a user adds or removes something from a release. Consequently, when a new integration is added, inactive containers will not contain the new integration. They can be reactivated if desired to enable automatic updates again. (#986)
26 +
27 +==== Bug fixes ====
28 +
29 +* Create - Add Integrations: We fixed several issues regarding untransferring and transferring integrations. Among other things, we addressed the following specific cases.
30 +** Re-transferring integrations to Deploy.
31 +** Untransfering the last integration of a system.
32 +* Create - Flow Designer: The user can now completely read the alerts in the flow designer with a hover text. (#1168)
33 +* Create - Flow Designer: The "Allow empty array" checkbox in Create can now be used without it throwing an error. (#1640)
34 +* Create - Flow Designer: We ensured that the order in which you create flow versions for flows belonging to an "exit/entry" construction can be random. As a result, this will prevent users from ending up with only a part of the flows belonging to this construction in Deploy, while all flow versions are indeed created in Create.
35 +* Manage - Alerting - Triggers (Error): Error alerts with ‘not equal to’ and ‘does not contain’ evaluations on ‘exception class’ and/or ‘exception message’ will now only trigger if both the first and last exception don’t equal/contain the value. (#1576)