Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-185 - Get ready
	1	+202 - New Equilibrium

Author

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

Content

...	...	@@ -2,46 +2,74 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
	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.
6	6
7		-==**Audit trail User Management**==
8		-Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
9		-
10		-[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
	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:
11	11
12		-==**Next Generation Monitoring & Alerting engine**==
13		-In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
14		-
15		-* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
16		-* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
17		-* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
18		-* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
19		-* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
20		-
21		-
22		-=== **Improvements** ===
23		-
24		-* Performance Deployment plan
25		-When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
26		-
27		-* Flow Designer updates
28		-We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
29		-
30		-[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
31		-
32		-* Store
33		-We have fixed several smaller Store import issues to improve the user experience.
34		-
	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.
	14	+
	15	+{{info}}For more information please check out the following microlearnings:
	16	+
	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"]]
	20	+
	21	+Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	22	+{{/info}}
	23	+
	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.
	26	+
	27	+[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
	28	+
	29	+== **Feedback Items** ==
	30	+
	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.
	33	+
	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).
	36	+
	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.
	39	+
	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}}
	41	+
	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.
	44	+
	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.
	47	+
	48	+== **Bug Fixes** ==
	49	+
	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.
	52	+
	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.
	55	+
	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.
	58	+
	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	+
35	35	== **Fancy Forum Answers** ==
36	36
37		-As always, a gentle reminder to all 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:
	64	+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:
38	38
39		-* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
40		-* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||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"]]
41	41
42	42	== **Key takeaways** ==
43	43
44		-Thanks to all that help build, 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:
45	45
46	46	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
47	47	* If you have feedback or ideas for us, talk to the Platypus
...	...	@@ -52,12 +52,11 @@
52	52	* Start thinking about major, minor, and patch
53	53	* Upgrade to the latest build number
54	54	* Keep making great integrations
55		-* Check out the new documentation portal.
56	56
57	57	Let's stay in touch and till next time!
58	58
59	59	{{info}}
60		-~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	87	+~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61	61
62	62	~*~* Indicates a GEN3-only feature.
63	63	{{/info}})))((({{toc/}}))){{/container}}