Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 527.1
edited by Carlijn Kokkeler
on 2024/05/21 11:46
on 2024/05/21 11:46
Change comment:
There is no comment for this version
To version 532.1
edited by Carlijn Kokkeler
on 2024/05/22 11:23
on 2024/05/22 11:23
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
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,8 +16,8 @@ 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 directlyshown 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]] ... ... @@ -33,7 +33,7 @@ 33 33 34 34 == **Bug Fixes** == 35 35 //__XSD import__// 36 -When importing an xsdto 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. 37 37 38 38 [[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]] 39 39 ... ... @@ -41,7 +41,7 @@ 41 41 The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows. 42 42 43 43 //__Scope properties__// 44 -We fixed an issue where the generation of scope properties was incorrect for thelegacy API gateway runtimes using OAuth 2.0 security scheme.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 45 46 46 == **Fancy Forum Answers** == 47 47 ... ... @@ -59,7 +59,7 @@ 59 59 * If you have feedback or ideas for us, talk to the Platypus 60 60 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 61 61 * Clear your browser cache (Ctrl + Shift + Del) 62 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.22 0-PatchParade.WebHome||target="blank"]]62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]] 63 63 * Start thinking about how the license tracker can aid your development 64 64 * Start thinking about major, minor, and patch 65 65 * Keep making great integrations