Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 33.1
edited by Erik Bakker
on 2022/12/06 16:03
on 2022/12/06 16:03
Change comment:
There is no comment for this version
To version 60.1
edited by Erik Bakker
on 2023/03/14 08:53
on 2023/03/14 08:53
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 -1 89 -PrivateEye1 +194 - Giant Leap - Content
-
... ... @@ -1,24 +1,33 @@ 1 -The release brings a private store toourcommunity and makesthe latest runtimeimageavailable forourcustomers running on the3rd generation architecture.Furthermore,we introduce severalimprovementstoour3rd generation runtime anditsinteractionwiththeportal.1 +The release introduces improvements to our 3rd generation runtime architecture and other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.189 - Private Eye.WebHome||target="blank"]]. 3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.194 - Giant Leap.WebHome||target= "blank"]]. 4 + 4 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.V1~.~1~.~0.WebHome||target="blank"]]. 6 6 7 +* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]]. 8 +* Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers, and waking up a cloud slot will start those containers. (#889) 9 + 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. 12 +* Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you use custom error handling on your event processors. 13 +* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807) 14 +* Deploy - User Management: Roles are sorted alphabetically. (#806) 15 +* Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup. Please use the ‘Upgrade’ feature to keep your cloud architecture up-to-date. 16 +* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and chart, and made minor visual improvements. 17 +* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833) 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 21 +* Generic: We fixed an issue in that you may see a screen with a broken styling when switching among phases. 22 +* Create - Flow Designer: Removed the option to create a new resource on the resource selection popup of a simple XSD schema support object. 23 +* Create - Flow designer: We fixed the flow generation of entry flows for API Key secured API Gateway operations. This problem was introduced in version 193 (2023-02-04). (#902) 24 +* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filenames (>100 characters). 25 +* Deploy - Releases: You need edit rights in the test environment of the deploy phase to execute the “Update flows to latest versions” action. 26 +* Manage - Dashboard: We update the view to visualize the split entries after you migrate combined entries. 27 +* Manage - Logging: When a container cannot be started due to an incorrect stylesheet, the error message will include what the error is and in which stylesheet it occurred (#825) 28 +* Manage - Logging: Reduced the occurrence of 'Failed to send to Elastic' log messages which trigger alerts. (#898) 29 +* Manage - Alerting: Editable column shows the correct value. 30 + 23 23 ====Remarks==== 24 -* Mendix Runtime has been upgraded to Mendix 9.19.0. 32 + 33 +* Create - Flow designer: After the deployment, the ‘Version Compare' and 'Version Restore’ features will be unavailable for a few hours because of data migration. You will get an error stating that the version is incompatible with the selected feature until the migration is finished.