Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 326.1
edited by Carlijn Kokkeler
on 2024/09/27 09:36
Change comment: There is no comment for this version
To version 328.1
edited by Carlijn Kokkeler
on 2024/10/07 15:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -230 - Petite Peaks
1 +231 - Microscopic Madness
Content
... ... @@ -1,13 +1,18 @@
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 +During our recent sprint cycle, we have improved the search options for flow testing logs and monitoring logs. Next to this, we fixed the unused properties overview and improved the deletion functionality of router containers.
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.231 - Microscopic Madness||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 [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]].
7 7  
8 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 +* Create - Flow Testing: Search options for flow testing logs have been improved.
8 +** Improved search options for flow test logs. You can now search for 'logger' and 'message', search for 'timestamp from' and 'to' have been removed.
9 +** Unified the UI with Manage phase logging of G3) for a more streamlined experience
10 +* Manage - Monitoring: Search options for monitoring logs have been improved.
11 +** Unified the UI with flow testing log interface, showing the message and stack trace (if available) in 2 different tabs
12 +** Added the 'logger' column that shows the last part of the logger name.
13 +** Added a search field for ‘logger’
10 10  
15 +
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.
17 +* Deploy - Architecture: Router containers that were deleted from the Deploy Architecture, are now cleaned up completely from the environment.
18 +* Deploy - Releases: We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. (#1442)