Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 30.1
edited by Erik Bakker
on 2022/12/06 16:02
Change comment: There is no comment for this version
To version 85.1
edited by Erik Bakker
on 2023/06/05 16:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +199 - Home Improvements
Content
... ... @@ -1,24 +1,20 @@
1 -The release brings a private store to our community and makes the latest runtime image available for our customers running on the 3rd generation architecture. Furthermore, we introduce several improvements to our 3rd generation runtime and its interaction with the portal.
1 +In the last sprint cycle we have focused on improving various aspects of the portal functionality. Among others we focused on the next-generation architecture, the store, security and certificate management.
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.V1~.1~.0.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.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 - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately 3 months before the expiration dates of event streaming users' access certificates.
8 +* Deploy - Release: After successful machine deployments, unused runtime images will be automatically removed. This can be disabled by changing the machine step in your deployment plan.
9 +* Manage - Monitoring: HTTP statistics page now displays all of the resources.
10 +* Manage - Alerting: congestion control wil be enabled by default with 10 alerts per 10 minutes and user cannot see or change it.
11 +* General - Infra: Changed the library used for storing metadata in the eMagiz Control Tower.
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  
15 +* Create - Store: Spring Reserved words that contain * are not incorrectly replaced with the prefix of the flow.
16 +* Manage - Monitoring: When an application failed to start, not all log messages were visible in the manage phase.
17 +
23 23  ====Remarks====
24 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
19 +
20 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.