Changes for page 240 - Spring Cleaning
Last modified by Erik Bakker on 2025/03/10 10:00
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 603.1
edited by Erik Bakker
on 2024/07/16 14:38
on 2024/07/16 14:38
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 19-CreationCarousel1 +225 - Pop-up Party - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -3,61 +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 haveanewversion of oureMagiz Mendixconnectoravailable,that will support Mendix version10and higher.Furthermore,we have improved ourfunctionalitytoenableuserstoseamlesslyimportOpenAPIspecificationswithURL paths of upto300charactersinlength.Lastly, we have donemany bugfixes,oneof which will ensurethat SFTP sessionswill be closed againaftercompletion. For thisfix,aew[[runtime image>>doc:Main.ReleaseInformation.RuntimeImages.V304.WebHome||target="blank"]] hasbeenpublished.6 +**Hi there, eMagiz developers!** In this release, a new runtime image (LINK) will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens. Find out all we released below! 7 7 8 8 == **Feedback Items** == 9 +//__Alerting notification settings__// 9 9 10 -//__e MagizMendixconnector__//11 - WereleasedanewversionofureMagizMendixconnectorthatwill supportMendixversion10andhigher.11 +//__Process containers__// 12 +If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern. 12 12 13 -//__ External machineagents__//14 -W ehaveadded functionalitythat allowstheuserto (auto-)updatetheirexternal(on-premise)machineagentson thecurrentgenerationarchitecturefromtheportal.Withfuture releasesofenvironmenttemplates, your on-premise agents may also be updated.14 +//__Design settings__// 15 +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. 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. 17 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]] 18 18 19 -//__Flow test stack trace__// 20 -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 +//__Untested images__// 20 + 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. 21 + 22 +[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]] 21 21 22 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]] 24 +//__Infinispan Cache Manager__// 25 +We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available. 26 + 27 +//__Infinispan Cache Manager error message__// 28 +We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available. 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. 30 +//__Flow bump__// 31 +When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description. 32 + 33 +[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]] 25 25 26 -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. 35 +//__Unused support objects__// 36 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'. 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}} 38 +[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]] 39 + 40 +//__Deleting routes__// 41 +For clarity purposes, a confirmation pop-up will be shown when deleting routes. 29 29 43 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]] 44 + 45 +//__Debug queue__// 46 +The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it. 47 + 48 +[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]] 49 + 30 30 == **Bug Fixes** == 31 -//__ Errorhandling__//32 - Whenmigratingto thecurrent generationarchitecture,thedefault errorhandlingwillnowalsobe migratedcorrectly,sothatnomanualchangeshave tobedone forthis.51 +//__Internal server error__// 52 +The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it. 33 33 34 -//__ Volumemappingpasswords__//35 - Passwordsfornetwork volumesre nowsecurelyhiddenheruntime’smachine afterdeployinganewrelease.54 +//__Namespace update__// 55 +Editing a namespace used in a message definition automatically updates the message definition & transformations. 36 36 37 -//__ Create integrationremoval__//38 -W hen removingan integrationfrom Create,theCreatephaseis nowcorrectlyupdated.57 +//__Error pop-up__// 58 +We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows. 39 39 40 -//__ Legacystatistics__//41 - Legacypagesare nowcorrectly hiddenwhen runningonthe currentruntimearchitecture.60 +//__SMB inbound channel adapter__// 61 +The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new runtime image LINK is available. 42 42 43 -//__ Unusedproperties__//44 - Usersshouldnotbeabletoeditor delete eMagizproperties,andsotheseeMagiz propertieswill nownotbeshowninthe'Unusedpropertyoverview'anymore.63 +//__Heap memory__// 64 +The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available. 45 45 46 -//__ Enumerationvalues__//47 - Usersarenow abletoadd and editenumerationvalueswhile editingevent processorflowsin theCreatephase.66 +//__Classpath conflicts__// 67 +We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. 48 48 49 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 50 - 51 -//__SFTP sessions__// 52 -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. 53 - 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 -* [[ Createanoverviewof DataFlowswithoutanydatatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]59 -* [[ Flowtestdoesnotwork>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]60 -* [[ Debuggerblocks allothertraffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]73 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 74 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 75 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 61 61 62 62 == **Key Takeaways** == 63 63 ... ... @@ -67,7 +67,7 @@ 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.2 19-CreationCarousel.WebHome||target="blank"]]85 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]] 71 71 * Start thinking about how the license tracker can aid your development 72 72 * Start thinking about major, minor, and patch 73 73 * Keep making great integrations