Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-198 - Great Migration
	1	+220 - Patch Parade

Author

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

Content

...	...	@@ -1,53 +1,93 @@
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 the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
	6	+**Hi there, eMagiz developers!** In the last few weeks, we worked hard on solving several feedback items and bug fixes. On top of that, we have release a new runtime image LINK that ensures that Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. Without further ado, let us look at our improvements and bug fixes below.
6	6
7		-== **3rd generation improvements and bug fixes** ==
	8	+== **Feedback Items** ==
8	8
9		-//__"Stop" action when running a hybrid situation is not causing issues anymore__//
10		-Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed.
	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		-{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
	13	+[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
13	13
14		-//__Improved efficiency in deploying a release__//
15		-This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
	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		-//__Removed specific dependencies between Deploy Architecture and Releases__//
18		-In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
	18	+[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
19	19
20		-//__Improved validation errors on the invalid configuration of HTTP outbound components__//
21		-This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
	20	+//__Search boxes__//
	21	+Search boxes in the properties overview are now shown by default.
22	22
23		-//__Improved migration behavior__//
24		-This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
25		-A smoother migration of your JMS (and backup JMS) process.
26		-Shortening of names that otherwise would be too long, additional feedback given to the user.
27		-Feedback when the migration process is finished.
	23	+[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
28	28
29		-//__Additional checks when deploying__//
30		-This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
	25	+//__Set as mapped__//
	26	+It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
31	31
	28	+[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
	29	+
	30	+//__SSL settings__//
	31	+Changes can now be deployed on SSL level without creating a new version of a flow in Create.
	32	+
	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	+
	36	+[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
	37	+
	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	+
	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	+
	70	+//__Copy password__//
	71	+The copy to clipboard button now copies the actual value of passwords instead of the masked value of them.
	72	+
32	32	== **Fancy Forum Answers** ==
33	33
34	34	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:
35	35
36		-* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
37		-* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
	77	+* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
	78	+* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]]
38	38
39		-== **Key takeaways** ==
	80	+== **Key Takeaways** ==
40	40
41		-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	+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:
42	42
43	43	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
44	44	* If you have feedback or ideas for us, talk to the Platypus
45		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	86	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
46	46	* Clear your browser cache (Ctrl + Shift + Del)
47		-* Check out the release notes [here]
	88	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
48	48	* Start thinking about how the license tracker can aid your development
49	49	* Start thinking about major, minor, and patch
50		-* Upgrade to the latest build number
51	51	* Keep making great integrations
52	52
53	53	Let's stay in touch and till next time!
...	...	@@ -55,6 +55,11 @@
55	55	{{info}}
56	56	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57	57
58		-~*~* Indicates a GEN3-only feature.
59		-{{/info}})))((({{toc/}}))){{/container}}
	98	+{{/info}}
	99	+)))
	100	+
	101	+(((
	102	+{{toc/}}
	103	+)))
60	60	{{/container}}
	105	+{{/container}}