Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 488.1
edited by Carlijn Kokkeler
on 2024/04/23 16:30
on 2024/04/23 16:30
Change comment:
There is no comment for this version
To version 392.1
edited by Carlijn Kokkeler
on 2024/02/16 12:08
on 2024/02/16 12:08
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 +214 - System Symphony - Content
-
... ... @@ -3,58 +3,52 @@ 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 anew versionof oureMagizMendixconnector available,thatwill supportMendixversion10and higher.Furthermore,wehave improvedour functionalitytoenableuserstoseamlesslyimportOpenAPIspecificationswithURLpathsofupto300 charactersinlength.Lastly, wehavedoneany bug fixes,one ofwhichwill ensurethatSFTPsessions willbeclosedagainafter completion.For this fix, a new[[runtimeimage>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]]hasbeenpublished.6 +**Hi there, eMagiz developers!** This release contains multiple bug fixes, as well as some other improvements. The monitoring graphs have been improved, such that they can now show data up to the last thirty days. Moreover, we can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done. 7 7 8 8 == **Feedback Items** == 9 9 10 -//__e Magiz Mendixconnector__//11 -We releasedanewversion ofoureMagiz MendixconnectorthatwillsupportMendixversion10and higher.10 +//__On premise Windows machines__// 11 +We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. 12 12 13 - //__ImprovedOpenAPIimport__//14 - Thepathlength thateMagiz supports whenimportingOpenAPIspecificationsis now increased toamaximum of 300 characters.13 +[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]] 14 + [[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-windows.png]] 15 15 16 -//__ Flowteststacktrace__//17 -I faflowtest createsa log linewith level ‘Warning’or‘Error’andthereisastacktracecreated,thenweshowthestacktraceinside thelogmessage ona separatetab.16 +//__Adding multiple attributes__// 17 +It is now possible to add multiple existing attributes to an entity at once. This saves time when having to add multiple attributes to an entity. 18 18 19 -[[image:Main.Images.Release Blog.WebHome@release-21 9-creation-carousel-stack-trace.png]]19 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.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. 21 +//__Monitoring graphs__// 22 +The monitoring graphs can now show data up to the last thirty days. 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. 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. 25 +//__Image versions__// 26 +To keep the overview of releases compact we now have improved the (automatic) deletion behavior in the following way: 27 +* The deletion of releases with deployed container versions will not be blocked anymore. 28 +* Automated release clean up behaviour will also not exclude these releases from deletion. 29 +* Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases. 30 30 31 -//__ Volumemapping passwords__//32 - Passwords for networkvolumesare nowsecurely hidden inthe runtime’smachine afterdeployinga newrelease.31 +//__Failover group helptext__// 32 +The helptext of the Group attribute has been improved. 33 33 34 -//__Create integration removal__// 35 -When removing an integration from Create, the Create phase is now correctly updated. 34 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 36 36 37 -//__ Legacystatistics__//38 - Legacypages are nowcorrectlyhiddenwhenrunningonthecurrent runtime architecture.36 +//__Failover group refresh__// 37 +A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in the Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed. 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. 39 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 42 42 43 -//__ Enumeration values__//44 - Usersarenowabletoaddandedit enumerationvalueswhile editingevent processorflowsin theCreatephase.41 +//__Resource paths__// 42 +After migrating a gateway away fom the legacy runtime architecture, the path references in the event processors would be broken. This has been fixed. 45 45 46 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 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. 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"]] 48 +* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]] 49 +* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]] 50 +* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]] 51 +* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||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"]]61 +* Check out the release notes [here] 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