Changes for page 243 - Migration Magic

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-197 - Pay Attention
	1	+243 - Migration Magic

Content

...	...	@@ -1,26 +1,30 @@
1		-Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments.
	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.197 - Pay Attention.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 - 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.
7		-* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
	5	+====New Features====
8	8
9		-=====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.
10	10
11		-* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated.
12		-* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute."
13		-* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments.
	10	+====Minor Changes====
14	14
	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	+
15	15	====Bug fixes====
16	16
17		-* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item.
18		-* Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952)
19		-* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947)
20		-* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
21		-* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again. Note that to make this functionality available a new "base image" was created which will automatically be applied to all gen two karaf containers when you create a new release and deploy it via the deployment plan causing redeployments.
22		-* Design - Message Definitions: "Message format" button is also available in view mode. (#919)
23		-
24		-====Remarks====
25		-
26		-* Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture. Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off.
	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.