Changes for page 241.1 - Wild West
Last modified by Erik Bakker on 2025/04/04 08:35
From version 239.1
edited by Erik Bakker
on 2025/04/04 08:35
on 2025/04/04 08:35
Change comment:
There is no comment for this version
To version 85.1
edited by Erik Bakker
on 2023/06/05 16:03
on 2023/06/05 16:03
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 - 2411-WildWest1 +199 - Home Improvements - Content
-
... ... @@ -1,10 +1,20 @@ 1 -In th isadditionalunplannedrelease,we havecorrectedtwo problemswithinthe platformthatwerecausingproblems for ourcustomers.On top of that, weupdated our infrastructureinlight ofarecentlydiscoveredvulnerabilityinoneoftheunderlying platforms weuse.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.199 - Home Improvements.WebHome||target= "blank"]]. 4 + 5 +=====Minor changes===== 6 + 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. 12 + 3 3 ====Bug fixes==== 4 4 5 -* Overall-Feedback:Sinceour previousrelease, it has beenimpossibleto issue feedbackonourplatform duetoatightened security policy.This problem has been fixed with thisrelease.6 -* Deploy-Releases: Due toournewlyintroduced feature regardingcomparingproperties, we lostperformancewhenactivatingreleases inmodelscontainingMendixsystems. Asaresult,usersexperienceddelaysin waiting foreMagizto finishthis process.This problemhas beenfixedwiththis release.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. 7 7 8 8 ====Remarks==== 9 9 10 -* In light ofavulnerabilitydiscoveredinoneofthe underlyingplatformswe use, we tookproactiveactionstosafeguardourinfrastructureagainstthiseven better.20 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.