Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 245.1
edited by Erik Bakker
on 2025/04/22 10:58
Change comment: There is no comment for this version
To version 141.1
edited by Carlijn Kokkeler
on 2023/10/23 16:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -243 - Migration Magic
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,30 +1,29 @@
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 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.
1 +In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.243 - Migration Magic.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
4 4  
5 -====New Features====
5 +=====Minor changes=====
6 6  
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.
7 +* Design - Message Mapping: The button 'Import from Store' will directly open the store.
8 +* Design - Performance: Performance improvements for the Flow Designer have been implemented.
9 +* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
10 +* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
11 +* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
12 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
13 +* Manage - Data Sink: Data sink page has been moved to the “Explore” tab. (#946)
14 +* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
15 +For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
16 +The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
17 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
18 +* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
9 9  
10 -====Minor Changes====
20 +====Bug fixes====
11 11  
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.
22 +* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
23 +* Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term.
22 22  
23 -====Bug fixes====
24 24  
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.
26 +
27 +=====Infra and image changes=====
28 +
29 +* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.