Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 44.1
edited by Erik Bakker
on 2023/01/23 13:49
Change comment: There is no comment for this version
To version 48.1
edited by Erik Bakker
on 2023/02/16 08:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +192 - Small Step
Content
... ... @@ -1,32 +1,29 @@
1 -The release finished many new improvements to our 3rd generation runtime offering and fixed various annoying bugs and minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
1 +The release introduces two new features for our 3rd generation runtime. Subsequently, we will release several minor feedback points and bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.192 - Small Step.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.V120.WebHome||target="blank"]].
7 -* 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.
6 +* Deploy - Architecture: We add a new option per container to open a page that you can use a feature "Start / Stop flows" for runtime running on the 3rd generation runtime. Note that the debugger functionality can also be started on this view.
7 +* Manage - Monitoring: New dashboard, ‘Event streaming statistics,’ is available for you to monitor your topics and consumer groups.
8 8  
9 9  =====Major changes=====
10 10  
11 -* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
11 +* Create - Flow Designer: We applied a new setting for the JMS flow where the JMS flow will try to shrink the journal files to 50, so it does not end up with a high amount of JMS files that take too long to read. For this to be applied, please reset your JMS flow and deploy the new version on your model.
12 12  
13 13  =====Minor changes=====
14 14  
15 -* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes.
16 -* Create - Flow designer: sensitive information stored in property values is masked. (#790)
17 -* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions.
18 -* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
19 -* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
20 -* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828)
21 -* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
22 -* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
23 -* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
15 +* Design- Kafka topic: As a user, you can now only define the retention size on the topic level. Based on that input value and a set of best practices eMagiz will, in turn, calculate the correct settings for you. Don't hesitate to contact your partner manager if you want to change the default settings. When applying the configured settings to your topic, we also send configuration settings for segment bytes and segment ms based on our best practice to improve performance.
16 +* Create - Flow Designer: You can make a multiple selection zone by pressing and holding the left mouse button instead of pressing the "Shift" key from now on.
17 +* Deploy- User Management: Transfer from design button imports users and roles
18 +* Deploy - Release: We improved the activation process of a release with one or more 3rd generation runtimes. As of now, we are preparing the release as the first step of deploying your release. In this overview, you can see the progress of the preparation step when you execute the deployment of a release. Note that a new deployment plan is needed to make this work.
24 24  
20 +
25 25  ====Bug fixes====
26 -* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
27 -* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793)
28 -* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
29 -* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
30 -* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
31 -* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
32 32  
23 +* Deploy/Monitoring - Debugger: We have improved the error handling on the debugger functionality to ensure it does not show the error code and technical error anymore.
24 +* Deploy/Monitoring - Debugger: Pressing the "Stop debugger" button now functions correctly
25 +
26 +====Remarks====
27 +
28 +* Mendix Runtime has been upgraded to Mendix 9.21.0.
29 +