Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 332.1
edited by Carlijn Kokkeler
on 2024/01/03 10:01
Change comment: There is no comment for this version
To version 564.1
edited by Carlijn Kokkeler
on 2024/06/18 11:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +223 - TBD
Content
... ... @@ -3,70 +3,56 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes, mainly relating to the Deploy and Manage phase.
6 +**Hi there, eMagiz developers!**
7 +
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.
7 7  
8 -== **Logging** ==
9 -//__Missing log entries__//
10 -We improved crash handling so that log messages clearly show when and why a container failed to start.
12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
11 11  
12 -//__Runtime logging__//
13 -We fixed a bug where no new log messages were showing up, even though they were produced by a container.
14 +//__Deprecated warnings__//
15 +We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10.
14 14  
15 -//__Deployment execution error message__//
16 -In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
17 +//__Used message types__//
18 +It is now possible to filter the message types in Capture on whether they are used.
17 17  
18 -== **Overviews** ==
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.
19 19  
20 -//__Runtime overview__//
21 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
25 +== **Bug Fixes** ==
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.
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
29 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
24 24  
25 -//__Missing properties overview__//
26 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
27 27  
28 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
32 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
29 29  
30 -//__Runtime restart or redeploy overview__//
31 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
34 +//__SFTP sessions__//
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.
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
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.
34 34  
35 -== **Feedback Items** ==
40 +//__View XSLT__//
41 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
36 36  
37 -//__Breaking changes pop-up__//
38 -Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
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.
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
41 -
42 -//__External recipients emailaddress__//
43 -The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
44 -
45 -//__Broker queue metrics dashboards__//
46 -It is now possible to select the MQTT broker in the queue metrics dashboards.
47 -
48 -//__Runtime image version__//
49 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
50 -
51 -
52 -== **Bug Fixes** ==
53 -
54 -//__Message throughput__//
55 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
56 -
57 -//__Cloud template upgrade incorrect rollback__//
58 -An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
59 -
60 -//__Next generation block__//
61 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
62 -
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  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:
66 66  
67 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||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"]]
68 68  
69 -== **Key takeaways** ==
55 +== **Key Takeaways** ==
70 70  
71 71  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
72 72  
... ... @@ -74,7 +74,7 @@
74 74  * If you have feedback or ideas for us, talk to the Platypus
75 75  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76 76  * Clear your browser cache (Ctrl + Shift + Del)
77 -* Check out the release notes [here]
63 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
78 78  * Start thinking about how the license tracker can aid your development
79 79  * Start thinking about major, minor, and patch
80 80  * Keep making great integrations