Changes for page 262 - Good News
Last modified by Erik Bakker on 2026/02/23 08:06
From version 318.1
edited by Erik Bakker
on 2026/02/23 08:05
on 2026/02/23 08:05
Change comment:
There is no comment for this version
To version 295.1
edited by Erik Bakker
on 2025/11/19 20:51
on 2025/11/19 20:51
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 62-GoodNews1 +257 - Changing Chameleon - Content
-
... ... @@ -1,28 +1,31 @@ 1 -This release includesmanyupdates to our platform.Wearereleasingsomebetafeatures forcustomersusingour latest versionoftheAPI Gateway, allowing them touse multiple authenticationmethods. On top of that, wehavealsolaunchedanew [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers.Furthermore, we haveaseriesofsmallerimprovementsto enhanceyoureverydaywork.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>>doc:Main.Release Information.Release Blogs.2 62-GoodNews.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.257 - Changing Chameleon.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 + 5 5 ==== Minor changes ==== 6 6 7 -* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers is available. 8 -* Create - Flow Designer: The help text for the Result Type attribute of the JSON to XML transformer has been improved. (#1553) 9 -* Deploy - Releases: The on‑hover text for a release also displays the most recent date and time the release was edited. (#341) 10 -* Create - Flow Designer: Unused support objects can be deleted with a single button. (#794) 11 -* Deploy - User Management: For models that have been migrated to our latest functionality for both our event streaming and API offering, changes to users in the Deploy phase will be applied immediately for both manually created users and system users. 12 -* Deploy - Architecture: The Apply to Environment pop-up has been updated to reflect progressive changes made to specific objects. Any pending changes on Container, Router, Certificate, Instance, and AWS resources are now stacked and displayed to the user. The list is ordered from the earliest change at the top to the most recent at the bottom, allowing users to clearly see all modifications made to a specific object until the Apply to Environment button is clicked. These changes will remain active for future operations. (#1537) 13 -* Deploy - Architecture - Routes: The View and Edit pages for Routers have been updated to remove the Endpoint DNS Name and Flow Symbolic Name fields. (#1537) 14 -* Manage - Alerting: For Log and Error triggers, a custom subject can now be specified under ‘notifications’. This enables you to sort incoming alerts in your mailbox more easily. 15 -* Manage - Alerting: We have tightened the allowed characters for the triggers to reduce further the likelihood of HTML injection into the bodies of alerting emails sent by eMagiz. 16 -** Note: if you already have existing alert rules that contain characters that are now considered illegal, you will need to change them when you make any change to that trigger. 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. 17 17 18 18 ==== Bug fixes ==== 19 19 20 -* Create - Flow Designer: When using DSH support objects, the required admin-only fields are automatically filled in. (#1755) 21 -* Create - Untransfer integration: We fixed an issue where you could not remove an integration of the Mendix connector system, which was migrated from the Legacy eMagiz Mendix Connector to the current eMagiz Mendix Connector in Create. 22 -* Design - Catalog: Help texts related to “content”, “Json format”, and “Gateway message definition” are updated. (#1082) 23 -* Create - Store: When importing a store component with properties, validation feedback will now be provided if the property value does not align with the expected type. (#1276) 24 -* Manage - Explore: Error message is much more descriptive when the container is not running (#1321) 25 - 26 -==== Remarks ==== 27 - 28 -* General - Infrastructure: We updated our image builder for Windows images to use the latest Java versions for images. Effectively, this means that any image built for Windows from this release onwards that uses a base image //3.4.0// or above, will use Java 21.0.10 as baseline. Images below version //3.4.0// will now use Java 17.0.18. Therefore, new (property) releases that use the same eMagiz base image, will still use a different Java version, and may therefore have some changed behavior. Normally that would not be noticable, but since these Java version increases drops support for some weak cipher suites, connectivity may be affected. For more information, please refer to the release notes of image 3.5.1. 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)