Skip to Content

Changes for page 189 - Private Eye

Last modified by Carlijn Kokkeler on 2024/05/22 13:43
From version 35.1
edited by Erik Bakker
on 2022/12/06 16:11
Change comment: There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2022/10/24 11:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +186 - Daemon Switch
Content
... ... @@ -1,29 +1,25 @@
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 +Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
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.186 - Daemon Switch.WebHome||target="blank"]].
4 4  
5 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"]].
6 +* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
7 7  
8 -=====Major changes=====
9 -
10 -* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your jms-server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
11 -
12 12  =====Minor changes=====
13 13  
14 -* Create - Event Streaming: Event streaming is now available for models migrating to the 3rd generation runtime.
15 -* Create - Transformation: source filter on attribute with empty field is more readable in read-only mode. (#732)
16 -* Create - Migration: Improved compatibility checks related to the 3rd generation runtime migration.
17 -* Deploy - Check properties: Informative error messages when saving or creating a property. (#576)
18 -* Deploy - Deployment plan: We improved the deployment plan to avoid crashing the server when executing a deployment plan.
19 -* Deploy - Architecture: Added reset feature for 3rd generation runtimes.
10 +* Design System. Changed the look and feel across the portal altogether. Changes can be seen in:
11 + ** Datagids, where there is now on hover action for example.
12 + ** Pop ups
13 + ** Context menus, also have on hover action
14 + ** Styling of scrollbars
15 + ** Warning, info and error context labels.
16 +* Message Redelivery - admin logs improved to better analyze issues when they occur
17 +* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality
18 +* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
20 20  
21 21  ====Bug fixes====
22 -* Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows.
23 -* Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances.
24 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish.
25 -* 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)
26 -* Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment.
27 -
28 -====Remarks====
29 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
21 +* Deploy - Deployment plan. Performance of page to deploy a release increased significantly
22 +* Store - Import resources was incorrectly done in specific cases, which is now fixed
23 +* Store - Target namespace will be imported when importing an XML Message Definition
24 +* Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model.
25 +* Store - Importing items from the store sometimes resulted in invalid JMS connection factories.