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	+202 - New Equilibrium

Author

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

Content

...	...	@@ -1,92 +1,84 @@
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!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.
7	7
8		-== **Pop-up Improvements** ==
	7	+== **Release Properties** ==
	8	+As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, timing of changing properties was crucial to avoid costly mistakes on Production. On top of that it was not always clear whether a property value was indeed updated as it was not linked to something that was deployed. These considerations let us to change the property management behavior not only on our next-generation architecture but also on our current generation architecture. Having said that, there are several key changes compared to the current way of managing your properties. Most notably among these are:
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.
	10	+* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
	11	+* Property placeholders (i.e. the names of properties as given in Create) are now automatically created for you. This to avoid mistakes when filling them in.
	12	+* When adding or editing a property you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double lane setup or having a distributed landscape of containers.
	13	+* A, for most, new concept of a "property release" is introduced. With the help of this functionality you can easily change a property on Production without having to create a completely new release in Test and promote it to the Production environment.
12	12
13		-[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
	15	+{{info}}For more information please check out the following microlearnings:
14	14
15		-//__Runtime deletion__//
16		-When deleting a runtime, the error message is more descriptive. The error message will now include the names of the flows that run on the container.
	17	+* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
	18	+* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
	19	+* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
17	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.
	21	+Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	22	+{{/info}}
20	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.
	24	+== ** Manage - Next generation graphs improvements ** ==
	25	+As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the manage graphs as we retrieve and show less fine-grained information when zooming out.
23	23
24		-== **Formatting & Alignments** ==
	27	+[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
25	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.
	29	+== **Feedback Items** ==
28	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	+//__Improved editability when testing in eMagiz wihout Edit rights in Create__//
	32	+Without having edit rights in the Create phase you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we missed during the implementation. These have been fixed allowing those without edit rights to now also change the name and description of the test case.
31	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	+//__Improved auditability on Deploy Architecture__//
	35	+To improve the audtiability on Deploy Architecture we now also log when someone with Admin rights changes specific functions on this level (i.e. Fixed IP).
34	34
35		-//__State generation statistics__//
36		-The state generation graphs will now show the correct number of cache hits and misses.
	37	+//__Test your own exported work__//
	38	+We have now made it possible to test your own exported work to the Store before it gets approved. This will increase the quality of store items we have, and our partners, have on offer within the store.
37	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	+{{info}}In case the concept of the store is new for you please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
40	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.
	42	+//__Improved Audit Trail on several places__//
	43	+In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
43	43
44		-== **Feedback Items** ==
	45	+//__Removed the erroneous alert on message mapping when having a passthrough API__//
	46	+This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
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.
48		-
49		-//__Q&A forum search__//
50		-The option to search by pressing the Enter key has been added to the Q&A forum.
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.
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).
	50	+//__Avoid clicking on other components while deleting another__//
	51	+To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
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.
	53	+//__Improved validation feedback in migrating to the next-generation architecture__//
	54	+We have improved the validation feedback when migrating to the next-generation architecture.
67	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.
	56	+//__Make sure that user credentials can be viewed with view rights__//
	57	+This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
70	70
	59	+//__Refresh behavior within the deployment plan is fixed__//
	60	+This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
	61	+
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"]]
	66	+* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
	67	+* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
	68	+* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
78	78
79		-== **Key Takeaways** ==
	70	+== **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:
	72	+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.
	76	+* 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
	81	+* 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		-)))
	89	+~*~* Indicates a GEN3-only feature.
	90	+{{/info}})))((({{toc/}}))){{/container}}
103	103	{{/container}}
104		-{{/container}}