Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 594.1
edited by CarlijnKokkeler
on 2024/07/16 12:01
Change comment: There is no comment for this version
To version 486.1
edited by CarlijnKokkeler
on 2024/04/23 15:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - TBD
1 +219 - Creation Carousel
Content
... ... @@ -3,40 +3,59 @@
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!** This release, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
7 7  
8 -
9 9  == **Feedback Items** ==
10 -//__Alerting notification settings__//
11 -The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
10 +//__eMagiz Mendix connector__//
11 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
14 14  
15 -//__Process containers__//
16 -If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
13 +//__Improved OpenAPI import__//
14 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
17 17  
18 -//__Design settings__//
19 -When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
16 +//__Flow test stack trace__//
17 +If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab.
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
19 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
22 22  
23 -//__Untested images__//
24 - A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before.
25 -
26 -PICTURE
21 +{{info}}With the release of Spring 6 in our previous release, some users reported that their filters have begun logging warnings about discarding messages even though the filter is configured to not throw an exception on rejection. For flows that process high numbers of messages (and potentially discard a lot of messages as well) this can significantly disturb the overview of the logs in the manage phase.
27 27  
23 +To mitigate this, you can change the filter that throws the warning so it specifically refers to a discard channel. Given the chosen configuration, we advice to use the nullChannel option. This will silently drop the message without registering a warning in the log. In case you find the warning in the log a nice addition, we suggest to add an explicit discard channel leading to a logging outbound channel adapter. This log component can then be configured to throw a warning.
28 28  
25 +In the next release, we will aid you by adding a validation check that will force you to select a discard channel when it is currently not selected once you edit the flow to create a new version. More on this in the next release blog. {{/info}}
26 +
27 +
29 29  == **Bug Fixes** ==
29 +//__Error handling__//
30 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
30 30  
32 +//__Volume mapping passwords__//
33 +Passwords for network volumes are hidden on the machine after deployment.
31 31  
35 +//__Create integration removal__//
36 +When removing an integration from Create, the Create phase is now correctly updated.
32 32  
38 +//__Legacy statistics__//
39 +Legacy pages are now correctly hidden when running on the current runtime architecture.
33 33  
41 +//__Unused properties__//
42 +Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
34 34  
44 +//__Enumeration values__//
45 +Enumeration values for event processors can now be edited in Create.
46 +
47 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
48 +
49 +//__SFTP sessions__//
50 +SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released.
51 +
35 35  == **Fancy Forum Answers** ==
36 36  
37 37  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:
38 38  
39 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
56 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
57 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
58 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
40 40  
41 41  == **Key Takeaways** ==
42 42  
... ... @@ -46,7 +46,7 @@
46 46  * If you have feedback or ideas for us, talk to the Platypus
47 47  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
48 48  * Clear your browser cache (Ctrl + Shift + Del)
49 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
68 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
50 50  * Start thinking about how the license tracker can aid your development
51 51  * Start thinking about major, minor, and patch
52 52  * Keep making great integrations