Changes for page 263 - User Update

Last modified by Erik Bakker on 2026/03/10 12:40

From version 227.2
edited by Erik Bakker
on 2025/02/10 09:33
Change comment: Update document after refactoring.
To version 320.1
edited by Erik Bakker
on 2026/03/09 13:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -238 - Preparation Paradise
1 +263 - User Update
Content
... ... @@ -1,12 +1,20 @@
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 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.238 - Preparation Paradise.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 -====Minor Changes====
5 +==== Minor changes ====
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: 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)
9 9  
10 -====Bug fixes====
10 +==== Bug fixes ====
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)
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 ====
19 +
20 +* General - Portal: We have removed part of our platform's functionality as it was not used anymore.