Changes for page 263 - User Update
Last modified by Erik Bakker on 2026/03/10 12:40
From version 17.1
edited by Erik Bakker
on 2022/11/08 08:30
on 2022/11/08 08:30
Change comment:
There is no comment for this version
To version 321.1
edited by Erik Bakker
on 2026/03/10 12:40
on 2026/03/10 12:40
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 187-IntegrationSponsor1 +263 - User Update - Content
-
... ... @@ -1,25 +1,19 @@ 1 -Th ereleasebrings the next step of the Design store to the publicandreleasesanewversion of theeMagiz Mendix Connector that unlocksthoseusing it to migrate tothe next generationruntime.Ontopof that, wehaveseveralfeedbackitems and bug fixes.1 +This release includes many user-driven updates to our platform to enhance your everyday work. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 187-IntegrationSponsor Switch.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.263 - User Update.WebHome||target="blank"]]. 4 4 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. 5 +==== Minor changes ==== 11 11 12 - =====Minor changes=====7 +* Create - Flow Designer: Improved the help text of the advanced ‘Match value’ attribute of the XPath filter, so it is clear how this option of the XPath filter can be used. (#1542) 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. 9 +==== Bug fixes ==== 17 17 11 +* Deploy - Deployment plan execution: The failure message shown during release preparation has been improved to be more descriptive. (#1568) 12 +* Deploy - Releases: We fixed an issue where the UI of the Create phase and Deploy phase were not aligned since the Releases screen did not show the new additions, but you can find them in the Release details popup. (#1675) 13 +* Manage - Explore - Topic browser: We fixed two problems with the topic browser. 14 +** When navigating to the last page of messages on a topic’s partition, the amount of messages shown in the paging will now correspond to the number of messages on that partition (#1714) 15 +** The first page of messages on a topic’s partition will now include the last message, with offset 1 below the ‘last offset’. 16 +* Manage - Export - Data sink: When opening this page on an empty data sink bucket, there will be a warning on top of the page (“no results found”). (#1096) 17 +==== Remarks ==== 18 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) 19 +* General - Portal: We have removed part of our platform's functionality as it was not used anymore.