Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-213 - Joyful Journeys
	1	+203 - Fast Paced

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.CarlijnKokkeler
	1	+XWiki.ebakker

Content

...	...	@@ -1,92 +1,46 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
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 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.
	5	+**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
7	7
8		-== **Pop-up Improvements** ==
	7	+== **Release Properties - Early Feedback** ==
	8	+The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
9	9
10		-//__Property releases__//
11		-When a new property release is created, this property release can now not only be viewed but also release properties can be 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		-
44	44	== **Feedback Items** ==
45	45
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	+//__"All entries" are now cleaned up as part of the migration__//
	13	+To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
48	48
49		-//__Q&A forum search__//
50		-The option to search by pressing the Enter key has been added to the Q&A forum.
	15	+//__Trigger ID added to our alerting on the next-generation architecture__//
	16	+We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
51	51
52		-//__Memory settings__//
53		-It is now possible to change the memory settings of a newly added container before pressing "Apply to environment".
54		-//__Runtime validation__//
55		-Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
	18	+//__Improved performance Manage Dashboards__//
	19	+We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture.
56	56
57		-//__Runtime overview image versions__//
58		-Insight into intended 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.
59		-
60	60	== **Bug Fixes** ==
61	61
62		-//__Removal of onramp__//
63		-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).
	23	+//__Ensure no flow can be in a release twice__//
	24	+We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
64	64
65		-//__Runtime statistics details__//
66		-We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
67		-
68		-//__Deployment prechecks__//
69		-During deployments, prechecks can be executed on runtimes level for runtimes that still have to be deployed. These prechecks can be executed via Deploy > Architecture.
70		-
71	71	== **Fancy Forum Answers** ==
72	72
73	73	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:
74	74
75		-* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
76		-* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
77		-* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
	30	+* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
78	78
79		-== **Key Takeaways** ==
	32	+== **Key takeaways** ==
80	80
81		-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:
	34	+Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
82	82
83	83	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
84	84	* If you have feedback or ideas for us, talk to the Platypus
85		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	38	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
86	86	* Clear your browser cache (Ctrl + Shift + Del)
87	87	* Check out the release notes [here]
88	88	* Start thinking about how the license tracker can aid your development
89	89	* Start thinking about major, minor, and patch
	43	+* Upgrade to the latest build number
90	90	* Keep making great integrations
91	91
92	92	Let's stay in touch and till next time!
...	...	@@ -94,11 +94,6 @@
94	94	{{info}}
95	95	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
96	96
97		-{{/info}}
98		-)))
99		-
100		-(((
101		-{{toc/}}
102		-)))
	51	+~*~* Indicates a next-generation-architecture only feature.
	52	+{{/info}})))((({{toc/}}))){{/container}}
103	103	{{/container}}
104		-{{/container}}