Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 110.1
edited by Carlijn Kokkeler
on 2024/05/22 13:39
Change comment: There is no comment for this version
To version 10.1
edited by Erik Bakker
on 2022/10/14 13:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -204 - Found It
1 +185 - Get Ready
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,21 +1,25 @@
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 +Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
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.185 - Get ready.WebHome||target="blank"]].
4 4  
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.
5 +=====New features=====
6 +* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
11 11  
12 -====Bug fixes====
8 +=====Minor changes=====
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.
10 +* Design System. Changed the look and feel across the portal altogether. Changes can be seen in:
11 + ** Datagids, where there is now on hover action for example.
12 + ** Pop ups
13 + ** Context menus, also have on hover action
14 + ** Styling of scrollbars
15 + ** Warning, info and error context labels.
16 +* Message Redelivery - admin logs improved to better analyze issues when they occur
17 +* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality
18 +* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
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.
20 +====Bug fixes====
21 +* Deploy - Deployment plan. Performance of page to deploy a release increased significantly
22 +* Store - Import resources was incorrectly done in specific cases, which is now fixed
23 +* Store - Target namespace will be imported when importing an XML Message Definition
24 +* Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model.
25 +* Store - Importing items from the store sometimes resulted in invalid JMS connection factories.