Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 523.1
edited by Carlijn Kokkeler
on 2024/05/21 11:29
Change comment: There is no comment for this version
To version 534.1
edited by Carlijn Kokkeler
on 2024/05/29 10:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,7 +3,7 @@
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 9  //__Q&A search__//
... ... @@ -16,27 +16,40 @@
16 16  
17 17  //__Attribute placements__//
18 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.
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 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 22  
23 23  [[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
24 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 +
25 25  == **Bug Fixes** ==
26 26  //__XSD import__//
27 -When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion.
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.
28 28  
29 29  [[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
30 30  
31 -//__XSD import__//
40 +//__Container deletion__//
32 32  The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
33 33  
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 +
34 34  == **Fancy Forum Answers** ==
35 35  
36 36  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:
37 37  
38 -* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
39 -* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||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"]]
40 40  
41 41  == **Key Takeaways** ==
42 42  
... ... @@ -46,7 +46,7 @@
46 46  * If you have feedback or ideas for us, talk to the Platypus
47 47  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
48 48  * Clear your browser cache (Ctrl + Shift + Del)
49 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
50 50  * Start thinking about how the license tracker can aid your development
51 51  * Start thinking about major, minor, and patch
52 52  * Keep making great integrations