Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 486.1
edited by Carlijn Kokkeler
on 2024/04/23 15:19
Change comment: There is no comment for this version
To version 316.1
edited by Carlijn Kokkeler
on 2023/12/21 14:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -219 - Creation Carousel
1 +211 - Log Luminary
Content
... ... @@ -3,62 +3,76 @@
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, 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.
6 +**Hi there, eMagiz developers!**
7 7  
8 +== **TBD** ==
9 +
10 +
11 +
8 8  == **Feedback Items** ==
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.
14 +//__Runtime overview__//
15 +We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
12 12  
13 -//__Improved OpenAPI import__//
14 -The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
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.
19 +//__Missing properties overview__//
20 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
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.
24 +//__Breaking changes pop-up__//
25 +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'.
22 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.
27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
24 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}}
29 +//__External recipients emailaddress__//
30 +The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
26 26  
32 +//__Broker queue metrics dashboards__//
33 +It is now possible to select the MQTT broker in the queue metrics dashboards.
27 27  
28 -== **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.
35 +//__Runtime image version__//
36 +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.
31 31  
32 -//__Volume mapping passwords__//
33 -Passwords for network volumes are hidden on the machine after deployment.
38 +//__Runtime restart or redeploy overview__//
39 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
34 34  
35 -//__Create integration removal__//
36 -When removing an integration from Create, the Create phase is now correctly updated.
41 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
37 37  
38 -//__Legacy statistics__//
39 -Legacy pages are now correctly hidden when running on the current runtime architecture.
43 +== **Bug Fixes** ==
40 40  
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.
45 +//__Message throughput__//
46 +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.
43 43  
44 -//__Enumeration values__//
45 -Enumeration values for event processors can now be edited in Create.
48 +//__Cloud template upgrade unjust rollback__//
49 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
46 46  
47 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
51 +//__Missing log entries__//
52 +We improved crash handling so that log messages clearly show when and why a container failed to start.
48 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.
54 +//__Runtime logging__//
55 +We fixed a bug where no new log messages were showing up, even though they were produced by the container.
51 51  
57 +//__Next generation block__//
58 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
59 +
60 +//__Deployment execution error message__//
61 +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.
62 +
52 52  == **Fancy Forum Answers** ==
53 53  
54 54  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:
55 55  
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"]]
67 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
68 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
69 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
70 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
71 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
59 59  
60 -== **Key Takeaways** ==
61 61  
74 +== **Key takeaways** ==
75 +
62 62  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:
63 63  
64 64  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -65,9 +65,10 @@
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 66  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
82 +* Check out the release notes [here]
69 69  * Start thinking about how the license tracker can aid your development
70 70  * Start thinking about major, minor, and patch
85 +* Upgrade to the latest build number
71 71  * Keep making great integrations
72 72  
73 73  Let's stay in touch and till next time!
... ... @@ -75,6 +75,7 @@
75 75  {{info}}
76 76  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  
93 +~*~* Indicates a next-generation-architecture only feature.
78 78  {{/info}}
79 79  )))
80 80