Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 247.1
edited by Carlijn Kokkeler
on 2024/05/21 12:11
Change comment: There is no comment for this version
To version 18.1
edited by Erik Bakker
on 2022/11/08 08:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +187 - Integration Sponsor
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,18 +1,25 @@
1 -In the last sprint cycle, we have worked on .
1 +The release brings the next step of the Design store to the public and releases a new version of the eMagiz Mendix Connector that unlocks those using it to migrate to the next generation runtime. On top of that, we have several feedback items and bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.221 - Swift Shift||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.187 - Integration Sponsor.WebHome||target="blank"]].
4 4  
5 -===== New features =====
5 +=====New features=====
6 +* Design - Store: It is now possible to import Transformations and Data Models from the Store into a model.
7 +** The Design Store can now be opened from the Mapping and Data Model screens as well.
8 +** The Design Store now offers search options to find store items that include Transformations and/or Data Models.
9 +** When importing a Store item with a Transformation and/or Data Model a new merge tool is available to link the Store Items data model to the users data model or to add new attributes/entities to the user data model.
10 +** When importing a Store item with a data model that has been previously linked the links are automatically restored allowing for easy updating of store based Integrations and for easier installation of multiple Store items with the same data model.
6 6  
7 -* Q & A: Search results are now persisted when pressing the back button after opening a question in the community Q & A. (#1324)
8 -* Catalog: We have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
9 -* Design - CDM/System message: A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. (#151)
10 -* Design - System message: Moving an attribute in the datamodel is now directly shown in the tree structure as well. (#151)
11 -* Design - CDM/API Data model/ES data model and system message: 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. (#151)
12 -* Deploy - Deploy release: When executing a start/stop action on a group, the description of the step now contains the name of the group.
13 -* Deploy - Architecture: 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".
12 +=====Minor changes=====
14 14  
15 -===== Bug fixes =====
16 -* Design - System messages: When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. (#140)
17 -* Deploy - Containers: The delete behaviour of containers in the container overview has been improved. (#1053)
18 -* Deploy - API Gateway: We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.
14 +* Create - Flow designer: Improved the help texts of the Kafka components to better explain certain performance and load-balancing considerations, and added detailed information how messages (including headers) are converted to/from Kafka records.
15 +* Create - eMagiz Mendix Connector exit: Download buttons are added for non legacy eMagiz Mendix connectors
16 +* Create - Overview: You will now be able to see the errors that you have within a flow but on the integration widget. To do this, go into your flow and the number of errors you have in it, if any, will update so that next time you don’t have to navigate inside the flow to check how many alerts you have.
17 +
18 +
19 +====Bug fixes====
20 +* Design - Store: Importing store item from response messages doesn't cause issues anymore
21 +* Design - Store: Importing response message and transformation to Api integration is possible
22 +* Design - API Gateway: The order of attributes in gateway messages were not always the same as the order in the generated Open API document.
23 +* Create - Flow Designer: Fix bugs when copy and paste components in G3 configuration
24 +* Create - Flow designer - Store: We fixed the maintaining selection of flow flagment from Store.
25 +* Manage - Exceptions of error messages: The count of error messages per exception class are now displayed (#744)