Changes for page 189 - Private Eye
Last modified by Carlijn Kokkeler on 2024/05/22 13:43
From version 24.1
edited by Erik Bakker
on 2022/11/21 13:22
on 2022/11/21 13:22
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,4 +1,4 @@ 1 -The release brings several improvements to our 3rd generation runtime and t heinteraction withit. On top of that, we have several feedback items and bug fixes.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. 2 2 3 3 Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.WebHome||target="blank"]]. 4 4 ... ... @@ -5,13 +5,15 @@ 5 5 =====Minor changes===== 6 6 7 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 getbetter clarityonwhatit canbeusedfor.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 just5 times. After 5 timesthe runtimewill remain in thestopped state.11 -* Deploy- Releases:The activatereleasefunctionalitygaineda performanceimprovementfor modelsthat use the3rdgeneration 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 13 ====Bug fixes==== 14 -* Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718) 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) 15 15 * Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703) 16 16 * Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore. 17 17 * 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.