Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 520.1
edited by Carlijn Kokkeler
on 2024/05/21 10:52
on 2024/05/21 10:52
Change comment:
There is no comment for this version
To version 391.1
edited by Carlijn Kokkeler
on 2024/02/14 10:10
on 2024/02/14 10:10
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 -2 21 - Swift Shift1 +214 - System Symphony - Content
-
... ... @@ -3,29 +3,52 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** 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 -//__Q&A search__// 10 -Search results are now persisted when pressing the back button after opening a question in the community Q & A. 11 11 12 -//__ Eventcatalog__//13 - ForCatalogusers,wehavesignificantlyimprovedtheEventCatalogoverviewbyintroducingamuch simplerlayoutforr navigation.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. 14 14 15 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog.png]] 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]] 16 16 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 + 19 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]] 20 + 21 +//__Monitoring graphs__// 22 +The monitoring graphs can now show data up to the last thirty days. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed. 23 + 17 17 == **Bug Fixes** == 18 -//__XSD import__// 19 -When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. 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. 20 20 21 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]] 31 +//__Failover group helptext__// 32 +The helptext of the Group attribute has been improved. 22 22 34 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 35 + 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. 38 + 39 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 40 + 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. 43 + 23 23 == **Fancy Forum Answers** == 24 24 25 25 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: 26 26 27 -* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]] 28 -* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||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"]] 29 29 30 30 == **Key Takeaways** == 31 31 ... ... @@ -35,7 +35,7 @@ 35 35 * If you have feedback or ideas for us, talk to the Platypus 36 36 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 37 37 * Clear your browser cache (Ctrl + Shift + Del) 38 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]61 +* Check out the release notes [here] 39 39 * Start thinking about how the license tracker can aid your development 40 40 * Start thinking about major, minor, and patch 41 41 * Keep making great integrations