Skip to Content

Changes for page 254 - Other One

Last modified by Erik Bakker on 2025/10/09 11:13
From version 270.1
edited by Erik Bakker
on 2025/07/14 07:44
Change comment: There is no comment for this version
To version 57.1
edited by Erik Bakker
on 2023/03/14 08:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -249 - Amendment Avalanche
1 +194 - Giant Leap
Content
... ... @@ -1,35 +1,24 @@
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.
1 +The release introduces various improvements on our 3rd generation runtime architecture and various other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.249 - Amendment Avalanche.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.194 - Giant Leap.WebHome||target= "blank"]].
4 4  
5 -==== New features ====
5 +=====New features=====
6 6  
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. **
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.
10 10  
11 -==== Minor changes ====
11 +=====Minor changes=====
12 12  
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)
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.
26 26  
27 -==== Bug fixes ====
18 +====Bug fixes====
28 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)
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)