Skip to Content

Changes for page 239 - Modern Talking

Last modified by Erik Bakker on 2025/02/26 21:08
From version 229.1
edited by Erik Bakker
on 2025/02/25 08:29
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 -239 - Modern Talking
1 +187 - Integration Sponsor
Content
... ... @@ -1,17 +1,25 @@
1 -In the last sprint, we focused on testing the eMagiz Mendix Connector and solving internal feedback on the process and the connector itself. With that behind us we are ready to launch the new eMagiz Mendix Connector to our community. With this release we will make available for all new Mendix systems in models running on the current-generation architecture. Subsequently we will implement a migration wizard aiding a simple and smooth migration to the new eMagiz Mendix Connector. On top of that, we have some minor updates to improve the quality of the platform.
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.239 - Modern Talking.WebHome||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 -* New Mendix connector: We will introduce a new eMagiz Mendix connector. This new connector delivers improved stability and a simpler setup process. The new connector is better integrated in your eMagiz models and will receive full support. The connector can be used for new systems and will be enabled by default for new models.
8 -** A migration wizard will be released later which allows you to easily and smoothly migrate your current legacy Mendix connectors to the new Mendix connector.
12 +=====Minor changes=====
9 9  
10 -====Minor Changes====
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.
11 11  
12 -* Create - Flow Designer: The view button that can be found by navigating to the right panel of the Flow Designer and choosing the Support Objects tab opens a pop-up that shows a list of all support objects that can be added. This button is accessible only in view mode of the Flow Designer. (#870)
13 13  
14 14  ====Bug fixes====
15 -
16 -* Create - Flow Creation: Payload root Qname support object for the API gateway infra is not containing duplicates now. (#1517)
17 -* Manage - Dashboard: The manage phase dashboard no longer breaks when an error occurs in a component with an id that does not follow the [id].[system].[flow] convention, or when that value is longer than expected. (#1566)
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)