Changes for page 243 - Migration Magic
Last modified by Erik Bakker on 2025/06/02 09:33
From version 230.1
edited by Erik Bakker
on 2025/02/25 08:59
on 2025/02/25 08:59
Change comment:
There is no comment for this version
To version 86.1
edited by Erik Bakker
on 2023/06/05 16:04
on 2023/06/05 16:04
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 - 239 -ModernTalking1 +199 - Home Improvements - Content
-
... ... @@ -1,17 +1,21 @@ 1 -In the last sprint ,we focused ontesting the eMagiz Mendix Connectorand solvinginternal feedback on the processand theonnector itself.Withthat behindus, we are readyto launchthe new eMagiz Mendix Connectorin our community.Withthis release,wewill make it availablefor all new Mendixsystems in modelsrunningon thecurrent-generation architecture.In a futurerelease, we will bring a migration wizard aiding a simpleandsmooth migrationtothe new eMagiz MendixConnector. Ontop ofthat, wehave some minor updates to improvehe quality of the platform.1 +In the last sprint cycle we have focused on improving various aspects of the portal functionality. Among others we focused on the next-generation architecture, the store, security and certificate management. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 239 -ModernTalking.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]]. 4 4 5 -==== NewFeatures====5 +=====Minor changes===== 6 6 7 -* New Mendix connector: We will introduce a new eMagiz Mendix connector. This new connector delivers improved stability and a simpler setup process. It is better integrated into your eMagiz models and will receive full support. The connector can be used for new systems and will be enabled by default for new models. 8 -** A migration wizard will be released later, allowing you to quickly and smoothly migrate your legacy Mendix connectors to the new Mendix connector. 7 +* * Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 8 +* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately 3 months before the expiration dates of event streaming users' access certificates. 9 +* Deploy - Release: After successful machine deployments, unused runtime images will be automatically removed. This can be disabled by changing the machine step in your deployment plan. 10 +* Manage - Monitoring: HTTP statistics page now displays all of the resources. 11 +* Manage - Alerting: congestion control wil be enabled by default with 10 alerts per 10 minutes and user cannot see or change it. 12 +* General - Infra: Changed the library used for storing metadata in the eMagiz Control Tower. 9 9 10 -==== Minor Changes====14 +====Bug fixes==== 11 11 12 -* Create - Flow Designer: The view button that can be found by navigating to the right panel of the Flow Designer and choosing the Support Objects tab opens a pop-up that shows a list of all support objects that can be added. This button is accessible only in the view mode of the Flow Designer. (#870) 16 +* Create - Store: Spring Reserved words that contain * are not incorrectly replaced with the prefix of the flow. 17 +* Manage - Monitoring: When an application failed to start, not all log messages were visible in the manage phase. 13 13 14 -==== Bug fixes====19 +====Remarks==== 15 15 16 -* Create - Flow Creation: When creating the corresponding infra and entry flows belonging to a system that will host a SOAP endpoint, we fixed a bug causing two support objects to break upon creation. (#1517) 17 -* Manage - Dashboard: The manage phase dashboard no longer breaks when an error occurs in a component with an id that does not follow the {{code}}[id].[system].[flow]{{/code}} convention, or when that value is longer than expected. (#1566) 21 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.