Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 532.1
edited by Carlijn Kokkeler
on 2024/05/22 11:23
Change comment: There is no comment for this version
To version 531.1
edited by Carlijn Kokkeler
on 2024/05/21 12:56
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!** 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 +**Hi there, eMagiz developers!** This release, we have done several improvements for failover and grouping, as well as for the placement of attributes in datamodels. Next to this, we have improved the Event Catalog overview for Catalog users. It is now also possible to use the back button on the eMagiz Q&A without your search being removed. Regarding bug fixes, the delete behaviour for containers has been improved, and scope properties will now be generated correctly. Lastly, the warning message that is given when importing an xsd has now been removed when the request or response message is empty.
7 7  
8 8  == **Feedback Items** ==
9 9  //__Q&A search__//
... ... @@ -17,7 +17,7 @@
17 17  //__Attribute placements__//
18 18  Some improvements regarding the placement of attributes have been done:
19 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.
20 +* Moving an attribute in the datamodel is now directly shown in the tree structure as well.
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 XSD to a new or empty response or request message, you will not receive a warning message anymore to avoid confusion.
36 +When importing an xsd to a new 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