Skip to Content

Changes for page 259 - Improve Infinitely

Last modified by Erik Bakker on 2026/01/15 09:27
From version 227.1
edited by Erik Bakker
on 2025/02/10 09:31
Change comment: There is no comment for this version
To version 301.1
edited by Erik Bakker
on 2026/01/15 09:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -238 - Preparation Paraside
1 +259 - Improve Infinitely
Content
... ... @@ -1,12 +1,21 @@
1 -In the last sprint, we focused on finishing the first iteration of our new eMagiz Mendix Connector and the first iteration of our new base image. We will first utilize the new eMagiz Mendix Connector to get an even better feeling of its performance, but you will notice a UI change straightaway. Once we have passed that hurdle, we will share more information about it and release it to a broader range of customers. Regarding the base image, we will now introduce this to our flow testing offering to see if anything unexpected happens. This is an additional safety measure we have put in place to reduce the chance of something breaking in your model once the new base image is released. On top of that, we have some minor updates to improve the quality of the platform.
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.238 - Preparation Paradise.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 -====Minor Changes====
5 +==== New features ====
6 6  
7 -* ILM: We defined the systems labeled as “isMendix” with the “MX“ icon, making it easier to identify the Mendix system.
8 -* Create - Flow Testing: As we are finalizing the new eMagiz runtime image that will update the Spring version to Spring boot 3.4.1 and Java to 17.0.13, we are now bringing these latest updates to flow testing. This means that any flow test you execute will run on the base image your runtimes will run on after the release of the new eMagiz runtime image. If one of your test cases suddenly exhibits weird behavior that you think is due to the update, feel free to contact us via our [[support department>>mailto:support@emagiz.com]].
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 -====Bug fixes====
9 +==== Minor changes ====
11 11  
12 -* Create - Add Integrations: Integrations using the entry/exit connector, using the same message type, can now be untransferred from the create phase. (#1591)
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)
13 +
14 +==== Bug fixes ====
15 +
16 +* Create - Transformation: The content section of the XSLT snippet is converted to an XML editor to beautify the field. (#1739)
17 +* Create - Flow Designer: Validation feedback is visualised on the flat file field right before the save action to provide clarity to the user. (#891)
18 +* Create - Flow Designer: 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 +