Changes for page 259 - Improve Infinitely
Last modified by Erik Bakker on 2026/01/15 09:27
From version 293.1
edited by Erik Bakker
on 2025/11/19 20:07
on 2025/11/19 20:07
Change comment:
There is no comment for this version
To version 271.1
edited by Erik Bakker
on 2025/07/14 08:06
on 2025/07/14 08:06
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 57-DSH Delight1 +249 - Amendment Avalanche - Content
-
... ... @@ -1,33 +1,35 @@ 1 -This release featuresvariousupdates to our platform,with ourneweventstreamingbrokerrunningon DSHtakingcenterstage. With thisrelease,ourlatest eventstreaming functionality will beavailabletoeveryone(GA).Ontopof that,wewilllaunchthepreviouslyannouncednew [[runtimeimage>>doc:Main.ReleaseInformation.RuntimeImages.V341.WebHome||target="blank"]]for **all**customers.Ontopof that,wehaveseveralsmaller featuresandbug fixesforyoutoenjoy.1 +This release is characterized by many updates to our platform, both from a user perspective and from a technical perspective regarding our backend services. This sets us up to allow all users to prepare their Mendix systems for a migration to DSH (if applicable). Furthermore, it enables us to assist our users more effectively as they develop within the platform. 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>>Main.Release Information.Release Blogs.249 - Amendment Avalanche.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 - License Tracker: You can now see licensed flows on the model level alongside the company level after we have registered the correct configuration. (#859) 8 +* Event Streaming - DSH Connection: The eMagizConnector base image has been updated as preparation to support event streaming integrations on DSH. This allows all users to prepare their Mendix systems to connect to DSH. 9 +** Note that all users running the new eMagiz Connector will receive this update with their next release. **If you already have a running eMagiz Connector, you need to restart the application to retrieve the latest information after the new release is prepared for you. ** 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. 13 +* Event Streaming - User Management: When adding new event streaming integrations that link to an **existing** event streaming processor, you **must** transfer them to the Create phase via the adding integrations tooling in the Create. This will trigger eMagiz to update the Deploy user management accordingly. 14 +** This functionality applies to both the old and new event broker. 15 +* Design - Message Definition: The overview of the attributes shown in the entity overview of the data model (i.e., CDM) and the system message now also shows the description of the attribute. (#1671) 16 +* Create - Flow Designer: The circuit breaker option under the request handler advice chain can now also be filled with a property placeholder. (#1619) 17 +* Create - Flow Designer: The overwrite option of the headers of a standard header enricher is now placed in the 'Basic' tab instead of the 'Advanced' tab. (#1666) 18 +* Create - Flow Testing: When creating a new test message and selecting the option "from existing file", the default option is now "Create" instead of "Capture". (#1659) 19 +* Create - Flow Testing: Each trace entry in the "Traces" overview now contains a timestamp. (#1661) 20 +* Capture - Overview: Deleting systems/integrations/tenants in Capture now shows a progress bar. (#1665) 21 +* Deploy - Unused Properties: For the unused properties functionality on the Create Phase Release, it is adjusted so that only the properties that are not used in any of your releases across environments are shown. They can be deleted without impacting any of the existing releases. (#1244) 22 +** Context is added to guide users through the following actions. 23 +** Performance has improved significantly. As a result, the process takes less time than before. 24 +* Deploy - Releases: Promoting a release to the next environment does not trigger the auto-delete behaviour of releases anymore. (#1318) 25 +* Deploy - Containers: Only the active containers are updated when a user adds or removes something from a release. Consequently, when a new integration is added, inactive containers will not contain the new integration. They can be reactivated if desired to enable automatic updates again. (#986) 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) 33 - 29 +* Create - Add Integrations: We fixed several issues regarding untransferring and transferring integrations. Among other things, we addressed the following specific cases. 30 +** Re-transferring integrations to Deploy. 31 +** Untransfering the last integration of a system. 32 +* Create - Flow Designer: The user can now completely read the alerts in the flow designer with a hover text. (#1168) 33 +* Create - Flow Designer: The "Allow empty array" checkbox in Create can now be used without it throwing an error. (#1640) 34 +* Create - Flow Designer: We ensured that the order in which you create flow versions for flows belonging to an "exit/entry" construction can be random. As a result, this will prevent users from ending up with only a part of the flows belonging to this construction in Deploy, while all flow versions are indeed created in Create. 35 +* Manage - Alerting - Triggers (Error): Error alerts with ‘not equal to’ and ‘does not contain’ evaluations on ‘exception class’ and/or ‘exception message’ will now only trigger if both the first and last exception don’t equal/contain the value. (#1576)