Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
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 98.1
edited by Erik Bakker
on 2023/07/17 21:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +201 - Be Informed
Content
... ... @@ -1,29 +1,30 @@
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 +In the last sprint cycle, we focused on planning the upcoming quarter, finishing up, and working on the Hackathon to fix several smaller items.
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.201 - Be Informed.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"]].
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.
7 +* Portal - Menu: The back button is changed to have text on it to make the navigation much clearer. (#949)
8 +* Design-Architecture: Topic Storage detail page contains help text. (#994)
9 +* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832)
10 +* Design - API Gateway: Small styling improvement on the "Edit integration page." (#954)
11 +* Create - Flow Designer: When deleting one or multiple components, you cannot change the selection before confirming or canceling the delete action. (#969)
12 +* Create - Migrate to 3rd Generation: If one or more flows break during migration, a popup will inform the flows containing errors after the migration. (#983)
13 +* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979)
14 +* Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown. All changes made in the portal that will affect your running environment are listed here. These changes can be applied to the environment or reverted. (#828)
15 +** Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release.
16 +** Changes with a direct effect will not be listed (for example, restarting a machine).
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 27  
28 -====Remarks====
29 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
20 +* Design - Solutions: We fixed an issue that displayed a message mapping error despite having a passthrough API gateway. (#935)
21 +* Design - Settings: The full length of the contract number can now be registered. (#958)
22 +* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen 3 will not block migration. (#982)
23 +* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990)
24 +* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972)
25 +* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
26 +
27 +=====Infra and image changes=====
28 +
29 +* Changed the endpoint for sending error messages to the eMagiz Control Tower.
30 +* Updated the Spring version of the gateway supporting deploy and manage phase operations.