Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 86.1
edited by Erik Bakker
on 2023/06/05 16:04
Change comment: There is no comment for this version
To version 247.1
edited by Carlijn Kokkeler
on 2024/05/21 12:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +221 - Swift Shift
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,21 +1,18 @@
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.
1 +In the last sprint cycle, we have worked on .
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.221 - Swift Shift||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +===== New features =====
6 6  
7 -* * Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
8 -* 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.
9 -* 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.
10 -* Manage - Monitoring: HTTP statistics page now displays all of the resources.
11 -* Manage - Alerting: congestion control wil be enabled by default with 10 alerts per 10 minutes and user cannot see or change it.
12 -* General - Infra: Changed the library used for storing metadata in the eMagiz Control Tower.
7 +* Q & A: Search results are now persisted when pressing the back button after opening a question in the community Q & A. (#1324)
8 +* Catalog: We have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
9 +* Design - CDM/System message: A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. (#151)
10 +* Design - System message: Moving an attribute in the datamodel is now directly shown in the tree structure as well. (#151)
11 +* Design - CDM/API Data model/ES data model and system message: The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. (#151)
12 +* Deploy - Deploy release: When executing a start/stop action on a group, the description of the step now contains the name of the group.
13 +* Deploy - Architecture: When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
13 13  
14 -====Bug fixes====
15 -
16 -* Create - Store: Spring Reserved words that contain * are not incorrectly replaced with the prefix of the flow.
17 -* Manage - Monitoring: When an application failed to start, not all log messages were visible in the manage phase.
18 -
19 -====Remarks====
20 -
21 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
15 +===== Bug fixes =====
16 +* Design - System messages: When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. (#140)
17 +* Deploy - Containers: The delete behaviour of containers in the container overview has been improved. (#1053)
18 +* Deploy - API Gateway: We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.