Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-199 - Home Improvements
	1	+220 - Patch Parade

Author

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

Content

...	...	@@ -1,62 +1,91 @@
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 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.
	6	+**Hi there, eMagiz developers!**
6	6
7		-== **Next generation improvements and bug fixes** ==
	8	+== **Feedback Items** ==
8	8
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.
	10	+//__Integration pattern information__//
	11	+Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
11	11
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.
	13	+[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
14	14
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}}
	15	+//__Message queue history__//
	16	+All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
16	16
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.
	18	+[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
19	19
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.
	20	+//__Search boxes__//
	21	+Search boxes in the properties overview are now shown by default.
22	22
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.
	23	+[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
25	25
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}}
	25	+//__Set as mapped__//
	26	+It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
27	27
28		-== **Store Improvements** ==
	28	+[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
29	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.
	30	+//__SSL settings__//
	31	+Changes can now be deployed on SSL level without creating a new version of a flow in Create.
32	32
33		-//__Fixed bug in creating a message mapping on top of an imported system message__//
34		-It is now possbile to create a message mapping to an imported system message from the store.
	33	+//__Machine deletion__//
	34	+When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted.
35	35
36		-== **Event Streaming - Certificate Management** ==
	36	+[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
37	37
38		-//__Expired certification notification__//
39		-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]].
	38	+//__JMS header handling__//
	39	+Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new runtime image(LINK) has been released.
40	40
	41	+== **Bug Fixes** ==
	42	+//__Annotation styling__//
	43	+It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
	44	+
	45	+[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
	46	+
	47	+//__Filter rejection warnings__//
	48	+A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
	49	+
	50	+[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
	51	+
	52	+//__Manage Explore__//
	53	+An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
	54	+
	55	+//__Page refreshing__//
	56	+Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
	57	+
	58	+//__Message redelivery__//
	59	+An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page.
	60	+
	61	+//__Deployment plan__//
	62	+We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps.
	63	+
	64	+//__Overview pages__//
	65	+We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase.
	66	+
	67	+//__Memory check__//
	68	+Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines.
	69	+
41	41	== **Fancy Forum Answers** ==
42	42
43	43	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:
44	44
45		-* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
46		-* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
	74	+* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
	75	+* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
	76	+* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
47	47
48		-== **Key takeaways** ==
	78	+== **Key Takeaways** ==
49	49
50		-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:
	80	+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:
51	51
52	52	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53	53	* If you have feedback or ideas for us, talk to the Platypus
54		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	84	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
55	55	* Clear your browser cache (Ctrl + Shift + Del)
56		-* Check out the release notes [here]
	86	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
57	57	* Start thinking about how the license tracker can aid your development
58	58	* Start thinking about major, minor, and patch
59		-* Upgrade to the latest build number
60	60	* Keep making great integrations
61	61
62	62	Let's stay in touch and till next time!
...	...	@@ -64,6 +64,11 @@
64	64	{{info}}
65	65	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66	66
67		-~*~* Indicates a GEN3-only feature.
68		-{{/info}})))((({{toc/}}))){{/container}}
	96	+{{/info}}
	97	+)))
	98	+
	99	+(((
	100	+{{toc/}}
	101	+)))
69	69	{{/container}}
	103	+{{/container}}