Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 34.1
edited by Erik Bakker
on 2022/12/06 16:05
on 2022/12/06 16:05
Change comment:
There is no comment for this version
To version 103.1
edited by Erik Bakker
on 2023/08/29 11:07
on 2023/08/29 11:07
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 189-PrivateEye1 +204 - Found It - Content
-
... ... @@ -1,24 +1,18 @@ 1 - Thereleasebringsaprivatestoretoourcommunityand makesthe latestruntimeimage availableforourcustomers running on the 3rd generation architecture.Furthermore, we introduce severalimprovements toour3rd generationruntimeandits interactionwiththeportal.1 +In the last sprint cycle, we focused on the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.189 - Private Eye.WebHome||target="blank"]]. 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.V110.WebHome||target="blank"]]. 3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.204 - Found It.WebHome||target="blank"]]. 6 6 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. 7 +* Deploy - Containers: Removed generation of unnecessary properties from the 3rd generation event streaming containers. 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. 11 +* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970) 12 +* Manage - Error messages: Error messages with a lengthy message history will also be displayed. This change only impacts containers that work on the 3rd generation architecture. 13 +* Deploy - Releases: When a user activates a release containing nested properties and the property is not created, we show it now as missing. We add the property placeholder after the user tries to activate the release. 14 +* Manage - Error messages: Error messages with a stack trace larger than 32kb will also be displayed. This change only impacts containers that work on the 3rd generation architecture. 15 + 16 +=====Infra and image changes===== 17 + 18 +* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.