Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 46.1
edited by Erik Bakker
on 2023/01/31 14:51
Change comment: There is no comment for this version
To version 246.1
edited by Erik Bakker
on 2025/04/22 13:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +243 - Migration Magic
Content
... ... @@ -1,53 +1,30 @@
1 -The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
1 +In the last sprint, we released our migration wizard for the new eMagiz connector. This wizard will guide you through the process of migrating the existing eMagiz connector within Mendix to our latest version, which is packed with improvements. Furthermore, we will release a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] that corrects some changes and improves the UI/UX of loads of data grids across the platform. In addition, we have various smaller changes and bug fixes for you to enjoy.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.243 - Migration Magic.WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -* Deploy - Architecture: We added the possibility to register network shares in your container volume settings. This enables the use of network shares without having to mount them manually on the host machine and then again on container level. This option is only available for 3rd generation runtimes that run on-premises.
7 -* Deploy - Containers: In Deploy containers a ‘Debug’ option is added for flows on the 3rd generation eMagiz runtime.
8 -** This option will temporarily be available for users on the next generation runtime. It allows to easily wiretap messages from channels in a flow to a queue, which can the be browsed using the queue browser. One flow can be wiretapped at the time, per container.
9 -** To use this option, the model must be fully migrated to Gen3, including the JMS which also needs to be reset. Additionally only flows in a container that has the Gen3 Debugging components inside of the associated container infra flow can be debugged. For more information on how to setup debugging on Gen3, please consult the documentation.
10 -* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
11 -** Error Message is to evaluate the headers of the original message which resulted in an error.
12 -** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
13 -** Queue Consumers is to configure for queues where more than 1 consumer is expected.
14 -** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
15 -** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow.
5 +====New Features====
16 16  
17 -=====Minor changes=====
7 +* eMagiz Connector - Migration: We have implemented a migration wizard that allows you to migrate to the new eMagiz Connector. You can start this wizard via Deploy -> Mendix connectors on a system-by-system basis.
8 +** Migrating eMagiz connector flows to the new version will remove the history of the old versions from the history tab. Make sure you copy this information if you want to archive it. After migrating your flows, this will no longer be visible.
18 18  
19 -* Data-Limit: Set data limit per environment.
20 -* Login page: Login page /login.html now redirects to the real login page /p/login. (#671)
21 -* Create - Flow designer: Removed the unnecessary refresh button from the component creation pop-ups. (#858)
22 -* Create - Flow designer: Properties in the property overview pages are sorted as Test/Acceptance/Production. (#804)
23 -* Create - Flow designer: We improved validation and help text on Wss4J interceptors components. (#733)
24 -* Create-Flow testing: Improved the help text when adding a header type for a test message. It now clearly states which types of Java classes can be used along with some examples. (#742)
25 -* Deploy - Releases: Setting a release as active by pressing the deploy button creates an entry in the deploy history. (#823)
26 -* Deploy - Releases: We improved the notification popups of failed machine deployments.
27 -* Deploy - Releases: We added column sorting to the popup showing the missing properties. (#860)
28 -* Deploy - Architecture: New cloud slots have their auto-upgrade value set to true by default. (#841)
29 -* Deploy - Architecture: A docker container's status is more visible when you open detail page of the docker container.
30 -* Deploy - Architecture: On the detail page about an instance, the state of the instance is now visible. (#699)
31 -* Deploy - Architecture: We changed the wake-up time of cloud slots on Fridays to 6:00 UTC, so that they no longer fall within our regular deployment windows. (#559)
32 -* Deploy - Architecture: We added runtime memory checks to ‘Apply to environment’, to prevent invalid deployments. (#719)
33 -* Deploy - Properties: We improved runtime selection when copying properties. (#796)
34 -* Manage - Explore: Improved the displayed error message when a message could not be loaded in the message redelivery screen. (#696)
35 -* Manage - Explore: “Save as test message” button opens a pop-up that allows you to edit your test message’s name, description, content and headers before saving it.
36 -* Manage - HTTP statistics: Fixed a typo in HTTP statistics dashboard. (#856)
37 -* Manage - Alerting: By default, no filter is applied to Status when navigating to Notifications, or resetting the filters on Notifications. (#486)
10 +====Minor Changes====
38 38  
12 +* General - Event Streaming: We have updated our event streaming infrastructure.
13 +* General - Datagrids: We have updated a lot of our data grids to reflect the latest changes available
14 +** ‘Double click’ action on data grid rows is introduced to the newer datagrid format and, where possible, configured as such. Since older grids will be gradually replaced, this update allows for the maintainability of the behavior you are used to.
15 +** Unfortunately, The above change resulted in a behavior shift when selecting one or multiple rows in a grid (for example, in the trigger overview). Previously, clicking on the whole row resulted in the selection of the row. Now only checking the checkbox results in a row selection.
16 +* Create - Transformation: In the Transformation tab of the Create phase, conditional operators can be added for transformations that have multiple attributes as a source . (#1272)
17 +* Deploy - Machine: We have updated the default network deployment strategy for Windows machines, which might affect your machines. When you access the Deploy phase, you will see the list of machines required for redeployment. Redeploying your machine will ensure you benefit from these enhanced network capabilities.
18 +* Deploy - History: Deploy releases history tab better renders the information on the screen.
19 +** Additionally, we have updated the "Export to Excel" button to reflect the latest functionality. As a result, there is no longer a limit to how many rows can be exported. (#1601)
20 +* Deploy - General: We have implemented performance improvements to the Deploy phase. The larger the model, the more notable the improvements.
21 +* eMagiz Connector - General: We released a new patch version of the eMagizConnector in the Mendix marketplace. It includes some small changes to the naming conventions to remove the ACR violations.
39 39  
40 40  ====Bug fixes====
41 41  
42 -* Design - Solution design: We hide systems without functional integration now. (#714)
43 -* Create - API Gateway: Security header case insensitive
44 -* Create - Flow designer: Enabling redelivery for you integration is applied after resetting your offramp and exit flow. Before this change, you needed to remove and add the integration to Create phase to apply this setting.
45 -* Deploy - Containers: Applied styling to the error pop-up with the list of reasons why a runtime can’t be deleted to make it easier to read. (#546)
46 -* Deploy - Architecture: Deploying your model to the cloud for the first time, required you to press ‘Apply to Environment’ twice. This is no longer the case. (#508)
47 -* Deploy-Volumes: Network volumes visible when container not deployed.
48 -* Manage - Monitoring: Fix typo in Event Proccessors Metrics. (#835)
49 -
50 -====Remarks====
51 -
52 -* Mendix Runtime has been upgraded to Mendix 9.21.0.
53 -
25 +* Design - System Message: Using the "save and create new attribute" button in the system message tab of the design phase will not open a "new attribute" window until the previous attribute’s details are properly entered and saved. (#1650)
26 +* Create - Transformation: Help text appears for relevant attributes when creating a new transformer in the transformation tab of the create phase. (#1352)
27 +* Catalog - General: The content inside the “used by integrations” table for the topic catalog is properly rendered to be more readable for systems with longer names. The title represents the content of the table. (#1224)
28 +* Create - Transformation: Date/time transformer pop-ups in the Transformation tab of the Create phase are rendered in a format that allows editing when in edit mode. (#1642)
29 +* Infra - Runtime Image: Support for the ‘NTCredentials’ authentication method in a custom HttpComponentsMessageSender support object has been reintroduced.
30 +* Infra - Runtime Image: In some edge cases, log messages produced with the Logging channel adapter component did not end up in the Manage phase. This issue is now resolved.