Skip to Content

Changes for page 273 - Squash Squash

Last modified by Erik Bakker on 2026/07/27 11:44
From version 83.1
edited by Erik Bakker
on 2023/05/22 15:20
Change comment: There is no comment for this version
To version 347.1
edited by Erik Bakker
on 2026/07/27 08:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -198 - Great Migration
1 +273 - Squash Squash
Content
... ... @@ -1,24 +1,11 @@
1 -Another couple of weeks have passed, so it is time for a new release. We have focused in this period on improving the migration process towards the next-generation architecture as well as how the user experience and interaction with the next-generation architecture works.
1 +This release includes various smaller improvements throughout the various phases of the platform. On top of that, we have updated certain parts of our Mendix project to their respective latest version.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.273 - Squash Squash.WebHome||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +==== Minor Changes ====
6 6  
7 -* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
8 -* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
9 -* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
10 -* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
11 -* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
12 -* Deploy - Architecture: You can apply your changes to environment without having an active release.
13 -* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
14 -(control tower, so Gen3 only)
15 -* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
7 +* Deploy - History (Releases): Introduced various changes to this overview to make the information we show here more specific. The main changes are that we show a full timestamp in the “When” column instead of the date itself, and the “eye” icon is only present when the registered audit log exceeds a predefined length. (#1779)
16 16  
17 -====Bug fixes====
9 +==== Remarks ====
18 18  
19 -* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models.
20 -* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
21 -
22 -====Remarks====
23 -
24 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
11 +* Updated various UI related modules within our Mendix project to their respective latest version.