Changes for page 237 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 33.1
edited by Erik Bakker
on 2022/12/06 16:03
on 2022/12/06 16:03
Change comment:
There is no comment for this version
To version 175.1
edited by Carlijn Kokkeler
on 2023/12/21 16:27
on 2023/12/21 16:27
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 89-Private Eye1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,24 +1,28 @@ 1 - Thereleasebringsaprivate storeoourcommunityandmakes thelatestruntime imageavailableforourcustomersrunningon the3rdgenerationarchitecture.Furthermore,we introduceseveral improvementsto our3rdgenerationuntime and itsinteractionwiththe portal.1 +In the last sprint cycle, we focused on improving several aspects related overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.189 - Private Eye.WebHome||target="blank"]]. 3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]]. 4 + 4 4 =====New features===== 5 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Release blog>>Main.Release Information.Runtime Images.V1~.~1~.~0.WebHome||target="blank"]]. 6 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 in an overview. 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 + 7 7 =====Minor changes===== 8 8 9 -* General: Code mapping is now available for models migrating to the 3rd generation runtime. 10 -* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785) 11 -* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you. 12 -* Deploy - Deployment plan: For 3rd generation runtimes we have changed the restart behavior in case of startup problems. This means that 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) 13 -** 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: Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'. 15 +* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. 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. 14 14 15 15 ====Bug fixes==== 16 -* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717) 17 -* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718) 18 -* Deploy - Deployment plan: Before when you tried to deploy a Release via the Deploy functionality the widget could crash randomly. With this fix we ensured the widget will always load correctly. (#362) 19 -* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703) 20 -* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore. 21 -* 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. 22 22 23 -====Remarks==== 24 -* 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 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container. 23 +* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. 24 +* Deploy - Cloud templates: An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks. 25 +* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 26 + 27 + 28 +