Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-221 - Swift Shift
	1	+198 - Great Migration

Author

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

Content

...	...	@@ -1,67 +1,53 @@
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!** This release, we have done several improvements for failover and grouping, as well as for the placement of attributes in datamodels. Next to this, we have improved the Event Catalog overview for Catalog users. It is now also possible to use the back button on the eMagiz Q&A without your search being removed. Regarding bug fixes, the delete behaviour for containers has been improved, and scope properties will now be generated correctly. Lastly, the warning message that is given when importing an xsd has now been removed when the request or response message is empty.
	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.
7	7
8		-== **Feedback Items** ==
9		-//__Q&A search__//
10		-Search results are now persisted when pressing the back button after opening a question in the community Q & A.
	7	+== **3rd generation improvements and bug fixes** ==
11	11
12		-//__Event catalog__//
13		-For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
	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.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
	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}}
16	16
17		-//__Attribute placements__//
18		-Some improvements regarding the placement of attributes have been done:
19		-* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute.
20		-* Moving an attribute in the datamodel is now directly shown in the tree structure as well.
21		-* The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype.
	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.
22	22
23		-[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
	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.
24	24
25		-//__Failover & grouping__//
26		-Some improvements regarding the widgets for failover and grouping have been done:
27		-* When executing a start/stop action on a group, the description of the step now contains the name of the group.
28		-* When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
	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.
29	29
30		-[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
	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.
31	31
32		-[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
	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.
33	33
34		-== **Bug Fixes** ==
35		-//__XSD import__//
36		-When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion.
37		-
38		-[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
39		-
40		-//__Container deletion__//
41		-The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
42		-
43		-//__Scope properties__//
44		-We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.
45		-
46	46	== **Fancy Forum Answers** ==
47	47
48	48	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:
49	49
50		-* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
51		-* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
52		-* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
	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"]]
53	53
54		-== **Key Takeaways** ==
	39	+== **Key takeaways** ==
55	55
56		-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:
	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:
57	57
58	58	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
59	59	* If you have feedback or ideas for us, talk to the Platypus
60		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	45	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
61	61	* Clear your browser cache (Ctrl + Shift + Del)
62		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
	47	+* Check out the release notes [here]
63	63	* Start thinking about how the license tracker can aid your development
64	64	* Start thinking about major, minor, and patch
	50	+* Upgrade to the latest build number
65	65	* Keep making great integrations
66	66
67	67	Let's stay in touch and till next time!
...	...	@@ -69,11 +69,6 @@
69	69	{{info}}
70	70	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
71	71
72		-{{/info}}
73		-)))
74		-
75		-(((
76		-{{toc/}}
77		-)))
	58	+~*~* Indicates a GEN3-only feature.
	59	+{{/info}})))((({{toc/}}))){{/container}}
78	78	{{/container}}
79		-{{/container}}