Skip to Content

Changes for page 215 - Tiny Tales

Last modified by Carlijn Kokkeler on 2024/04/18 13:05
From version 304.1
edited by Carlijn Kokkeler
on 2023/12/21 13:51
Change comment: There is no comment for this version
To version 375.1
edited by Carlijn Kokkeler
on 2024/02/12 15:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +214 - System Symphony
Content
... ... @@ -3,59 +3,46 @@
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 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.
7 7  
8 -== **TBD** ==
9 -
10 -
11 -
12 12  == **Feedback Items** ==
13 13  
14 -//__Runtime overview__//
15 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
10 +//__On premise Windows machines__//
11 +Support for deploying to on premise Windows machines has been delivered.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
13 +//__Adding multiple attributes__//
14 +It is now possible to add multiple existing attributes to an entity at once.
18 18  
19 -//__Missing properties overview__//
20 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
16 +//__Monitoring graphs__//
17 +The monitoring graphs can now show data up to the last 30 days.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
23 -
24 -//__Breaking changes pop-up__//
25 -Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
26 -
27 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
28 -
29 -//__Broker queue metrics dashboards__//
30 -It is now possible to select the MQTT broker in the queue metrics dashboards.
31 -
32 32  == **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.
33 33  
34 -//__Deployment execution error message__//
35 -In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup.
23 +//__Failover group helptext__//
24 +The helptext of the Group attribute has been improved.
36 36  
37 -//__Cloud template upgrade unjust rollback__//
38 -An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
26 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
39 39  
40 -//__Missing log entries__//
41 -We improved crash handling so that log messages clearly show when and why a container failed to start.
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.
42 42  
43 -//__Runtime logging__//
44 -We fixed a bug where no new log messages were showing up, even though they were produced by the container.
31 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
45 45  
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 +
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 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
51 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
52 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
53 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
54 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
40 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
41 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
42 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
55 55  
44 +== **Key Takeaways** ==
56 56  
57 -== **Key takeaways** ==
58 -
59 59  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:
60 60  
61 61  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -65,7 +65,6 @@
65 65  * Check out the release notes [here]
66 66  * Start thinking about how the license tracker can aid your development
67 67  * Start thinking about major, minor, and patch
68 -* Upgrade to the latest build number
69 69  * Keep making great integrations
70 70  
71 71  Let's stay in touch and till next time!
... ... @@ -73,7 +73,6 @@
73 73  {{info}}
74 74  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75 75  
76 -~*~* Indicates a next-generation-architecture only feature.
77 77  {{/info}}
78 78  )))
79 79