Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 105.1
edited by BoukeReitsma
on 2023/09/14 15:09
Change comment: There is no comment for this version
To version 294.1
edited by Erik Bakker
on 2025/11/19 20:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +257 - DSH Delight
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.BoukeReitsma
1 +XWiki.ebakker
Content
... ... @@ -1,27 +1,33 @@
1 -In the last sprint cycle, we focused on what we show in Manage concerning the next-generation architecture. Furthermore, we will release a new cloud template. On top of that, we will release several minor changes with a potentially significant impact.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.205 - World Explorers.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.257 - DSH Delight.WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
5 +==== New features ====
7 7  
8 -=====Minor changes=====
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.
9 9  
10 -* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
11 -* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
12 -* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1046)
13 -* Manage - Alerting - Triggers: The non-editable trigger for Event streaming topic size has been changed to trigger on 95% of the configured size instead of 80%.
14 -* Manage - Monitoring: Viewing runtime, queue, and HTTP statistics are now limited to 7 days at a time. (3rd generation only)
10 +==== Minor changes ====
15 15  
16 -====Bug fixes====
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.
17 17  
18 -* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
19 -* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
20 -* Manage - Queue statistics: Models with a vast number of queues will now show all queues. This used to be cut off. (Gen3 only)
21 -* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
22 -* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
23 23  
20 +==== Bug fixes ====
24 24  
25 -=====Infra and image changes=====
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)
26 26  
27 -* No infra and/or image changes is this release.