Skip to Content

Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 26.1
edited by Erik Bakker
on 2022/11/21 13:25
Change comment: There is no comment for this version
To version 174.1
edited by Carlijn Kokkeler
on 2023/12/21 16:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,21 +1,31 @@
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.
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.188 - Close Encounters.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||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 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 +
10 +
11 +
12 +
13 +
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.
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.
11 -** After five times, the runtime will remain in the stopped state.
12 -* Deploy - Releases: The activate release functionality performance for models that use the 3rd generation runtime is improved.
16 +* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
17 +* 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'.
18 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
13 13  
20 +
21 +
22 +
23 +
14 14  ====Bug fixes====
15 -* 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.
26 +* 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.
27 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container.
28 +
29 +
30 +
31 +