Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06

From version 294.3
edited by Erik Bakker
on 2025/11/19 20:31
Change comment: Renamed back-links.
To version 47.1
edited by Erik Bakker
on 2023/01/31 14:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -257 - Changing Chameleon
1 +191 - Fifty Fifty
Content
... ... @@ -1,31 +1,53 @@
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 +The release introduces a lot of minor fixes as a result of our "hackathon" efforts. Subsequently, we will release several 3rd generation runtime offerings.
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>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target= "blank"]].
4 4  
5 -==== New features ====
5 +=====New features=====
6 +* Deploy - Architecture: We added the possibility to register network shares in your container volume settings. This enables the use of network shares without having to mount them manually on the host machine and then again on the container level. This option is only available for 3rd generation runtimes that run on-premises.
7 +* Deploy - Containers: In Deploy containers, a 'Debug' option is added for flows on the 3rd generation eMagiz runtime.
8 +** This option will temporarily be available for users on the next generation runtime. It allows one to easily wiretap messages from channels in a flow to a queue, which can then be browsed using the queue browser. One flow can be wiretapped at the time per container.
9 +** To use this option, the model must be fully migrated to Gen3, including the JMS. Additionally, only flows in a container with the Gen3 Debugging components inside the associated container infra flow can be debugged. Please consult the documentation for more information on how to set up debugging on Gen3.
10 +* Manage - Alerting: Five new triggers are available for Model in G3.
11 +** Error Message is to evaluate the headers of the original message which resulted in an error.
12 +** Log Keyword is to evaluate logging messages. You can provide one or several words which you expect in your logging events.
13 +** Queue Consumers is to check whether more than one consumer is expected on the queue level.
14 +** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
15 +** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages expected to pass through the flow.
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.
17 +=====Minor changes=====
9 9  
10 -==== Minor changes ====
19 +* Data-Limit: Set data limit per environment.
20 +* Login page: The login page /login.html now redirects to the actual login page /p/login. (#671)
21 +* Create - Flow designer: Removed the unnecessary refresh button from the component creation pop-ups. (#858)
22 +* Create - Flow designer: Properties in the property overview pages are sorted as Test/Acceptance/Production. (#804)
23 +* Create - Flow designer: We improved validation and help text on Wss4J interceptors components. (#733)
24 +* Create-Flow testing: Improved the help text when adding a header type for a test message. It clearly states which Java classes can be used, along with some examples. (#742)
25 +* Deploy - Releases: Setting a release as active by pressing the deploy button creates an entry in the deploy history. (#823)
26 +* Deploy - Releases: We improved the notification pop-ups of failed machine deployments.
27 +* Deploy - Releases: We added column sorting to the pop-up showing the missing properties. (#860)
28 +* Deploy - Architecture: New cloud slots have their auto-upgrade value set to true by default. (#841)
29 +* Deploy - Architecture: A docker container's status is more visible when you open the detail page of the docker container.
30 +* Deploy - Architecture: The instance's state is now visible on the detail page about an instance. (#699)
31 +* Deploy - Architecture: We changed the wake-up time of cloud slots on Fridays to 6:00 UTC so that they no longer fall within our regular deployment windows. (#559)
32 +* Deploy - Architecture: We added runtime memory checks to 'Apply to environment' to prevent invalid deployments. (#719)
33 +* Deploy - Properties: We improved runtime selection when copying properties. (#796)
34 +* Manage - Explore: Improved the displayed error message when a message could not be loaded in the message redelivery screen. (#696)
35 +* Manage - Explore: "Save as test message" button opens a pop-up that allows you to edit your test message's name, description, content, and headers before saving it.
36 +* Manage - HTTP statistics: Fixed a typo in the HTTP statistics dashboard. (#856)
37 +* Manage - Alerting: By default, no filter is applied to the status when navigating to the "Notifications" overview or resetting the filters on the "Notifications" overview. (#486)
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.
18 18  
19 -==== Bug fixes ====
40 +====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)
42 +* Design - Solution design: We hide systems without functional integration now. (#714)
43 +* Create - API Gateway: Security header case insensitive
44 +* Create - Flow designer: Enabling redelivery for your integration is applied after resetting your offramp and exit flow. Before this change, you needed to remove and add the integration to Create phase to use this setting.
45 +* Deploy - Containers: Applied styling to the error pop-up with the list of reasons why a runtime can't be deleted to make it easier to read. (#546)
46 +* Deploy - Architecture: Deploying your model to the cloud for the first time required you to press 'Apply to Environment' twice. This is no longer the case. (#508)
47 +* Deploy-Volumes: Network volumes are visible when the container is not deployed.
48 +* Manage - Monitoring: Fix typo in Event Processors Metrics. (#835)
49 +
50 +====Remarks====
51 +
52 +* Mendix Runtime has been upgraded to Mendix 9.21.0.
53 +