Skip to Content

Changes for page 189 - Private Eye

Last modified by Carlijn Kokkeler on 2024/05/22 13:43
From version 18.1
edited by Erik Bakker
on 2022/11/08 08:30
Change comment: There is no comment for this version
To version 23.1
edited by Erik Bakker
on 2022/11/21 13:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +188 - Close Encounters
Content
... ... @@ -1,25 +1,25 @@
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.
1 +The release brings several improvements to our 3rd generation runtime and the interaction with it. 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.187 - Integration Sponsor.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.WebHome||target="blank"]].
4 4  
5 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 +* Design - Store: It is now possible to import Transformations and Data Models from the store into a model.
7 +** The Design Store can also be opened from the Mapping and Data Model screens.
8 +** The Design Store now offers search options for store items, including Transformations and Data Models.
9 +** When importing a Store item with a Transformation 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 easier installation of multiple Store items with the same data model.
11 11  
12 12  =====Minor changes=====
13 13  
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.
14 +* Create - Flow Designer: Code mapping is now available for models migrating to the 3rd generation runtime
15 +* Create - eMagiz Mendix Connector exit: Download buttons are added for non-legacy eMagiz Mendix connectors.
16 +* Create - Overview: You will now see your errors within a flow but on the Create - Overview. To activate this, open 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 17  
18 18  
19 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)
20 +* Design - Store: Importing store items from response messages doesn't cause issues anymore.
21 +* Design - Store: Importing response messages and transformation to API integration is possible.
22 +* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document. (#783)
23 +* Create - Flow Designer: Ensure that the copy and pasting experience works for all flows.
24 +* Create - Flow Designer - Store: We fixed the maintaining selection of flow fragments from the store.
25 +* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed. (#744)