Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-203 - Fast Paced
	1	+221 - Swift Shift

Author

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

Content

...	...	@@ -1,49 +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!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
	6	+**Hi there, eMagiz developers!** In this release, we improved the user interface for managing your failover and grouping configurations and improved the method for adding new attributes to data models. Next to this, we have improved the Event Catalog overview for Catalog users. Using the back button on the eMagiz Q&A now also brings you back to where you were with your search query. We also fixed some previous bugs, resulting in improved delete behavior for containers and correctly generated scope properties. Lastly, there will not be a warning message anymore when importing an XSD if there is no selected request or response message definition.
6	6
7		-== **Release Properties - Early Feedback** ==
8		-The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
9		-
10	10	== **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.
11	11
12		-//__"All entries" are now cleaned up as part of the migration__//
13		-To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
	12	+//__Event catalog__//
	13	+For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
14	14
15		-//__Trigger ID added to our alerting on the next-generation architecture__//
16		-We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
	15	+[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
17	17
18		-//__Improved performance Manage Dashboards__//
19		-We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture.
	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	+* For system message definition, moving an attribute in the data model is now directly reflected in the tree structure as well. However for CDM, API Gateway, and EVS Data Model, moving an attribute will not be directly reflected in the tree structure. A pop-up confirmation, as shown below, will appear with respect to the type of message definition (i.e., system message or CDM) that the user is working with.
	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.
20	20
	23	+[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
	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".
	29	+
	30	+[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
	31	+
	32	+[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
	33	+
21	21	== **Bug Fixes** ==
	35	+//__XSD import__//
	36	+When importing an XSD to a new or empty response or request message, you will not receive a warning message anymore to avoid confusion.
22	22
23		-//__Ensure no flow can be in a release twice__//
24		-We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
	38	+[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
25	25
26		-//__Ensure no flow can be in a release twice__//
27		-We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
	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.
28	28
	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	+
29	29	== **Fancy Forum Answers** ==
30	30
31	31	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:
32	32
33		-* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||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"]]
34	34
35		-== **Key takeaways** ==
	54	+== **Key Takeaways** ==
36	36
37		-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:
38	38
39	39	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
40	40	* If you have feedback or ideas for us, talk to the Platypus
41		-* 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.
42	42	* Clear your browser cache (Ctrl + Shift + Del)
43		-* Check out the release notes [here]
	62	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
44	44	* Start thinking about how the license tracker can aid your development
45	45	* Start thinking about major, minor, and patch
46		-* Upgrade to the latest build number
47	47	* Keep making great integrations
48	48
49	49	Let's stay in touch and till next time!
...	...	@@ -51,6 +51,11 @@
51	51	{{info}}
52	52	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53	53
54		-~*~* Indicates a next-generation-architecture only feature.
55		-{{/info}})))((({{toc/}}))){{/container}}
	72	+{{/info}}
	73	+)))
	74	+
	75	+(((
	76	+{{toc/}}
	77	+)))
56	56	{{/container}}
	79	+{{/container}}