Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 529.1
edited by Carlijn Kokkeler
on 2024/05/21 12:08
Change comment: There is no comment for this version
To version 392.1
edited by Carlijn Kokkeler
on 2024/02/16 12:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +214 - System Symphony
Content
... ... @@ -3,53 +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 done several improvements for failover and grouping, as well as for the placement of attributes in datamodels. Next to this, we have improved the Event Catalog overview for Catalog users. It is now also possible to use the back button on the eMagiz Q&A without your search being removed. Regarding bug fixes, the delete behaviour for containers has been improved, and scope properties will now be generated correctly. Lastly, the warning message that is given when importing an xsd has now been removed when the request or response message is empty.
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 -//__Event catalog__//
13 -For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier 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-2.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  
17 -//__Attribute placements__//
18 -Some improvements regarding the placement of attributes have been done:
19 -* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute.
20 -* Moving an attribute in the datamodel is now directly shown in the tree structure as well.
21 -* The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype.
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.
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
19 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]
24 24  
25 -//__Failover & grouping__//
26 -Some improvements regarding the widgets for failover and grouping have been done:
27 -* When executing a start/stop action on a group, the description of the step now contains the name of the group.
28 -* When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
21 +//__Monitoring graphs__//
22 +The monitoring graphs can now show data up to the last thirty days.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
24 +== **Bug Fixes** ==
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.
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
31 +//__Failover group helptext__//
32 +The helptext of the Group attribute has been improved.
33 33  
34 -== **Bug Fixes** ==
35 -//__XSD import__//
36 -When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion.
34 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
37 37  
38 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
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 -//__Container deletion__//
41 -The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
39 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
42 42  
43 -//__Scope properties__//
44 -We fixed an issue where the generation of scope properties was incorrect for the legacy API gateway runtimes using OAuth 2.0 security scheme.
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 46  == **Fancy Forum Answers** ==
47 47  
48 48  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:
49 49  
50 -* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
51 -* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
52 -* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||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"]]
53 53  
54 54  == **Key Takeaways** ==
55 55  
... ... @@ -59,7 +59,7 @@
59 59  * If you have feedback or ideas for us, talk to the Platypus
60 60  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
61 61  * Clear your browser cache (Ctrl + Shift + Del)
62 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
61 +* Check out the release notes [here]
63 63  * Start thinking about how the license tracker can aid your development
64 64  * Start thinking about major, minor, and patch
65 65  * Keep making great integrations