Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 325.1
edited by Carlijn Kokkeler
on 2024/09/25 16:56
Change comment: There is no comment for this version
To version 86.1
edited by Erik Bakker
on 2023/06/05 16:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -230 - Petite Peaks
1 +199 - Home Improvements
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,13 +1,21 @@
1 -During our recent sprint cycle, we improved the functionality of adding an integration to an existing API in Design, ensured that queues with illegal characters will not generate errors anymore, and we fixed an issue where the execution of a deployment step would be blocked. Read all about it below!
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.230 - Petite Peaks||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 -====New features====
6 -* All - Failover: We have introduced a new failover feature, allowing you to enable failover on messaging flows with minimal setup required. Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more on our documentation page (LINK).
5 +=====Minor changes=====
7 7  
8 -====Minor changes====
9 -* Design - Solution Design: When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
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.
10 10  
11 11  ====Bug fixes====
12 -* Manage - Explore: Queues with illegal characters will not generate errors anymore. As a result they can be explored and if needed removed from your model.
13 -* Deploy - Deployment: We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
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.