Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-222 - Flee Frustration
	1	+221 - Swift Shift

Content

...	...	@@ -3,23 +3,46 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!**
	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.
7	7
8	8	== **Feedback Items** ==
9		-//__Trigger activation__//
10		-Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
	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		-[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
	12	+//__Event catalog__//
	13	+For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
13	13
	15	+[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
	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	+* 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.
	22	+
	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	+
14	14	== **Bug Fixes** ==
15		-//__Trigger activation__//
16		-Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
	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.
17	17
18		-//__Trigger activation__//
19		-Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
	38	+[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
20	20
21		-[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
	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.
22	22
	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	+
23	23	== **Fancy Forum Answers** ==
24	24
25	25	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: