Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-189 - Private Eye
	1	+221 - Swift Shift

Author

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

Content

...	...	@@ -1,85 +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!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.
	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		-== **Private Store** ==
8		-On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
	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.
9	9
10		-{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/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.
11	11
12		-== **3rd generation runtime bolstering** ==
	15	+[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
13	13
14		-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.
	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.
15	15
16		-//__SOAP and REST web services migration including splitting them__//
17		-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 and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal.
	23	+[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
18	18
19		-//__Changing SSL settings for 3rd generation runtime models works__//
20		-As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime.
	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".
21	21
22		-//__Improved migration for JMS flows__//
23		-This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
	30	+[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
24	24
25		-{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}}
	32	+[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
26	26
27		-//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28		-As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow.
	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.
29	29
30		-//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31		-We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
	38	+[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
32	32
33		-== **Feedback items ** ==
	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.
34	34
35		-We have also solved other feedback items besides the flow designer's critical updates.
	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.
36	36
37		-//__Improved naming convention on Store related pages__//
38		-We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
39		-
40		-//__Press "Enter" to search on multiple pages__//
41		-In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
42		-
43		-* Deploy → Deployment Plan
44		-* Deploy → Properties → History
45		-* Deploy → User Management → Roles
46		-* Manage → Error Messages → Error Messages
47		-* Manage → Error Messages → Flows with Error Messages
48		-* Manage → Error Messages → Exceptions of Error Messages
49		-* Manage → Log Entries
50		-* Manage → Alerts
51		-* Manage → Triggers
52		-* Manage → Tags – Cant find (only Gen2)
53		-* Manage → Notifications
54		-* Manage → Notification Settings
55		-* Manage → Data Usage → History
56		-* Manage → Code mappings → All tabs
57		-
58		-== **Bug fixes ** ==
59		-
60		-//__Loading problems of Deployment plan execution overview__//
61		-We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
62		-
63	63	== **Fancy Forum Answers** ==
64	64
65	65	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:
66	66
67		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
68		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
69		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||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"]]
70	70
71		-== **Key takeaways** ==
	54	+== **Key Takeaways** ==
72	72
73		-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:
74	74
75	75	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
76	76	* If you have feedback or ideas for us, talk to the Platypus
77		-* 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.
78	78	* Clear your browser cache (Ctrl + Shift + Del)
79		-* Check out the release notes [here]
	62	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
80	80	* Start thinking about how the license tracker can aid your development
81	81	* Start thinking about major, minor, and patch
82		-* Upgrade to the latest build number
83	83	* Keep making great integrations
84	84
85	85	Let's stay in touch and till next time!
...	...	@@ -87,6 +87,11 @@
87	87	{{info}}
88	88	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
89	89
90		-~*~* Indicates a GEN3-only feature.
91		-{{/info}})))((({{toc/}}))){{/container}}
	72	+{{/info}}
	73	+)))
	74	+
	75	+(((
	76	+{{toc/}}
	77	+)))
92	92	{{/container}}
	79	+{{/container}}