Changes for page 217 - Template Tango
Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 35.1
edited by Erik Bakker
on 2022/12/06 16:11
on 2022/12/06 16:11
Change comment:
There is no comment for this version
To version 83.1
edited by Erik Bakker
on 2023/05/22 15:20
on 2023/05/22 15:20
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 89 -PrivateEye1 +198 - Great Migration - Content
-
... ... @@ -1,29 +1,24 @@ 1 - Theeleasebrings a private storetoour communityandmakesthe latest runtimeimage available for ourcustomers runningon the3rd generation architecture.Furthermore,weintroduce severalimprovementstoour3rd generationruntime and its interaction with theportal.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. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.1 89 -PrivateEye.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]]. 4 4 5 -=====New features===== 6 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]]. 7 - 8 -=====Major changes===== 9 - 10 -* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your jms-server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime. 11 - 12 12 =====Minor changes===== 13 13 14 -* Create - Event Streaming: Event streaming is now available for models migrating to the 3rd generation runtime. 15 -* Create - Transformation: source filter on attribute with empty field is more readable in read-only mode. (#732) 16 -* Create - Migration: Improved compatibility checks related to the 3rd generation runtime migration. 17 -* Deploy - Check properties: Informative error messages when saving or creating a property. (#576) 18 -* Deploy - Deployment plan: We improved the deployment plan to avoid crashing the server when executing a deployment plan. 19 -* Deploy - Architecture: Added reset feature for 3rd generation runtimes. 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. 20 20 21 21 ====Bug fixes==== 22 -* Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows. 23 -* Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances. 24 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. 25 -* Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798) 26 -* Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment. 27 27 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 + 28 28 ====Remarks==== 29 -* Mendix Runtime has been upgraded to Mendix 9.19.0. 23 + 24 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.