Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 724.1
edited by Carlijn Kokkeler
on 2024/09/25 16:55
Change comment: There is no comment for this version
To version 722.1
edited by Carlijn Kokkeler
on 2024/09/25 13:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,7 +5,7 @@
5 5  
6 6  **Hi there, eMagiz developers!** In this release, we have some small improvements and bug fixes. First of all, the pop-up when adding an integration to an existing API in Design has been improved. Secondly, queues with illegal characters will not cause errors anymore. Thirdly, an issue has been fixed where a deployment step would get blocked. Please find out all below!
7 7  
8 -{{info}}Please note that during this deployment, Kafka metrics will be unavailable and lost for the duration of the deployment. After the deployment is complete, Kafka metrics will resume and be reflected in the monitoring graphs, but no metrics will be present corresponding to the deployment period.{{/info}}
8 +{{info}}Please note that during this deployment, Kafka metrics will be unavailable and lost for the duration of the deployment. After the deployment is complete, Kafka metrics will resume and be reflected in the monitoring graphs, but no metrics will be present corresponding to the deployment period.{{\info}}
9 9  
10 10  == **Feedback Items** ==
11 11  //__Add integration__//
... ... @@ -13,9 +13,7 @@
13 13  
14 14  [[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]]
15 15  
16 -//__Failover__//
17 -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).
18 -
16 +
19 19  == **Bug Fixes** ==
20 20  //__Queues with illegal characters__//
21 21  Existing queues with illegal characters will not generate errors anymore. They can now be searched, deleted, explored, wiretapped, etc. in Manage -> Explore.