Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 96.1
edited by Erik Bakker
on 2023/06/22 13:26
Change comment: There is no comment for this version
To version 294.2
edited by Erik Bakker
on 2025/11/19 20:31
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -200 - Uncharted Territories
1 +257 - Changing Chameleon
Content
... ... @@ -1,27 +1,33 @@
1 -In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture and others.
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.200 - Uncharted Territories.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 -=====Minor changes=====
5 +==== New features ====
6 6  
7 -* Create - Flow Designer: it is possible to select multiple components by area selection on the area with a scrollbar.
8 -* Create - Flow designer: The new best practices have updated Kafka components' default values. Updated values are:
9 -** For Kafka templates:
10 -*** Batch size: 200000
11 -*** Linger: 300
12 -** For Kafka message listener containers
13 -*** Fetch min. amount: 100000
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.
14 14  
15 -{{warning}}The existing Kafka components in your flows will automatically be updated with the new best practice values. To make deploying these changes more effortless for you, we will create a new version of your flows after updating the values (versions will be created in the name of model contacts) and transfer them to the Deploy phase. You can then create and deploy a new release with updated flow versions.{{/warning}}
10 +==== Minor changes ====
16 16  
17 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
18 -* Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture.
19 -* Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation. Now, you can see all related logs regarding your deployment. By default, we only show some necessary logs, such as error logs, warning logs, and started runtime information logs. You can use the filter logs icons at the top of the list to show more information.
20 -* Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser. Furthermore, there is no deployment step configuration to "enable" triggers anymore.
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.
21 21  
22 -====Bug fixes====
23 23  
24 -* Deploy - Architecture: We improved timeout settings to give Stop, Restart, and Reset runtime actions enough time to execute. (#957)
25 -* Design - Store: Importing into "Design" from the store is possible, even if the integration is not in Create yet.
26 -* Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases. Note that this functionality requires a newly deployed release. (#956)
27 -* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
20 +==== Bug fixes ====
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)
33 +