Changes for page 202 - New Equilibrium

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-194 - Giant Leap
	1	+202 - New Equilibrium

Author

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

Content

...	...	@@ -1,68 +1,74 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** In the last few weeks, we have worked around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.
	6	+**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 smaller feedback items from our hackathon efforts that are now released to you.
6	6
7		-== **3rd generation improvements** ==
	8	+== **Release Properties** ==
8	8
9		-//__Better feedback in the error log when a corrupt stylesheet is encountered__//
10		-We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
	10	+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, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are:
11	11
12		-//__Better internal error handling to avoid unnecessary alerting and notifications__//
13		-We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the alerts you receive on this topic when your model runs on the 3rd generation monitoring stack.
	12	+* 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
	13	+* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration.
	14	+* 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.
	15	+* 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 an entirely new release in Test and promote it to the Production environment.
14	14
15		-//__Improved Manage Dashboard__//
16		-This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime architecture.
	17	+{{info}}
	18	+For more information, please check out the following microlearnings:
17	17
18		-//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19		-When a slot is put into standby mode, we also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. The opposite happens when the slot wakeup is triggered. As a result, not only the cloud runtimes are started but also all on-premise runtimes.
	20	+* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
	21	+* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
	22	+* [[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	20
21		-//__Improved process of deploy preparation__//
22		-With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced.
	24	+Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	25	+{{/info}}
23	23
24		-//__Improved migration of Streaming container__//
25		-When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention.
	27	+== ** Manage - Graphs improvements ~*~* ** ==
26	26
27		-//__Add History to Notifications in Manage__//
28		-To improve the auditability of our platform, we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way, it is always visible when the notifications were paused and who paused or unpaused the notifications.
	29	+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 managed graphs as we retrieve and show less fine-grained information when zooming out.
29	29
30		-//__Improved Manage phase for Event Streaming__//
31		-Based on the feedback on our first iteration of the Manage phase for Event Streaming, we have improved the graphs and the calculations that fill the graphs with values. On top of that, we have added help texts to clarify what each chart our table displays to you.
	31	+[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
32	32
33		-//__Improved help text for network volumes__//
34		-With this release, we have improved the help text that explains network volumes and how to use them within our solution.
	33	+== **Feedback Items** ==
35	35
36		-{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
	35	+//__Improved editability when testing in eMagiz without Edit rights in Create__//
	36	+Without editing 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 should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.
37	37
38		-== **Feedback items ** ==
	38	+//__Improved auditability on Deploy Architecture__//
	39	+To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).
39	39
40		-//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41		-With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
	41	+//__Test your own exported store content__//
	42	+We have now allowed testing of your 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.
42	42
43		-//__User Roles are sorted alphabetically__//
44		-All user roles under User Management are now also sorted alphabetically.
	44	+{{info}}
	45	+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"]]
	46	+{{/info}}
45	45
46		-//__Name of keystore for user management now includes the environment__//
47		-To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename.
	48	+//__Improved comparison of flows in the releases overview__//
	49	+We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
48	48
49		-== **Bug fixes ** ==
	51	+== **Bug Fixes** ==
50	50
51		-//__Consolidated upgrade process cloud template__//
52		-With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud.
	53	+//__Improved validation on XPath header enricher__//
	54	+To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
53	53
54		-//__Ensure users can deploy release on environments they have edit rights on__//
55		-Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so.
	56	+//__Cancel behavior on flow testing property overview fixed__//
	57	+We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.
56	56
	59	+//__Cancel behavior on flow fragment level when exporting store content__//
	60	+We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
	61	+
	62	+//__Adding numbers on containers in Deploy Architecture__//
	63	+With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.
	64	+
57	57	== **Fancy Forum Answers** ==
58	58
59	59	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:
60	60
61		-* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
62		-* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
63		-* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
	69	+* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
64	64
65		-== **Key takeaways** ==
	71	+== **Key Takeaways** ==
66	66
67	67	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:
68	68
...	...	@@ -70,7 +70,7 @@
70	70	* If you have feedback or ideas for us, talk to the Platypus
71	71	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
72	72	* Clear your browser cache (Ctrl + Shift + Del)
73		-* Check out the release notes [here]
	79	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.202 - New Equilibrium.WebHome||target="blank"]]
74	74	* Start thinking about how the license tracker can aid your development
75	75	* Start thinking about major, minor, and patch
76	76	* Upgrade to the latest build number
...	...	@@ -81,6 +81,12 @@
81	81	{{info}}
82	82	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83	83
84		-~*~* Indicates a GEN3-only feature.
85		-{{/info}})))((({{toc/}}))){{/container}}
	90	+~*~* Indicates a next-generation-architecture only feature.
	91	+{{/info}}
	92	+)))
	93	+
	94	+(((
	95	+{{toc/}}
	96	+)))
86	86	{{/container}}
	98	+{{/container}}