Skip to Content

Changes for page 214 - System Symphony

Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 375.1
edited by Carlijn Kokkeler
on 2024/02/12 15:14
Change comment: There is no comment for this version
To version 367.1
edited by Carlijn Kokkeler
on 2024/01/29 15:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -214 - System Symphony
1 +213 - Joyful Journeys
Content
... ... @@ -3,35 +3,71 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done.
7 7  
8 +== **Pop-up Improvements** ==
9 +
10 +//__Property releases__//
11 +When a new property release is created, this property release can now not only be viewed but also deleted.
12 +
13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
14 +
15 +//__Runtime deletion__//
16 +When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
17 +
18 +//__Wiretap & debug error messages__//
19 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
20 +
21 +//__Action messages__//
22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
23 +
24 +== **Formatting & Alignments** ==
25 +
26 +//__Input fields__//
27 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
28 +
29 +//__UI improvements__//
30 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
31 +
32 +//__Component changes reversion__//
33 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
34 +
35 +//__State generation statistics__//
36 +The state generation graphs will now show the correct number of cache hits and misses.
37 +
38 +//__Queue browser timestamps__//
39 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
40 +
41 +//__Addition and deletion of internal recipients__//
42 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
43 +
8 8  == **Feedback Items** ==
9 9  
10 -//__On premise Windows machines__//
11 -Support for deploying to on premise Windows machines has been delivered.
46 +//__Update flows__//
47 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
12 12  
13 -//__Adding multiple attributes__//
14 -It is now possible to add multiple existing attributes to an entity at once.
49 +//__Q&A forum search__//
50 +The option to search by pressing the Enter key has been added to the Q&A forum.
15 15  
16 -//__Monitoring graphs__//
17 -The monitoring graphs can now show data up to the last 30 days.
52 +//__Memory settings__//
53 +It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
18 18  
19 -== **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.
55 +//__Runtime validation__//
56 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
22 22  
23 -//__Failover group helptext__//
24 -The helptext of the Group attribute has been improved.
58 +//__Runtime overview image versions__//
59 +Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
25 25  
26 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
61 +== **Bug Fixes** ==
27 27  
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.
63 +//__Removal of onramp__//
64 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
30 30  
31 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
66 +//__Runtime statistics details__//
67 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
32 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.
69 +//__Deployment prechecks__//
70 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
35 35  
36 36  == **Fancy Forum Answers** ==
37 37