Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 489.1
edited by Carlijn Kokkeler
on 2024/04/24 09:20
on 2024/04/24 09:20
Change comment:
There is no comment for this version
To version 308.1
edited by Carlijn Kokkeler
on 2023/12/21 14:05
on 2023/12/21 14:05
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -21 9-CreationCarousel1 +211 - Log Luminary - Content
-
... ... @@ -3,64 +3,65 @@ 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!** 7 7 8 -== ** Feedback Items** ==8 +== **TBD** == 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 12 13 -//__External machine agents__// 14 -We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents on the current generation architecture from the portal. With future releases of environment templates, your on-premise agents may also be updated. 15 15 16 -//__Improved OpenAPI import__// 17 -The path length that eMagiz supports when importing OpenAPI specifications is now increased to a maximum of 300 characters. 12 +== **Feedback Items** == 18 18 19 -//__ Flowteststack trace__//20 - If a flow testcreatesalog lineithlevel‘Warning’or ‘Error’ andthereisatack trace created,thenwe show thestacktraceinsidethe log messageon aseparatetab.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. 21 21 22 -[[image:Main.Images.Release Blog.WebHome@release-21 9-creation-carousel-stack-trace.png]]17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 23 23 24 -{{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. 19 +//__Missing properties overview__// 20 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 25 25 26 - To mitigatethis, you canchangethefilter that throwsthewarning so it specifically refers toa discard channel.Given the chosen configuration, weadvice to use the nullChannel option. Thiswill silently drop themessage without registeringa warning in the log. In caseyou find the warning inthe log a niceaddition, wesuggest toadd anexplicit discard channel leading to a logging outbound channel adapter.This log component can then be configured to throw a warning.22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 27 27 28 -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}} 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'. 29 29 30 -== **Bug Fixes** == 31 -//__Error handling__// 32 -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. 27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 33 33 34 -//__ Volume mappingpasswords__//35 - Passwordsfornetworkvolumesare nowsecurelyhiddenin theruntime’smachineafter deployinganewrelease.29 +//__Broker queue metrics dashboards__// 30 +It is now possible to select the MQTT broker in the queue metrics dashboards. 36 36 37 -//__ Create integrationremoval__//38 - Whenremovinganintegration fromCreate,theCreatephase isnowcorrectlyupdated.32 +//__Runtime image version__// 33 +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. 39 39 40 -//__Legacy statistics__// 41 -Legacy pages are now correctly hidden when running on the current runtime architecture. 35 +== **Bug Fixes** == 42 42 43 -//__ Unusedproperties__//44 - Users should not be able toeditordelete eMagizproperties,andsotheseeMagizproperties will nownot beshowninthe'Unused propertyoverview'anymore.37 +//__Message throughput__// 38 +The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. 45 45 46 -//__ Enumerationvalues__//47 - Users are nowable to addand edit enumerationvalues while editing event processorflowsin theCreatephase.40 +//__Deployment execution error message__// 41 +In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup. 48 48 49 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 43 +//__Cloud template upgrade unjust rollback__// 44 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3. 50 50 51 -//__ SFTPsessions__//52 - SFTP sessionfactoriesdidnotclose theirconnectionafter it wascomplete. Thiscould cause connection starvationonthe SFTP server,andwas especially noticablewhen usingtheSFTP SessionFactorywithoutcaching,asthat factoryopensanewconnection for every call. For this, anew [[runtimeimage>>doc:Main.ReleaseInformation.RuntimeImages.V304.WebHome||target="blank"]] has been released.46 +//__Missing log entries__// 47 +We improved crash handling so that log messages clearly show when and why a container failed to start. 53 53 49 +//__Runtime logging__// 50 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 51 + 54 54 == **Fancy Forum Answers** == 55 55 56 56 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: 57 57 58 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 59 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 60 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 56 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 57 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 58 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 59 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 60 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 61 61 62 -== **Key Takeaways** == 63 63 63 +== **Key takeaways** == 64 + 64 64 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: 65 65 66 66 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -67,9 +67,10 @@ 67 67 * If you have feedback or ideas for us, talk to the Platypus 68 68 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 69 69 * Clear your browser cache (Ctrl + Shift + Del) 70 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]71 +* Check out the release notes [here] 71 71 * Start thinking about how the license tracker can aid your development 72 72 * Start thinking about major, minor, and patch 74 +* Upgrade to the latest build number 73 73 * Keep making great integrations 74 74 75 75 Let's stay in touch and till next time! ... ... @@ -77,6 +77,7 @@ 77 77 {{info}} 78 78 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 79 79 82 +~*~* Indicates a next-generation-architecture only feature. 80 80 {{/info}} 81 81 ))) 82 82