Changes for page 243 - Migration Magic
Last modified by Erik Bakker on 2025/06/02 09:33
From version 229.1
edited by Erik Bakker
on 2025/02/25 08:29
on 2025/02/25 08:29
Change comment:
There is no comment for this version
To version 59.1
edited by Erik Bakker
on 2023/03/14 08:51
on 2023/03/14 08:51
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 +194 - Giant Leap - Content
-
... ... @@ -1,17 +1,33 @@ 1 - In the lastsprint, we focused on testingthe eMagiz Mendix Connector andsolvinginternal feedback on theprocess and theconnector itself.With that behindus we arereadyto launch thew eMagiz Mendix Connectorto ourcommunity. Withthisreleasewe will makeavailableforall new Mendixsystems inmodelsrunningonthecurrent-generation architecture. Subsequently we willimplementamigrationizardaiding a simple andsmooth migrationto the new eMagizMendix Connector. On top of that, wehave some minorupdatestoimprovethequality of the platform.1 +The release introduces various improvements on our 3rd generation runtime architecture and various other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements. 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.194 - Giant Leap.WebHome||target= "blank"]]. 4 4 5 -====New Features====5 +=====New features===== 6 6 7 -* NewMendix connector: Wewillintroduce aneweMagiz Mendixconnector.This newconnector deliversimprovedstability and asimplersetup process. Thenew connectoris betterintegratedinyoureMagizmodelsand will receivefullsupport. Theconnectorcanbeusedfornewsystemsnd will beenabledby defaultfornewmodels.8 -* *Amigrationwizardwillbereleasedlaterwhich allows youto easilyandsmoothly migrateyourcurrentlegacyMendixconnectorstothenew Mendixconnector.7 +* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]]. 8 +* Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers and waking up a cloud slot will start those containers. (#889) 9 9 10 -====Minor Changes====10 +=====Minor changes===== 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 view mode of the Flow Designer. (#870) 12 +* Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you are using custom error handling on your event processors or not. 13 +* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807) 14 +* Deploy - User Management: Roles are sorted alphabetically. (#806) 15 +* Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup. Please use the ‘Upgrade’ feature to keep your cloud architecture up-to-date. 16 +* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and graph and made some small visual improvements. 17 +* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833) 13 13 14 14 ====Bug fixes==== 15 15 16 -* Create - Flow Creation: Payload root Qname support object for the API gateway infra is not containing duplicates now. (#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 [id].[system].[flow] convention, or when that value is longer than expected. (#1566) 21 +* Generic: We fixed an issue that you may see a screen with a broken styling when switching among phases. 22 +* Create - Flow Designer: Removed the option to create a new resource on resource selection pop-up of simple XSD schema support object. 23 +* Create - Flow designer: We fixed the flow generation of entry flows for API Key secured API Gateway operations. This problem was introduced in version 193 (2023-02-04). (#902) 24 +* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filename (>100 characters). 25 +* Deploy - Releases: You need edit rights in test environment of deploy phase to execute “Update flows to latest versions” action. 26 +* Manage - Dashboard: We update the view to visualize the split entries after you do a migration a combined entries. 27 +* Manage - Logging: When a container cannot be started due to an incorrect stylesheet, the error message will include what the error is and in which stylesheet is occurred (#825) 28 +* Manage - Logging: Reduced the occurance of 'Failed to send to Elastic' log messages which triggers alerts. (#898) 29 +* Manage - Alerting: Editable column shows the correct value. 30 + 31 +====Remarks==== 32 + 33 +* Create - Flow designer: After the deployment, the ‘Version Compare' and 'Version Restore’ features will be unavailable for a few hours, because of data migration. You will get an error stating that the version is not compatible with the selected feature until migration has finished.