Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 787.1
edited by Carlijn Kokkeler
on 2024/11/18 12:07
Change comment: There is no comment for this version
To version 770.1
edited by Carlijn Kokkeler
on 2024/11/04 11:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -234 - Alert Adventures
1 +233 - TBD
Content
... ... @@ -3,39 +3,38 @@
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!**
7 7  
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 -
12 -{{info}}
13 -Please take into consideration the following migration actions:
14 -* 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.
15 -* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
16 -** The 'Description' field has been replaced by the new 'Instructions' field (note: the 'Description' field no longer exists).
17 -** The values of the old description field will be transferred into the instructions field
18 -* 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.
19 -** This field will be automatically populated with a default name (e.g., "Error Trigger 1").
20 -** **Users are advised to review and update these names to appropriately reflect each trigger's purpose**.
21 -
22 -{{/info}}
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.
23 23  
24 -{{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}}
15 +[[image:Main.Images.Release Blog.WebHome@release-233-balance-failover.png]]
16 +
25 25  
26 -{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/warning}}
18 +[[image:Main.Images.Release Blog.WebHome@release-233-failover-system.png]]
27 27  
20 +//__SMB session factory__//
21 +We have added two additional configuration options to the SMB session factory support object.
22 +* Connect as guest: We have added the option to toggle whether the session factory should attempt to connect as a guest if the login attempt with the provided username and password is rejected.
23 +* Force SMB version 2: We have added the option to enforce the usage of SMB version 2. This effectively disables backwards-compatible version negotiation.
28 28  
29 -
30 -
31 31  == **Bug Fixes** ==
26 +//__Support object alert__//
27 +If a component misses a support object, an alert is now shown in the Flow Designer, displaying which support object is missing.
32 32  
29 +[[image:Main.Images.Release Blog.WebHome@release-233-support-object-alert.png]]
33 33  
31 +
32 +
34 34  == **Fancy Forum Answers** ==
35 35  
36 36  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:
37 37  
38 -* [[JSON-TO-JSON java.lang.NumberFormatException in string field>>https://my.emagiz.com/p/question/172825635703991104||target="blank"]]
37 +* [[H2 Database on ESF Across Multiple Runtimes>>https://my.emagiz.com/p/question/172825635703991017||target="blank"]]
39 39  
40 40  == **Key Takeaways** ==
41 41  
... ... @@ -45,7 +45,7 @@
45 45  * If you have feedback or ideas for us, talk to the Platypus
46 46  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
47 47  * Clear your browser cache (Ctrl + Shift + Del)
48 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.233 - Policy Polish.WebHome||target="blank"]]
47 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.232 - Bug Busters.WebHome||target="blank"]]
49 49  * Start thinking about how the license tracker can aid your development
50 50  * Start thinking about major, minor, and patch
51 51  * Keep making great integrations