Changes for page 204 - Found It
Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 41.1
edited by Erik Bakker
on 2023/01/18 11:22
on 2023/01/18 11:22
Change comment:
There is no comment for this version
To version 48.1
edited by Erik Bakker
on 2023/02/16 08:49
on 2023/02/16 08:49
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -19 0-FastForward1 +192 - Small Step - Content
-
... ... @@ -1,34 +1,29 @@ 1 -The release brings a private store toourcommunity and makes thelatest runtimeimagevailable for ourcustomers running on the3rd generationarchitecture.Furthermore, we introduce severalimprovements toour3rd generationruntimeanditsinteraction 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.19 0-FastForward.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.V110.WebHome||target="blank"]]. 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. 7 7 8 8 =====Major changes===== 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. 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. 15 15 16 16 =====Minor changes===== 17 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. 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 -* 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 -* Deploy - Architecture: 3rd generation runtimes are included in runtime checks while upgrading your cloud environment. 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 + 33 33 ====Remarks==== 34 -* Mendix Runtime has been upgraded to Mendix 9.19.0. 27 + 28 +* Mendix Runtime has been upgraded to Mendix 9.21.0. 29 +