Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 818.1
edited by Carlijn Kokkeler
on 2024/12/02 10:08
Change comment: There is no comment for this version
To version 721.1
edited by Carlijn Kokkeler
on 2024/09/25 09:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -235 - TBD
1 +230 - Petite Peaks
Content
... ... @@ -3,22 +3,29 @@
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 this is our last release of the year. Our next release will be on the 16th of January!{{/info}}
9 -
10 10  == **Feedback Items** ==
11 -//__Log alerting__//
12 -We have added log message alert triggers to our new alerting stack for the current runtime architecture. This new feature allows you to trigger on all incoming log messages with an error log-level, or trigger for log messages with a specific log message and log level (info, warning or error) combination. Furthermore, you can specify the specific runtime the log message originated from as one of the filters as well.
9 +//__Add integration__//
10 +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 13  
12 +[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]]
13 +
14 +
14 14  == **Bug Fixes** ==
16 +//__Queues with illegal characters__//
17 +Existing queues with illegal characters will not generate errors anymore. They can now be searched, deleted, explored, wiretapped, etc. in Manage -> Explore.
15 15  
19 +//__Blocked deployment step__//
20 +We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
16 16  
17 17  == **Fancy Forum Answers** ==
18 18  
19 19  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:
20 20  
21 -* [[H2 database following a queue channel without message store>>https://my.emagiz.com/p/question/172825635704003822||target="blank"]]
26 +* [[Error being stamped on the wrong "last flow">>https://my.emagiz.com/p/question/172825635703952578||target="blank"]]
27 +* [[AMQP broker hostname for JMS-host instead of IP>>https://my.emagiz.com/p/question/172825635703965465||target="blank"]]
28 +* [[Calling a soap webservice that is secured with a client certificate>>https://my.emagiz.com/p/question/172825635703965402||target="blank"]]
22 22  
23 23  == **Key Takeaways** ==
24 24  
... ... @@ -28,7 +28,7 @@
28 28  * If you have feedback or ideas for us, talk to the Platypus
29 29  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
30 30  * Clear your browser cache (Ctrl + Shift + Del)
31 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.234 - Alert Adventures.WebHome||target="blank"]]
38 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.230 - Petite Peaks.WebHome||target="blank"]]
32 32  * Start thinking about how the license tracker can aid your development
33 33  * Start thinking about major, minor, and patch
34 34  * Keep making great integrations