Changes for page 237 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 28.1
edited by Erik Bakker
on 2022/11/24 11:26
on 2022/11/24 11:26
Change comment:
There is no comment for this version
To version 184.1
edited by Carlijn Kokkeler
on 2024/01/15 14:46
on 2024/01/15 14:46
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 88-CloseEncounters1 +212 - Failover Fiesta - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,21 +1,27 @@ 1 - Thereleasebringsseveral improvements to our 3rd generationruntimeand its interaction with the portal. On top of that, wehaveseveral feedbackitems andbug fixes.1 +In the last sprint cycle, we focused on .... 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.1 88-CloseEncounters.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Feedback Fiesta||target="blank"]]. 4 4 5 +=====New features===== 6 + 7 +* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines. 8 +* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 9 + 5 5 =====Minor changes===== 6 6 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. 12 +* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 13 +* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment. 14 +* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high. 15 +* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917) 16 +* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards. 17 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start. 12 12 13 13 ====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. 19 19 20 -====Remarks==== 21 -* Mendix Runtime has been upgraded to Mendix 9.19.0. 21 +* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. 22 +* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks. 23 +* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 24 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container. 25 +* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108) 26 + 27 +