Skip to Content

Changes for page 240 - Spring Cleaning

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -233 - TBD
1 +230 - Petite Peaks
Content
... ... @@ -3,31 +3,33 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
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}}
9 +
8 8  == **Feedback Items** ==
11 +//__Add integration__//
12 +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.
13 +
14 +[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]]
15 +
9 9  //__Failover__//
10 -Several improvements for our failover functionality have been done:
11 -* We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.
12 -* We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment. This action can be found in Deploy Architecture, when right clicking on the white canvas.
13 -* We have added a visualization of connector systems that are pending a failover enable or disable in Deploy Architecture. Besides that, you will also see this shown in the pending changes list when you apply your changes to the environment.
14 -
15 -[[image:Main.Images.Release Blog.WebHome@release-233-balance-failover.png]]
16 -[[image:Main.Images.Release Blog.WebHome@release-233-failover-system.png]]
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).
17 17  
18 18  == **Bug Fixes** ==
19 -//__Support object alert__//
20 -If a component misses a support object, an alert is now shown in the Flow Designer, displaying which support object is missing.
20 +//__Queues with illegal characters__//
21 +Existing queues with illegal characters will not generate errors anymore. They can now be searched, deleted, explored, wiretapped, etc. in Manage -> Explore.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-233-support-object-alert.png]]
23 +//__Blocked deployment step__//
24 +We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
23 23  
24 -
25 -
26 26  == **Fancy Forum Answers** ==
27 27  
28 28  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
29 29  
30 -* [[H2 Database on ESF Across Multiple Runtimes>>https://my.emagiz.com/p/question/172825635703991017||target="blank"]]
30 +* [[Error being stamped on the wrong "last flow">>https://my.emagiz.com/p/question/172825635703952578||target="blank"]]
31 +* [[AMQP broker hostname for JMS-host instead of IP>>https://my.emagiz.com/p/question/172825635703965465||target="blank"]]
32 +* [[Calling a soap webservice that is secured with a client certificate>>https://my.emagiz.com/p/question/172825635703965402||target="blank"]]
31 31  
32 32  == **Key Takeaways** ==
33 33  
... ... @@ -37,7 +37,7 @@
37 37  * If you have feedback or ideas for us, talk to the Platypus
38 38  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
39 39  * Clear your browser cache (Ctrl + Shift + Del)
40 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.232 - Bug Busters.WebHome||target="blank"]]
42 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.230 - Petite Peaks.WebHome||target="blank"]]
41 41  * Start thinking about how the license tracker can aid your development
42 42  * Start thinking about major, minor, and patch
43 43  * Keep making great integrations