Skip to Content

Changes for page 259 - Improve Infinitely

Last modified by Erik Bakker on 2026/01/15 09:27
From version 294.1
edited by Erik Bakker
on 2025/11/19 20:30
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 -257 - DSH Delight
1 +259 - Improve Infinitely
Content
... ... @@ -1,33 +1,21 @@
1 -This release features various updates to our platform, with our new event streaming broker running on DSH taking center stage. With this release, our latest event streaming functionality will be available to everyone (GA). On top of that, we will launch the previously announced new [[runtime image>>doc:Main.Release Information.Runtime Images.V341.WebHome||target="blank"]] for **all** customers. On top of that, we have several smaller features 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>>doc:Main.Release Information.Release Blogs.257 - DSH Delight.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 5  ==== New features ====
6 6  
7 -* General - Event Streaming: The KPN DSH event streaming broker has been set as the default event streaming broker for models that start using event streaming for the first time. Please get in touch with your partner manager about the possibilities of using event streaming in your models.
8 -* General - Runtime Image: A new runtime image is introduced that fixes several issues reported by customers, updates the Java version, and prepares all models for migration to our MAM feature if they are ready.
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 10  ==== Minor changes ====
11 11  
12 -* Event Streaming - Data Retention: When DSH retention time is changed on the company level, deleting the topic by excluding it in Design > Architecture and applying the change in Deploy > Architecture and including it again in Design > Architecture and applying the change in Deploy > Architecture results in the retention time being updated in DSH.
13 -** Note that this action will delete the topic and therefore will result in **data loss**.
14 -* Design - System: Importing an Open Specification V2 has been deprecated, and it’s not supported anymore at eMagiz.
15 -* Design - System Message: Users can go from Design to the Create phase for all message types. (#1607)
16 -* Create - Flow testing: The properties that start with “emagiz.dsh“ are provided with a value automatically in the background.
17 -* Deploy - Releases: In case of activating a new release and there is trouble at the step of creating new certificates, the previous valid certificate will be reused.
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)
18 18  
19 -
20 20  ==== Bug fixes ====
21 21  
22 -* Create - Flow Designer: Users are correctly redirected to their request/response message based on the XSD they are selecting in the flow. (#1555)
23 -* Create - Transformation - Value mappings for a “string to enumeration” transformer are now visible after reopening the window. (#1715)
24 -* Create - System Message: The navigation from Create to Design has been fixed for event streaming. Additionally, improvements have been made for synchronous messaging so that the currently visualized message (request or response) is correctly considered when using the “Open in Design” button.
25 -* Create - Add Integrations: We fixed an issue where, when your model is migrating or migrated to the new Event streaming broker, you get an error message for security reasons, sometimes when you un-transfer integrations from the Create.
26 -* Create - Processes: We fixed an issue where opening an entry or exit connector with multiple integrations of the eMagiz Mendix connector system did not open the correct flow. The flows are now displayed in the same order as the topics in the center panel when you focus on a system. This ensures that when you select a flow, the correct one opens as expected.
27 -* Deploy - Architecture: We have fixed a bug for DSH-enabled event streaming models, which may have prematurely lost read/write access to deleting topics if the topic was still in use in the active release.
28 -* Deploy - Releases: We have fixed a bug for DSH-event streaming-enabled models, where updating one flow connecting to the DSH event streaming broker would result in containers hosting other such flows to be redeployed unintentionally as well.
29 -* Deploy - Unused Properties: Users can select multiple properties across pages and delete the selections all at once. (#1730)
30 -* Manage - Topic Triggers: All DSH topics have topic triggers. Removing topics without a topic trigger does not result in an error.
31 -* Manage - Triggers: Manage phase access rights have been updated to allow users with the proper access to view and edit correctly.
32 -* Manage - Error Messages: Increased the maximum number of displayed error message headers from 40 to 60. (#1309)
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)
33 33