Skip to Content

Changes for page 263 - User Update

Last modified by Erik Bakker on 2026/03/10 12:40
From version 320.1
edited by Erik Bakker
on 2026/03/09 13:25
Change comment: There is no comment for this version
To version 232.1
edited by Erik Bakker
on 2025/02/26 21:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -263 - User Update
1 +239 - Modern Talking
Content
... ... @@ -1,20 +1,18 @@
1 -This release includes many user-driven updates to our platform to enhance your everyday work.
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 in our community. With this release, we will make it available for all new Mendix systems in models running on the current-generation architecture. In a future release, we will bring 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.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.263 - User Update.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.239 - Modern Talking.WebHome||target="blank"]].
4 4  
5 -==== Minor changes ====
5 +====New Features====
6 6  
7 -* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers is available.
8 -* 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)
7 +* New Mendix connector: We will introduce a new eMagiz Mendix connector. This new connector delivers improved stability and a simpler setup process. It is better integrated into 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, allowing you to quickly and smoothly migrate your legacy Mendix connectors to the new Mendix connector.
9 +** We will publish the new module to the Mendix Marketplace on **February 28.**
9 9  
10 -==== Bug fixes ====
11 +====Minor Changes====
11 11  
12 -* Deploy - Deployment plan execution: The failure message shown during release preparation has been improved to be more descriptive. (#1568)
13 -* 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)
14 -* Manage - Explore - Topic browser: We fixed two problems with the topic browser.
15 -** 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)
16 -** The first page of messages on a topic’s partition will now include the last message, with offset 1 below the ‘last offset’.
17 -* 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)
18 -==== Remarks ====
13 +* 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 the view mode of the Flow Designer. (#870)
19 19  
20 -* General - Portal: We have removed part of our platform's functionality as it was not used anymore.
15 +====Bug fixes====
16 +
17 +* Create - Flow Creation: When creating the corresponding infra and entry flows belonging to a system that will host a SOAP endpoint, we fixed a bug causing two support objects to break upon creation. (#1517)
18 +* Manage - Dashboard: The manage phase dashboard no longer breaks when an error occurs in a component with an id that does not follow the {{code}}[id].[system].[flow]{{/code}} convention, or when that value is longer than expected. (#1566)