Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/04/22 14:08
From version 238.1
edited by Erik Bakker
on 2025/03/27 09:08
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 -241 - Wild West
1 +243 - Migration Magic
Content
... ... @@ -1,41 +1,30 @@
1 -In the last sprint, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] containing a much-needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.
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.241 - Wild West.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 5  ====New Features====
6 6  
7 -* Deploy - Releases: A comparison feature for the Deploy phase is added. The comparison feature allows users to compare releases to track the differences in property values of those releases. The feature also provides information on who made the changes. The differences are categorized by “InRelease” and “NotInRelease,” which means that the additional property value is either in the first selected release (InRelease) or the second selected release (NotInRelease).
8 -** This functionality only works for releases created **after** this release.
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.
9 9  
10 10  ====Minor Changes====
11 11  
12 -* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
13 -* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture because this field was not visible enough in the rest of the portal. (#1608)
14 -* Capture / Design: For new systems, message types, machines, tenants, and models, hyphens are **no longer allowed** in the technical name. The technical name can only consist of lowercase letters and digits and must start with a letter. This also applies to systems, message types, and tenants that have not yet been transferred from design to creation. The portal will give an error message while transferring, and the hyphen has to be removed manually.
15 -* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
16 -* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
17 -* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
18 -* Infra - Security: Improved security by implementing additional safeguards for AWS native services.
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.
19 19  
20 20  ====Bug fixes====
21 21  
22 -* Capture - Add System: A loading bar is displayed before showing the pop-up when a user tries to create or edit a system. (#1228)
23 -* Capture - Edit System: When editing a system, the validation now considers that the name cannot be an empty string. (#1562)
24 -* Design - Message Definition: Two minor improvements are introduced:
25 -** The widget prevents users from adding the same message attribute within a message definition multiple times.
26 -** When adding a new message entity within your message definition and expanding the existing message definition, it doesn’t throw an exception when the user presses the Save button multiple times in a short time frame.
27 -* Design - Catalog: When creating the Swagger JSON, all custom examples users add will be shown correctly when displaying the Swagger. (#1597)
28 -* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513)
29 -* Create - Add Integrations: Users can untransfer a flow even when there is a property attached to the flow. (#1590)
30 -* Create - Add Integrations: When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned.
31 -* Create - Components: The browser page now displays the correct page title (#1509)
32 -* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
33 -* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560)
34 -* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already an existing property description. (#1526)
35 -* Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
36 -* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore moves the user to the queue browser of the correct environment. (#1408)
37 -* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed. (#1550)
38 -
39 -====Remarks====
40 -
41 -* New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with **Java 21**, and functionality works as expected.
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.