Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 534.1
edited by Carlijn Kokkeler
on 2024/05/29 10:51
on 2024/05/29 10:51
Change comment:
There is no comment for this version
To version 530.1
edited by Carlijn Kokkeler
on 2024/05/21 12:11
on 2024/05/21 12:11
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!** In this release, weimprovedtheuser interfaceforanagingyour failover and groupingconfigurations andimprovedthe methodforadding new attributestodataUsingthe back button on the eMagiz Q&Anowalso brings you backto where youwere withyour searchquery.Wealsofixedsomepreviousbugs,resultingin improveddelete behavior for containers and correctlygeneratedscope properties. Lastly, therewill not beawarning message anymore when importing anXSDif there is noselected request or response messagedefinition.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 datareflected in the treestructure as well. However for CDM, API Gateway, andEVS Data Model, movingan attribute will not be directly reflected in the tree structure.A pop-up confirmation, asshown 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 XSDto a newormpty 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 ... ... @@ -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 1-SwiftShift.WebHome||target="blank"]]62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.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