Skip to Content

Changes for page 259 - Improve Infinitely

Last modified by Erik Bakker on 2026/01/15 09:27
From version 248.1
edited by Erik Bakker
on 2025/04/22 14:08
Change comment: There is no comment for this version
To version 300.1
edited by Erik Bakker
on 2026/01/15 09:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -243 - Migration Magic
1 +259 - Improve Infinitely
Content
... ... @@ -1,30 +1,21 @@
1 -In the last sprint, we released our migration wizard for the new eMagiz connector. This wizard will guide you through the process of migrating the existing eMagiz connector within Mendix to our latest version, which is packed with improvements. Furthermore, we will release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V331.WebHome||target="blank"]] that corrects some changes and improves the UI/UX of loads of data grids across the platform. In addition, we have various smaller changes and bug fixes for you to enjoy.
1 +This release features various updates to our platform, just after the holiday season. Apart from various more minor improvements, we have also launched a new [[runtime image>>doc:Main.Release Information.Runtime Images.V350.WebHome||target="blank"]] for **all** customers.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.243 - Migration Magic.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.259 - Improve Infinitely.WebHome||target="blank"]].
4 4  
5 -====New Features====
5 +==== New features ====
6 6  
7 -* eMagiz Connector - Migration: We have implemented a migration wizard that allows you to migrate to the new eMagiz Connector. You can start this wizard via Deploy -> Mendix connectors on a system-by-system basis.
8 -** Migrating eMagiz connector flows to the new version will remove the history of the old versions from the history tab. Make sure you copy this information if you want to archive it. After migrating your flows, this will no longer be visible.
7 +* General - Runtime Image: Maintenance update where we primarily updated Spring Boot from version 3.4.1 to 3.5.8 and ensured all our external libraries are up-to-date.
9 9  
10 -====Minor Changes====
9 +==== Minor changes ====
11 11  
12 -* General - Event Streaming: We have updated our event streaming infrastructure.
13 -* General - Datagrids: We have updated a lot of our data grids to reflect the latest changes available
14 -** ‘Double click’ action on data grid rows is introduced to the newer datagrid format and, where possible, configured as such. Since older grids will be gradually replaced, this update allows for the maintainability of the behavior you are used to.
15 -** Unfortunately, The above change resulted in a behavior shift when selecting one or multiple rows in a grid (for example, in the trigger overview). Previously, clicking on the whole row resulted in the selection of the row. Now only checking the checkbox results in a row selection.
16 -* Create - Transformation: In the Transformation tab of the Create phase, conditional operators can be added for transformations that have multiple attributes as a source. (#1272)
17 -* Deploy - Machine: We have updated the default network deployment strategy for Windows machines, which might affect your machines. When you access the Deploy phase, you will see the list of machines required for redeployment. Redeploying your machine will ensure you benefit from these enhanced network capabilities.
18 -* Deploy - History: Deploy releases history tab better renders the information on the screen.
19 -** Additionally, we have updated the "Export to Excel" button to reflect the latest functionality. As a result, there is no longer a limit to how many rows can be exported. (#1601)
20 -* Deploy - General: We have implemented performance improvements to the Deploy phase. The larger the model, the more notable the improvements.
21 -* eMagiz Connector - General: We released a new patch version of the eMagizConnector in the Mendix marketplace. It includes some small changes to the naming conventions to remove the ACR violations.
11 +* Create - Flow Designer: Selector expression is added on the channel interceptors page. (#1738)
12 +* Manage - Error Messages: Search by complete flow name functionality is added to the flows with error messages page. Additionally, the grid is updated to improve the page's appearance. (#1738)
22 22  
23 -====Bug fixes====
14 +==== Bug fixes ====
24 24  
25 -* Design - System Message: Using the "save and create new attribute" button in the system message tab of the design phase will not open a "new attribute" window until the previous attribute’s details are properly entered and saved. (#1650)
26 -* Create - Transformation: Help text appears for relevant attributes when creating a new transformer in the transformation tab of the create phase. (#1352)
27 -* Catalog - General: The content inside the “used by integrations” table for the topic catalog is properly rendered to be more readable for systems with longer names. The title represents the content of the table. (#1224)
28 -* Create - Transformation: Date/time transformer pop-ups in the Transformation tab of the Create phase are rendered in a format that allows editing when in edit mode. (#1642)
29 -* Infra - Runtime Image: Support for the ‘NTCredentials’ authentication method in a custom HttpComponentsMessageSender support object has been reintroduced.
30 -* Infra - Runtime Image: In some edge cases, log messages produced with the Logging channel adapter component did not end up in the Manage phase. This issue is now resolved.
16 +* Create - Transformation: The content section of the XSLT snippet is converted to an XML editor to beautify the field. (#1739)
17 +* Create - Transformation: Validation feedback is visualised on the flat file field right before the save action to provide clarity to the user. (#891)
18 +* Create - Transformation: The same display name was being used for two similar support objects, which caused confusion. The incorrectly labeled object has now been renamed. The second "Byte array length header (de)serializer" has been renamed to "ByteArrayRawSerializer". (#1751)
19 +* Deploy - Known Hosts String: When you create a new property and select the drop-down called “Data type”, choose the option called “Known hosting string”. Behind the “Value” field, a cog wheel appears. It leads you to a pop-up. In this pop-up, the Host and Port fields have been swapped. We did it because this ordering aligns with the common defaults used across IT systems. (#1749)
20 +* Monitoring - Runtimes: two graphs, namely “Problematic runtimes memory usage” and “Max memory usage”, are fixed and show correct information. (#1654)
21 +