Skip to Content

Changes for page 266 - Feel Free

Last modified by Erik Bakker on 2026/04/20 22:05
From version 296.1
edited by Erik Bakker
on 2025/11/20 16:12
Change comment: There is no comment for this version
To version 330.1
edited by Erik Bakker
on 2026/04/20 22:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -257 - Changing Chameleon
1 +266 - Feel Free
Content
... ... @@ -1,31 +1,31 @@
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 has a significant impact on users. Both in delivering functional value to our end users and in moving away from a legacy construct within our platform, and taking the UI one step into the future. On top of that, we have squashed some bugs. Sadly, however, we also have to announce that the announced **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** in [[release 264>>doc:Main.Release Information.Release Blogs.264 - Strict Separation.WebHome||target="blank"]] has been pulled due to not meeting quality standards. Having said that, enjoy reading our latest updates on the platform.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.257 - Changing Chameleon.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.266 - Feel Free.WebHome||target="blank"]].
4 4  
5 -==== New features ====
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.
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. (#1699)
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.
7 +* General - Event Streaming: To authenticate at DSH, our event streaming broker, we use certificates. These certificates have an expiration date, so they must be rotated. We have introduced a new way of rotating these certificates for you.
8 +** Proxy certificates must always be valid in DSH to prevent clients from encountering issues. A scheduled event runs daily during working hours to verify this.
9 +** If certificate rotation fails in the test environment, it will **not** continue to the acceptance or production environments.
10 +* General - Platform: Improved our general deletion behavior when deleting a model.
11 +* Create - System: We now show the parent entity when selecting an entity or attribute in the right panel. This allows a user to identify better where in the message's structure they currently are. (#1520)
12 +* Create - Add Integrations: Improved how we autogenerate flows for the user.
13 +* Deploy - Release: Creating a new release automatically puts you in “edit mode” for that release. (#672)
18 18  
19 19  ==== Bug fixes ====
20 20  
21 -* Create - Flow Designer: Users are correctly redirected to their request/response message based on the XSD they are selecting in the flow. (#1555)
22 -* Create - Transformation: Value mappings for a “string to enumeration” transformer are now visible after reopening the window. (#1715)
23 -* 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.
24 -* 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.
25 -* 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.
26 -* 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.
27 -* 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.
28 -* Deploy - Unused Properties: Users can select multiple properties across pages and delete the selections all at once. (#1730)
29 -* Manage - Topic Triggers: All DSH topics have topic triggers. Removing topics without a topic trigger does not result in an error.
30 -* Manage - Triggers: Manage phase access rights have been updated to allow users with the proper access to view and edit correctly.
31 -* Manage - Error Messages: Increased the maximum number of displayed error message headers from 40 to 60. (#1309)
17 +* Capture - Integration: Users are prevented from clicking the "Save integration" button too fast after creating a new message type to prevent a timing issue resulting in an error. The save button at the integration level is inactive until a message type is set for that integration. (#531)
18 +* Design - Catalog: The default request body is generated automatically for the POST operation when added as an integration in the Design phase.
19 +* Design - Edit an API integration - New/Edit resource: Added reserved keywords for the path of a resource, which can no longer be used. (#1585)
20 +* Create - Transformation - Custom XSLT snippet: Trying to save a newly edited XSLT snippet is only possible in “Edit mode”. (#1670)
21 +* Deploy - Architecture: Fixed an issue in the execution of the environment upgrade for models that have API MAM.
22 +* Deploy - Upgrade: Fixes a bug where the portainer agent could not be updated, as part of the environment template procedures, for Windows systems where portainer is installed on another drive than C:\. [CSP-1922]
23 +* Deploy - History: Entries stating 'null' will no longer be shown. (#1479)
24 +* Manage - Monitoring - HTTP Statistics (Other metrics): The mean and max for the response time are split into two graphs. (#1200)
25 +* Manage - Monitoring - Log Entries: The search/reset buttons are disabled while the reset/search is still being processed. (#1538)
26 +
27 +==== Remarks ====
28 +
29 +* General - Infrastructure: An update has been applied to the internal communication with the eMagiz-managed authorization server.
30 +* General - Platform: An update has been applied across the platform regarding the UI. As a result, all reference selectors have been replaced with combo boxes, aligning with current best practices and enabling users to interact with the platform more effectively.
31 +** Slightly modified the creation of new message types by implementing a new type of input widget that combines drop-down selection functionality with actions.