Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 37.1
edited by Erik Bakker
on 2022/12/08 08:52
Change comment: There is no comment for this version
To version 269.2
edited by Erik Bakker
on 2025/07/14 07:12
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +249 - Amendment Avalanche
Content
... ... @@ -1,33 +1,11 @@
1 -The release brings a private store to our community and makes the latest runtime image available for our customers running on the 3rd generation architecture. Furthermore, we introduce several improvements to our 3rd generation runtime and its interaction with the portal.
1 +This release introduces the ability for beta models to run on our new event broker. With this critical step being reached, we can migrate the first set of beta customers to the new event broker while simultaneously further developing this proposition.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.189 - Private Eye.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2471 - Help Out.WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
5 +==== New features ====
7 7  
8 -=====Major changes=====
7 +* General - Event Streaming: Run your event streaming solution on our new event broker at DSH. Please note that we will initially release this functionality as a **beta** feature. This means it is currently only available to a select number of models. Once this functionality is more developed, we will share more information on this.
9 9  
10 -*Store - Private store. This release introduces the private store with the following features:
11 -** Store items will be private by default and are only accessible for users that belong to the same company as the user that exported the store content. Note that the store item needs to be approved before it is visible to users.
12 -** A new user role, "Store Exporter," will be introduced and can be assigned to the users who can create and update store items.
13 -** Approval of a store item will be executed by eMagiz personnel, who can also set a store item to be public.
14 -** Public store items will be importable by all users.
9 +==== Minor changes ====
15 15  
16 -=====Minor changes=====
17 -
18 -* Create - Event Streaming: Event streaming is now available for models migrating to the 3rd generation runtime.
19 -* Create - Transformation: source filter on attribute with empty field is more readable in read-only mode. (#732)
20 -* Create - Migration: Improved compatibility checks related to the 3rd generation runtime migration.
21 -* Deploy - Check properties: Informative error messages when saving or creating a property. (#576)
22 -* Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps.
23 -* Deploy - Architecture: Added reset feature for 3rd generation runtimes.
24 -
25 -====Bug fixes====
26 -* Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows.
27 -* Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances.
28 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish.
29 -* Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798)
30 -* Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment.
31 -
32 -====Remarks====
33 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
11 +* Deploy - Properties: A new data type option is introduced on the property level. This data type enables the storage of PEM certificates in their correct format, which is necessary for a secure connection to DSH.