Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 788.1
edited by Carlijn Kokkeler
on 2024/11/18 12:09
Change comment: There is no comment for this version
To version 725.1
edited by Carlijn Kokkeler
on 2024/09/27 09:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -234 - Alert Adventures
1 +230 - Petite Peaks
Content
... ... @@ -3,41 +3,33 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, our new error alerting will be available! Please find out more about it here (LINK). Apart from this, .
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** ==
9 -//__Error alerting__//
10 -Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, following our queue alerting design that has been [[released>>doc:Main.Release Information.Release Blogs.226 - Alerting Alchemy.WebHome||target="blank"]] a couple of months ago. The new error alerting feature allows you to trigger an alert on all incoming errors, or choose to trigger when specific filters on the error’s headers, message or class have been met. Furthermore, you can select the specific runtime the error originated from as one of the filters as well.
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.
11 11  
12 -{{info}}Please take into consideration the following migration actions:
13 -* All existing error message alert triggers from the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture models will be automatically migrated to the new alerting feature.
14 -* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
15 -** The 'Description' field has been replaced by the new 'Instructions' field (note: the 'Description' field no longer exists).
16 -** The values of the old description field will be transferred into the instructions field
17 -* Additionally, a new field, 'Name', has been introduced for identification purposes. The 'Name' field will be included in email notifications when a trigger is activated.
18 -** This field will be automatically populated with a default name (e.g., "Error Trigger 1").
19 -** **Users are advised to review and update these names to appropriately reflect each trigger's purpose**.
20 -* If an error message alert trigger has the following specific configuration, its trigger conditions will be migrated to trigger alerts for all incoming error messages:
21 -** "Check header" is disabled.
22 -** "Check error message" is enabled.
23 -** The "Error message contains" field includes only a single character.
24 -* The new feature introduces duplicate detection when saving an individual error trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate error alerts.{{/info}}
25 -
26 -{{warning}}To keep a better overview, we recommend you to remove your old dynamic triggers after the new error triggers are activated, these have already been disabled by our migration process. The same applies for your queue-related triggers. These triggers can be found under the ‘Other’ tab on the alert triggers page.{{/warning}}
14 +[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]]
27 27  
28 -{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/warning}}
29 -
30 -
31 -
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 [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]].
32 32  
33 33  == **Bug Fixes** ==
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.
34 34  
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.
35 35  
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  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:
39 39  
40 -* [[JSON-TO-JSON java.lang.NumberFormatException in string field>>https://my.emagiz.com/p/question/172825635703991104||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"]]
41 41  
42 42  == **Key Takeaways** ==
43 43  
... ... @@ -47,7 +47,7 @@
47 47  * If you have feedback or ideas for us, talk to the Platypus
48 48  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
49 49  * Clear your browser cache (Ctrl + Shift + Del)
50 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.233 - Policy Polish.WebHome||target="blank"]]
42 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.230 - Petite Peaks.WebHome||target="blank"]]
51 51  * Start thinking about how the license tracker can aid your development
52 52  * Start thinking about major, minor, and patch
53 53  * Keep making great integrations