Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-222 - Flee Frustration
	1	+199 - Home Improvements

Author

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

Content

...	...	@@ -1,50 +1,59 @@
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!**
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
7	7
8		-== **Feedback Items** ==
9		-//__Cron triggers__//
10		-Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
	7	+== **Next generation improvements and bug fixes** ==
11	11
12		-[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
	9	+//__Enhanced overview of the HTTP Statistics__//
	10	+As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
13	13
14		-//__Design changes__//
15		-If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
	12	+//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
	13	+In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
16	16
17		-== **Bug Fixes** ==
18		-//__Trigger activation__//
19		-Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
	15	+{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
20	20
21		-//__Multiple users deploying__//
22		-Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
	17	+//__Forced congestion control__//
	18	+To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
23	23
24		-[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
	20	+//__Unused images are cleaned up__//
	21	+This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan.
25	25
	23	+//__Improved rollup and storage of metrics when running an event streaming solution__//
	24	+To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
26	26
27		-We have resolved deprecated warnings as part of our preparation to upgrade to Mendix version 10.
	26	+{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of July. From then on, all data before the 9th of June will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
28	28
	28	+== **Store Improvements** ==
	29	+
	30	+//__Improved importing behavior for specific use cases__//
	31	+Before, it could happen that a certain placeholder that contained an asterisk (*) were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users.
	32	+
	33	+== **Event Streaming - Certificate Management** ==
	34	+
	35	+//__Expired certification notification__//
	36	+As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	37	+
29	29	== **Fancy Forum Answers** ==
30	30
31	31	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:
32	32
33		-* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
34		-* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
35		-* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
	42	+* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
	43	+* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
36	36
37		-== **Key Takeaways** ==
	45	+== **Key takeaways** ==
38	38
39		-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:
	47	+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:
40	40
41	41	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
42	42	* If you have feedback or ideas for us, talk to the Platypus
43		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	51	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
44	44	* Clear your browser cache (Ctrl + Shift + Del)
45		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
	53	+* Check out the release notes [here]
46	46	* Start thinking about how the license tracker can aid your development
47	47	* Start thinking about major, minor, and patch
	56	+* Upgrade to the latest build number
48	48	* Keep making great integrations
49	49
50	50	Let's stay in touch and till next time!
...	...	@@ -52,11 +52,6 @@
52	52	{{info}}
53	53	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
54	54
55		-{{/info}}
56		-)))
57		-
58		-(((
59		-{{toc/}}
60		-)))
	64	+~*~* Indicates a GEN3-only feature.
	65	+{{/info}})))((({{toc/}}))){{/container}}
61	61	{{/container}}
62		-{{/container}}