Skip to Content

Changes for page 262 - Good News

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -257 - Changing Chameleon
1 +195 - Easter Party
Content
... ... @@ -1,33 +1,44 @@
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 +As the quarter has ended, we went silent for a couple of weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
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.195 - Easter Party.WebHome||target= "blank"]].
4 4  
5 -==== New features ====
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 +We take the first step to fix properties to a release. This gives users more control over properties. For example, they can ensure that the release contains suitable properties that are more manageable.
8 +When this release reaches production, the first new release that users activate and have Gen3 containers/properties, the new feature becomes active. Users will see a wrench icon on the release. When they click on it, they will see an overview of the attached Gen3 properties. These properties cannot be altered for that specific release. This only counts for Gen3 properties, properties for Gen2 runtimes/machines will still be fetched from the Deploy-Properties list and can still be altered.
9 +If users notice that a specific Gen3 property of a release not contains the correct value, users can edit the value by opening the property overview of the release. At the bottom of the overview, the option ‘Change properties’ allows users to edit the properties of a release.
9 9  
10 -==== Minor changes ====
11 +A new ‘property’ release will be created when users use that option. A ‘property’ release can be identified by a suffix that contains a letter. Users can change the properties, and when they are done, they can directly activate and deploy the release. With our new improvements to the deployment plan, only the affected containers by the property change(s) will be redeployed. This will result in faster deployments.
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 +{{info}}Important to note is that
14 +* While changing a property in a ‘property’ release, users also have the option to alter the value in the Deploy-Properties list. By default, this is set to Yes, because when a new release is created, the values of Deploy-Properties will be used and not properties of an earlier release. When a user closes the screen for editing a property, the change will immediately be implemented.
15 +* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release.
16 +* There is a maximum of 26 ‘property’ releases. (26 letters of the alphabet)
17 +* Only the latest release can be edited. This can be identified by checking the suffix. The suffix with the latest letter of the alphabet is editable.{{/info}}
18 18  
19 +=====Minor changes=====
19 19  
20 -==== Bug fixes ====
21 +* General - Control Tower: Changed several generic triggers for more predictable behavior.
22 +* Administration - License Tracker: The license tracker has been updated for new license models and features.
23 +* Administration - License Tracker: When the feature ‘Data sink’ is enabled, the number of message packs of the contract will be displayed when you hover with the mouse over the feature.
24 +* Capture - Settings: Editing message types are now consistent between new and existing ones. (#884)
25 +* Design - API Gateway: Default HTTP responses are generated automatically (#417)
26 +* Design - Solution design: An additional option is added to the context menu that navigates to the message definition added to event streaming topics without processors. (#850)
27 +* Create - Add Integrations: We used the name of the API integration that you set in the Design phase to display on the Transfer screen. That helps you choose the correct integrations to add to the Create phase more quickly.
28 +* Create - 3rd Generation Migration: You can toggle the custom error handling option for your event processors while migrating your event processing container to the 3rd Generation Runtime.
29 +* Deploy - Deployment plan: When you run your deployment plan in your model using the new generation runtimes, you will be able to be the logs that relate to an executing deployment step.
30 +* Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan.
31 +* Deploy - Architecture: Certificates only editable by system admin.
32 +* Manage - Jobs: In case the model has containers that contain jobs in one of its flows, users can inspect job managers, job executions, and job step executions. Note that this only works for the 3rd generation runtime.
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)
34 +====Bug fixes====
33 33  
36 +* General - Runtime Image: A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V140.WebHome||target="blank"]].
37 +* Design - API Gateway: Improved generation of Open API JSON and example messages for API gateway operations to handle cases where an element in your gateway definition is used multiple times. (#440)
38 +* Design - API Gateway: We fixed an issue where changing the message format of a gateway message did not result in an update of the OpenAPI (i.e., Swagger) document.
39 +* Design - System message: We fixed an issue that led to importing towards the wrong message definition when the option "Import from XSD" was chosen on a synchronous message. (#818)
40 +* Create - Message: When viewing or editing an enumeration, it is no longer deleted when the cancel button is pressed.
41 +
42 +====Remarks====
43 +
44 +* Deploy - Releases: We removed the existing snapshots of release property values.