Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 487.1
edited by Carlijn Kokkeler
on 2024/04/23 15:25
Change comment: There is no comment for this version
To version 567.1
edited by Carlijn Kokkeler
on 2024/06/18 11:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -219 - Creation Carousel
1 +223 - TBD
Content
... ... @@ -3,58 +3,54 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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, we have improved our functionality to enable users to seamlessly import OpenAPI specifications with URL paths of up to 300 characters in length. 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.
6 +**Hi there, eMagiz developers!** In the past week, we have worked hard to release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]]. This image contains several bug fixes, and increases the debugger duration. Next to this, improvements have been done to the SwaggerUI settings, we have resolved more deprecated warnings to prepare for Mendix version 10, and it is now possible to filter on the use of message types in Capture. Moreover, we have done bug fixes related to viewing an XSLT and SpEL expressions used for contructing a multipart/form-data HTTP request.
7 7  
8 8  == **Feedback Items** ==
9 +//__SwaggerUI default__//
10 +Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown.
9 9  
10 -//__eMagiz Mendix connector__//
11 -We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
12 12  
13 -//__Improved OpenAPI import__//
14 -The path length that eMagiz supports when importing OpenAPI specifications is now increased to a maximum of 300 characters.
14 +//__Deprecated warnings__//
15 +We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10.
15 15  
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.
17 +//__Used message types__//
18 +It is now possible to filter the message types in Capture on whether they are used.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
20 +[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]]
21 +
22 +//__Debugger duration__//
23 +Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5. Note that the JMS server needs to be reset (or updated) in order to also store the messages for 10 minutes instead of 5. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
20 20  
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.
22 -
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.
24 -
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 27  == **Bug Fixes** ==
28 -//__Error handling__//
29 -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.
26 +//__SFTP sessions__//
27 +Support has been added to provide SFTP session factories with a known_hosts in string format rather than file format, so that it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification.
30 30  
31 -//__Volume mapping passwords__//
32 -Passwords for network volumes are now securely hidden in the runtime’s machine after deploying a new release.
29 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
33 33  
34 -//__Create integration removal__//
35 -When removing an integration from Create, the Create phase is now correctly updated.
36 36  
37 -//__Legacy statistics__//
38 -Legacy pages are now correctly hidden when running on the current runtime architecture.
32 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
39 39  
40 -//__Unused properties__//
41 -Users should not be able to edit or delete eMagiz properties, and so these eMagiz properties will now not be shown in the 'Unused property overview' anymore.
34 +//__SMB outbound gateway__//
35 +The SMB outbound gateway with the GET command did not work, this has been resolved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
42 42  
43 -//__Enumeration values__//
44 -Enumeration values for event processors can now be edited in Create.
37 +//__TaskScheduler__//
38 +In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
40 +//__View XSLT__//
41 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
47 47  
48 -//__SFTP sessions__//
49 -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.
43 +//__Multipart/form-data HTTP request__//
44 +The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. The [[legacy documentation>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available.
50 50  
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
55 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
56 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
57 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
50 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
51 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
52 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
53 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
58 58  
59 59  == **Key Takeaways** ==
60 60  
... ... @@ -64,7 +64,7 @@
64 64  * If you have feedback or ideas for us, talk to the Platypus
65 65  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66 66  * Clear your browser cache (Ctrl + Shift + Del)
67 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
63 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
68 68  * Start thinking about how the license tracker can aid your development
69 69  * Start thinking about major, minor, and patch
70 70  * Keep making great integrations