Skip to Content

Changes for page 214 - System Symphony

Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 145.1
edited by Erik Bakker
on 2023/08/15 11:35
Change comment: There is no comment for this version
To version 376.1
edited by Carlijn Kokkeler
on 2024/02/12 15:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -203 - Fast Paced
1 +214 - System Symphony
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,46 +1,58 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
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 30 days. Moreover, support for deploying to on premise Windows machines is now available. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done.
6 6  
7 -== **Release Properties - Early Feedback** ==
8 -The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
9 -
10 10  == **Feedback Items** ==
11 11  
12 -//__"All entries" are now cleaned up as part of the migration__//
13 -To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
10 +//__On premise Windows machines__//
11 +Support for deploying to on premise Windows machines has been delivered.
14 14  
15 -//__Trigger ID added to our alerting on the next-generation architecture__//
16 -We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
13 +//__Adding multiple attributes__//
14 +It is now possible to add multiple existing attributes to an entity at once.
17 17  
16 +//__Monitoring graphs__//
17 +The monitoring graphs can now show data up to the last 30 days.
18 +
18 18  == **Bug Fixes** ==
20 +//__Image versions__//
21 +The deletion of releases with deployed container versions will not be blocked anymore. Automated release clean up behaviour will also not exclude these releases from deletion. 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.
19 19  
20 -//__Ensure no flow can be in a release twice__//
21 -We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
23 +//__Failover group helptext__//
24 +The helptext of the Group attribute has been improved.
22 22  
23 -//__Ensure no flow can be in a release twice__//
24 -We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
26 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
25 25  
28 +//__Failover group refresh__//
29 +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 Group tab of "Start/Stop Flows" screen.
30 +
31 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
32 +
33 +//__Resource paths__//
34 +After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
35 +
26 26  == **Fancy Forum Answers** ==
27 27  
28 28  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:
29 29  
30 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
40 +* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]]
41 +* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]]
42 +* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]]
43 +* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]]
31 31  
32 -== **Key takeaways** ==
45 +== **Key Takeaways** ==
33 33  
34 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
47 +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:
35 35  
36 36  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
37 37  * If you have feedback or ideas for us, talk to the Platypus
38 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
51 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
39 39  * Clear your browser cache (Ctrl + Shift + Del)
40 40  * Check out the release notes [here]
41 41  * Start thinking about how the license tracker can aid your development
42 42  * Start thinking about major, minor, and patch
43 -* Upgrade to the latest build number
44 44  * Keep making great integrations
45 45  
46 46  Let's stay in touch and till next time!
... ... @@ -48,6 +48,11 @@
48 48  {{info}}
49 49  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
50 50  
51 -~*~* Indicates a next-generation-architecture only feature.
52 -{{/info}})))((({{toc/}}))){{/container}}
63 +{{/info}}
64 +)))
65 +
66 +(((
67 +{{toc/}}
68 +)))
53 53  {{/container}}
70 +{{/container}}