Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 536.1
edited by Carlijn Kokkeler
on 2024/06/03 12:15
Change comment: There is no comment for this version
To version 526.1
edited by Carlijn Kokkeler
on 2024/05/21 11:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -222 - Flee Frustration
1 +221 - Swift Shift
Content
... ... @@ -3,30 +3,52 @@
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!**
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-users-deploying.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 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.
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 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.
20 -
38 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
21 21  
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 the 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:
26 26  
27 -* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
28 -* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
29 -* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
50 +* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
51 +* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]]
30 30  
31 31  == **Key Takeaways** ==
32 32  
... ... @@ -36,7 +36,7 @@
36 36  * If you have feedback or ideas for us, talk to the Platypus
37 37  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
38 38  * Clear your browser cache (Ctrl + Shift + Del)
39 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
61 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
40 40  * Start thinking about how the license tracker can aid your development
41 41  * Start thinking about major, minor, and patch
42 42  * Keep making great integrations