Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 82.1
edited by Erik Bakker
on 2023/05/22 15:19
Change comment: There is no comment for this version
To version 28.1
edited by Erik Bakker
on 2022/11/24 11:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -198 - Great Migration
1 +188 - Close Encounters
Content
... ... @@ -1,27 +1,21 @@
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 +The release brings several improvements to our 3rd generation runtime and its interaction with the portal. On top of that, we have several feedback items and bug fixes.
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.188 - Close Encounters.WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -
7 -
8 8  =====Minor changes=====
9 9  
10 -* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
11 -* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
12 -* 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.
13 -* 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.
14 -* 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.
15 -* Deploy - Architecture: You can apply your changes to environment without having an active release.
16 -* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
17 -(control tower, so Gen3 only)
18 -* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
7 +* General: Code mapping is now available for models migrating to the 3rd generation runtime.
8 +* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785)
9 +* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you.
10 +* Deploy - Deployment plan: When a runtime is being deployed, which is constantly crashing and thereby causing problems, the restart of the runtime is limited to just five times. (#720)
11 +** After five times, the runtime will remain in the stopped state.
19 19  
20 20  ====Bug fixes====
14 +* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717)
15 +* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
16 +* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
17 +* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
18 +* Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture.
21 21  
22 -* 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.
23 -* 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.
24 -
25 25  ====Remarks====
26 -
27 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
21 +* Mendix Runtime has been upgraded to Mendix 9.19.0.