Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 29.1
edited by Erik Bakker
on 2022/11/24 11:52
on 2022/11/24 11:52
Change comment:
There is no comment for this version
To version 255.1
edited by Carlijn Kokkeler
on 2024/06/03 13:33
on 2024/06/03 13:33
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 - 188-CloseEncounters1 +222 - Flee Frustration - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,22 +1,10 @@ 1 - Thereleasebringsseveral improvementstoour3rdgenerationruntimeanditsinteractionwith theportal. On top of that,we have severalfeedbackitems andbug 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-CloseEncounters.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 -==== =Minorchanges=====5 +====New features==== 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: 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) 11 -** After five times, the runtime will remain in the stopped state. 12 12 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 - 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) 17 -* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703) 18 -* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore. 19 -* 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. 20 20 21 -==== Remarks====22 -* MendixRuntime hasbeenupgraded toMendix9.19.0.9 +====Bug fixes==== 10 +* 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.