Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 263.1
edited by Erik Bakker
on 2025/06/17 09:10
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 -247 - Help Out
1 +187 - Integration Sponsor
Content
... ... @@ -1,12 +1,25 @@
1 -This release focuses on helping our community by improving various aspects of our platform in anticipation of some of the larger features that are just around the corner. So, without further ado, let's take a look at what's on the menu today!
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.247 - Help Out.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 -==== Bug fixes ====
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 -* Design - Architecture: A change is made to ensure that the "Design architecture" is correctly updated based on message type changes in the Capture phase. (#1614)
8 -* Create - Flow designer: New help text is generated for the “SOAP entry connector” check box. The check box is present in the "Design phase" while editing the system. (#1413)
9 -* Create - Flow designer: On the "File item reader message source," various help texts have been added to give additional clarity on what the component does. (#1463)
10 -* Create - Flow Designer: Resetting a flow and deploying the changes from the reset flow is corrected so that the flow is deployed with the correct flow version and component list. (#1618)
11 -* Deploy - Architecture: Deploy architecture for displaying the retention bytes is aligned with the Design architecture. It shows the topic retention bytes, as users are only allowed to modify this variable. (#1358)
12 -* Manage - Explore (Queue Browser): The bug is fixed so that all the options within the explore section of the Manage phase are responsive at all times. (#1524)
12 +=====Minor changes=====
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.
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)