Skip to Content

Changes for page 214 - System Symphony

Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 149.1
edited by Erik Bakker
on 2023/08/29 10:56
Change comment: There is no comment for this version
To version 373.1
edited by Carlijn Kokkeler
on 2024/02/12 15:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -204 - Found It
1 +214 - System Symphony
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,49 +1,54 @@
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 additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
6 +**Hi there, eMagiz developers!** In this release, ...
6 6  
7 7  == **Feedback Items** ==
8 8  
9 -//__Improved check on nested property placeholders__//
10 -To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
10 +//__Update flows__//
11 +Support for deploying to on premise Windows machines has been delivered.
11 11  
12 -//__Removed outdated properties when deploying on the new generation architecture stack__//
13 -We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before connecting to a Kafka cluster but have become obsolete once you migrate.
13 +//__Image versions__//
14 +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.
14 14  
15 -{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
16 +//__Adding multiple attributes__//
17 +It is now possible to add multiple existing attributes to an entity at once.
16 16  
17 -//__Improved performance Manage Dashboards__//
18 -We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
19 19  
20 +
21 +
20 20  == **Bug Fixes** ==
23 +//__Failover group helptext__//
24 +The helptext of the Group attribute has been improved.
21 21  
22 -//__Errors with long stack traces or long message histories will now also show in eMagiz__//
23 -We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
26 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
24 24  
25 -//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
26 -We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
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.
27 27  
31 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
32 +
28 28  == **Fancy Forum Answers** ==
29 29  
30 30  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:
31 31  
32 -* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
33 -* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
37 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
38 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
39 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
34 34  
35 -== **Key takeaways** ==
41 +== **Key Takeaways** ==
36 36  
37 37  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:
38 38  
39 39  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
40 40  * If you have feedback or ideas for us, talk to the Platypus
41 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
47 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
42 42  * Clear your browser cache (Ctrl + Shift + Del)
43 43  * Check out the release notes [here]
44 44  * Start thinking about how the license tracker can aid your development
45 45  * Start thinking about major, minor, and patch
46 -* Upgrade to the latest build number
47 47  * Keep making great integrations
48 48  
49 49  Let's stay in touch and till next time!
... ... @@ -51,6 +51,11 @@
51 51  {{info}}
52 52  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53 53  
54 -~*~* Indicates a next-generation-architecture only feature.
55 -{{/info}})))((({{toc/}}))){{/container}}
59 +{{/info}}
60 +)))
61 +
62 +(((
63 +{{toc/}}
64 +)))
56 56  {{/container}}
66 +{{/container}}