Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Content

...	...	@@ -5,16 +5,71 @@
5	5
6	6	**Hi there, eMagiz developers!** This release ....
7	7
	8	+== **Pop-up Improvements** ==
	9	+//__Property releases__//
	10	+When a new property release is created, this property release can now be viewed and deleted.
8	8
	12	+[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
	13	+
	14	+//__Runtime deletion__//
	15	+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.
	16	+
	17	+//__Wiretap & debug error messages__//
	18	+The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
	19	+
	20	+//__Action messages__//
	21	+The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
	22	+
	23	+== **Formatting & Alignments** ==
	24	+
	25	+//__Input fields__//
	26	+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.
	27	+
	28	+//__UI improvements__//
	29	+UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
	30	+
	31	+//__Runtime overview image versions__//
	32	+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.
	33	+
	34	+//__Component changes reversion__//
	35	+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.
	36	+
	37	+//__State generation statistics__//
	38	+The state generation graphs will now show the correct number of cache hits and misses.
	39	+
	40	+//__Queue browser timestamps__//
	41	+All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
	42	+
	43	+//__Addition and deletion of internal recipients__//
	44	+Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
	45	+
9	9	== **Feedback Items** ==
10	10
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"]].
	48	+//__Update flows__//
	49	+In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
13	13
	51	+//__Q&A forum search__//
	52	+The option to search by pressing the Enter key has been added to the Q&A forum.
	53	+
	54	+//__Memory settings__//
	55	+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.
	56	+
	57	+//__Runtime validation__//
	58	+Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
	59	+
	60	+
14	14	== **Bug Fixes** ==
15	15
	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).
16	16
	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.
17	17
	69	+//__Deployment prechecks__//
	70	+During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
	71	+
	72	+
18	18	== **Fancy Forum Answers** ==
19	19
20	20	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: