Changes for page 258 - Vale Bene

Last modified by Erik Bakker on 2025/12/01 09:38

From version 237.1
edited by Erik Bakker
on 2025/03/24 14:46
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 -241 - Wild West
1 +257 - DSH Delight
Content
... ... @@ -1,36 +1,33 @@
1 -In the last sprint, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] containing a much-needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.
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.241 - Wild West.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 -* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
8 -* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture because this field was not visible enough in the rest of the portal. (#1608)
9 -* Capture / Design: For new systems, message types, machines, tenants, and models, hyphens are **no longer allowed** in the technical name. The technical name can only consist of lowercase letters and digits and must start with a letter. This also applies to systems, message types, and tenants that have not yet been transferred from design to creation. The portal will give an error message while transferring, and the hyphen has to be removed manually.
10 -* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
11 -* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
12 -* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
13 -* Infra - Security: Improved security by implementing additional safeguards for AWS native services.
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 -====Bug fixes====
10 +==== Minor changes ====
16 16  
17 -* Capture - Add System: A loading bar is displayed before showing the pop-up when a user tries to create or edit a system. (#1228)
18 -* Capture - Edit System: When editing a system, the validation now considers that the name cannot be an empty string. (#1562)
19 -* Design - Message Definition: Two minor improvements are introduced:
20 -** The widget prevents users from adding the same message attribute within a message definition multiple times.
21 -** When adding a new message entity within your message definition and expanding the existing message definition, it doesn’t throw an exception when the user presses the Save button multiple times in a short time frame.
22 -* Design - Catalog: When creating the Swagger JSON, all custom examples users add will be shown correctly when displaying the Swagger. (#1597)
23 -* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513)
24 -* Create - Add Integrations: Users can untransfer a flow even when there is a property attached to the flow. (#1590)
25 -* Create - Add Integrations: When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned.
26 -* Create - Components: The browser page now displays the correct page title (#1509)
27 -* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
28 -* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560)
29 -* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already an existing property description. (#1526)
30 -* Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
31 -* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore moves the user to the queue browser of the correct environment. (#1408)
32 -* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed. (#1550)
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.
33 33  
34 -====Remarks====
35 35  
36 -* New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with **Java 21**, and functionality works as expected.
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 +