Changes for page 243 - Migration Magic
Last modified by Erik Bakker on 2025/06/02 09:33
From version 224.1
edited by Erik Bakker
on 2025/02/10 09:15
on 2025/02/10 09:15
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 - 238-PreparationParaside1 +199 - Home Improvements - Content
-
... ... @@ -1,12 +1,21 @@ 1 -In the last sprint ,we focused onfinishingthe firstiteration of ournew eMagiz Mendix Connector and the firstiteration ofour new base image. We will firstutilize thenew eMagiz Mendix Connectoro getan even better feelingofits performance, butyou will notice a UI change straightaway.Once we have passed that hurdle, we will sharemore informationaboutit and releaseit to a broaderrange oftomers. Regardingthebase image, we willnow introducehis to our flow testingoffering to see ifanythingunexpectedhappens. This is an additional safety measurewehaveputin place toducethe chance ofsomething breaking inyourmodeloncehe new baseimageis released. Ontop of that, 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. 238-PreparationParadise||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 -====Minor Changes====5 +=====Minor changes===== 6 6 7 -* ILM: We defined the systems labeled as “isMendix” with the “MX“ icon, making it easier to identify the Mendix system. 8 -* Create - Flow Testing: As we are finalizing the new eMagiz runtime image that will update the Spring version to Spring boot 3.4.1 and Java to 17.0.13, we are now bringing these latest updates to flow testing. This means that any flow test you execute will run on the base image your runtimes will run on after the release of the new eMagiz runtime image. If one of your test cases suddenly exhibits weird behavior that you think is due to the update, feel free to contact us via our [[support department>>mailto:support@emagiz.com]]. 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 10 ====Bug fixes==== 11 11 12 -* Create - Add Integrations: Integrations using the entry/exit connector, using the same message type, can now be untransferred from the create phase. (#1591) 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. 18 + 19 +====Remarks==== 20 + 21 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.