Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55

From version 25.1
edited by Erik Bakker
on 2022/11/21 13:22
Change comment: There is no comment for this version
To version 257.1
edited by Carlijn Kokkeler
on 2024/06/03 16:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +222 - Flee Frustration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,21 +1,17 @@
1 -The release brings several improvements to our 3rd generation runtime and the interaction with it. On top of that, we have several feedback items and bug fixes.
1 +In the last sprint cycle, we done several improvements for the Design and Deploy phases. Moreover, we have improved the Event Catalog overview for Catalog users. Our bug fixes concern the import of xsds, the deletion behaviour of containerse, and the generation of scope properties.
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.222 - Flee Frustration||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +====New features====
6 +* Design - Architecture: If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
7 +* Create - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
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 get better clarity on what it can be used for.
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 5 times.
11 -** After 5 times the runtime will remain in the stopped state.
12 -* Deploy - Releases: The activate release functionality gained a performance improvement for models that use the 3rd generation runtime.
13 -
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.
10 +* Design - Architecture: The number on the JMS container correctly displays the amount of queues present in Design. (#1284)
11 +* Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053)
12 +* Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282)
13 +* Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293)
14 +* Deploy - Releases: Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. (#1293)
19 19  
20 -====Remarks====
21 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
16 +
17 +