Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-190 - Fast Forward
	1	+221 - Swift Shift

Author

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

Content

...	...	@@ -1,109 +1,67 @@
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!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
	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.
6	6
7		-== **Queue Browser** ==
	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.
8	8
9		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
	12	+//__Event catalog__//
	13	+For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
10	10
11		-To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture we have added a new feature to our Manage phase called the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
	15	+[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
12	12
13		-To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies of your actual message that pass through the queue from the moment you pressed the Wiretap button.
	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	14
15		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
	23	+[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
16	16
17		-After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
	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".
18	18
19		-* Delete the message from the queue (Explore option)
20		- ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue.
21		-* Clear message from the wiretap queue (Wiretap option)
22		- ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore
23		-* Refresh messages list (both options)
24		- ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25		-* Save as test message
26		- ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality.
27		-* Download
28		- ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
	30	+[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
29	29
30		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
	32	+[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
31	31
32		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
	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.
33	33
34		-== **3rd generation runtime bolstering** ==
	38	+[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
35	35
36		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
	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.
37	37
38		-//__SOAP and REST web services migration, including splitting them__//
39		-With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
	43	+//__Scope properties__//
	44	+We fixed an issue where the generation of scope properties was incorrect for the legacy API gateway runtimes using OAuth 2.0 security scheme.
40	40
41		-//__Changing SSL settings for 3rd generation runtime models works__//
42		-As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
43		-
44		-//__Improved migration for JMS flows__//
45		-This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
46		-
47		-{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
48		-
49		-//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
50		-As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
51		-
52		-//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
53		-We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
54		-
55		-//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
56		-With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
57		-
58		-//__Added "Reset" functionality__//
59		-With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
60		-
61		-== **Feedback items ** ==
62		-
63		-We have also solved other feedback items besides the flow designer's critical updates.
64		-
65		-//__Improved naming convention on Store related pages__//
66		-We have improved various display names using the merge functionality within our store offering.
67		-
68		-//__Update security protocols for our internal architecture__//
69		-Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
70		-
71		-//__Improved read-only description for "if exists" constructions in Transformations__//
72		-To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
73		-
74		-
75		-== **Bug fixes ** ==
76		-
77		-//__Decent validation feedback when not filling in the property value__//
78		-We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
79		-
80		-//__Incorrect resource locations__//
81		-We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
82		-
83		-//__Apply to environment in User Management performance improvement__//
84		-We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
85		-
86	86	== **Fancy Forum Answers** ==
87	87
88	88	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:
89	89
90		-* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
91		-* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
92		-* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
93		-* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
	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"]]
94	94
95		-== **Key takeaways** ==
	54	+== **Key Takeaways** ==
96	96
97		-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:
	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:
98	98
99	99	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
100	100	* If you have feedback or ideas for us, talk to the Platypus
101		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	60	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
102	102	* Clear your browser cache (Ctrl + Shift + Del)
103		-* Check out the release notes [here]
	62	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
104	104	* Start thinking about how the license tracker can aid your development
105	105	* Start thinking about major, minor, and patch
106		-* Upgrade to the latest build number
107	107	* Keep making great integrations
108	108
109	109	Let's stay in touch and till next time!
...	...	@@ -111,6 +111,11 @@
111	111	{{info}}
112	112	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
113	113
114		-~*~* Indicates a GEN3-only feature.
115		-{{/info}})))((({{toc/}}))){{/container}}
	72	+{{/info}}
	73	+)))
	74	+
	75	+(((
	76	+{{toc/}}
	77	+)))
116	116	{{/container}}
	79	+{{/container}}