Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 108.1
edited by Carlijn Kokkeler
on 2023/09/18 13:12
Change comment: There is no comment for this version
To version 89.1
edited by Erik Bakker
on 2023/06/09 10:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -204 - Found It
1 +199 - Home Improvements
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,21 +1,19 @@
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.
1 +In the last sprint cycle, we 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.204 - Found It.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]].
4 4  
5 5  =====Minor changes=====
6 -* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change and can be multiply selected.
7 -* Deploy-Architecture: The container calculations are improved. For event streaming containers these show the amount of topic proccessers deployed. For gateway containers these represent the amount of operations deployed on a container. For JMS containers these represent the amount of message queues deployed. The other types of containers display the amount of intergrations deployed.
8 -* Create - 3rd Generation runtime migration: Your containers will be validated for 3rd Generation runtimes first before you approve the migration.
9 -* Deploy-Architecture: Users with edit rights in deploy can edit certificates.
10 -* Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
11 11  
7 +* Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store.
8 +* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899)
9 +* 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 three months before event streaming users' access certificates expire.
10 +* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan.
11 +* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960)
12 +* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.
13 +* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.
14 +
12 12  ====Bug fixes====
13 13  
14 -* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970)
15 -* 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.
16 -* 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.
17 -* 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.
17 +* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864)
18 +* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937)
18 18  
19 -=====Infra and image changes=====
20 -
21 -* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.