Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 201.1
edited by Carlijn Kokkeler
on 2024/02/26 10:47
Change comment: There is no comment for this version
To version 239.1
edited by Erik Bakker
on 2025/04/04 08:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -215 - Tiny Tales
1 +2411 - Wild West
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,15 +1,10 @@
1 -In the last sprint cycle, we focused on improving the event streaming graph. Moreover, we have done some bug fixes. First of all, the validation for queue names with respect to spaces has been improved. Moreover, it is now possible to remove an onramp that was previously linked to an all entry. Lastly, it is now possible to login to eMagiz by pressing enter when having the username field selected.
1 +In this additional unplanned release, we have corrected two problems within the platform that were causing problems for our customers. On top of that, we updated our infrastructure in light of a recently discovered vulnerability in one of the underlying platforms we use.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.215 - Tiny Tales||target="blank"]].
4 -
5 -=====Minor changes=====
6 -
7 -* Manage - Monitoring: The event streaming graph has been improved to better reflect the state of your topics. (#951)
8 -
9 9  ====Bug fixes====
10 10  
11 -* Login: In the login screen, users now have the ability to press enter to log in when having the username field selected.
12 -* Create - Flow Designer: The validation regarding undesired spaces for components that use a queue name has been improved. (#1012)
13 -* Create - Flow Designer: An issue has been fixed where it was not possible to remove an onramp that was previously linked to a combined entry. (#1021)
5 +* Overall - Feedback: Since our previous release, it has been impossible to issue feedback on our platform due to a tightened security policy. This problem has been fixed with this release.
6 +* Deploy - Releases: Due to our newly introduced feature regarding comparing properties, we lost performance when activating releases in models containing Mendix systems. As a result, users experienced delays in waiting for eMagiz to finish this process. This problem has been fixed with this release.
14 14  
8 +====Remarks====
15 15  
10 +* In light of a vulnerability discovered in one of the underlying platforms we use, we took proactive actions to safeguard our infrastructure against this even better.