Changes for page 214 - System Symphony

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -3,76 +3,18 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been achieved.
	6	+**Hi there, eMagiz developers!** This release ....
7	7
8	8
9		-== **Pop-up Improvements** ==
10		-//__Property releases__//
11		-When a new property release is created, this property release can now be viewed and 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		-
25		-== **Formatting & Alignments** ==
26		-
27		-//__Input fields__//
28		-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.
29		-
30		-//__UI improvements__//
31		-UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
32		-
33		-//__Runtime overview image versions__//
34		-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.
35		-
36		-//__Component changes reversion__//
37		-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.
38		-
39		-//__State generation statistics__//
40		-The state generation graphs will now show the correct number of cache hits and misses.
41		-
42		-//__Queue browser timestamps__//
43		-All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
44		-
45		-//__Addition and deletion of internal recipients__//
46		-Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
47		-
48		-
49	49	== **Feedback Items** ==
50	50
51		-//__Update flows__//
52		-In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
	11	+//__Failover setup__//
	12	+New components have been created to support a failover setup. Moreover, two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
53	53
54		-//__Q&A forum search__//
55		-The option to search by pressing the Enter key has been added to the Q&A forum.
56		-
57		-//__Memory settings__//
58		-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.
59		-
60		-//__Runtime validation__//
61		-Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
62		-
63		-
64	64	== **Bug Fixes** ==
65	65
66		-//__Removal of onramp__//
67		-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).
68	68
69		-//__Runtime statistics details__//
70		-We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
71	71
72		-//__Deployment prechecks__//
73		-During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
74		-
75		-
76	76	== **Fancy Forum Answers** ==
77	77
78	78	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: