Skip to Content

Changes for page 254 - Other One

Last modified by Erik Bakker on 2025/10/09 11:13
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 274.3
edited by Maria
on 2025/09/10 13:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -198 - Great Migration
1 +252 - FrostLine
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.maria
Content
... ... @@ -1,24 +1,15 @@
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 features numerous updates to our platform, with a user-centric focus. This release, we once again embarked on our traditional Hackathon journey, focused on making the lives of our day-to-day platform users easier.
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>>Main.Release Information.Release Blogs.250 - Fix Fest.WebHome||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +==== New features ====
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 +* We have introduced the ability to move flows to another container, and be able to move their respective properties along side with them. *
16 16  
17 -====Bug fixes====
9 +==== Minor changes ====
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.
11 +* Lorem ipsum
21 21  
22 -====Remarks====
13 +==== Bug fixes ====
23 23  
24 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
15 +* Users belonging to Mendix systems will no longer be shown Deploy > User management. All required information for these Mendix systems can be found in Deploy > Mendix connectors.