Changes for page 243 - Migration Magic

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+238 - Preparation Paraside

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.CarlijnKokkeler
	1	+XWiki.ebakker

Content

...	...	@@ -1,26 +1,12 @@
1		-In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
	1	+In the last sprint, we focused on finishing the first iteration of our new eMagiz Mendix Connector and the first iteration of our new base image. We will first utilize the new eMagiz Mendix Connector to get an even better feeling of its performance, but you will notice a UI change straightaway. Once we have passed that hurdle, we will share more information about it and release it to a broader range of customers. Regarding the base image, we will now introduce this to our flow testing offering to see if anything unexpected happens. This is an additional safety measure we have put in place to reduce the chance of something breaking in your model once the new base image is released. On top of that, we have some minor updates to improve the quality of the platform.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.238 - Preparation Paradise.WebHome||target="blank"]].
4	4
5		-=====New features=====
	5	+====Minor Changes====
6	6
7		-* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
	7	+* ILM: We defined the systems labeled as “isMendix” with the “MX“ icon, making it easier to identify the Mendix system.
	8	+* Create - Flow Testing: As we are finalizing the new eMagiz runtime image that will update the Spring version to Spring boot 3.4.1 and Java to 17.0.13, we are now bringing these latest updates to flow testing. This means that any flow test you execute will run on the base image your runtimes will run on after the release of the new eMagiz runtime image. If one of your test cases suddenly exhibits weird behavior that you think is due to the update, feel free to contact us via our [[support department>>mailto:support@emagiz.com]].
8	8
9		-=====Minor changes=====
10		-
11		-* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
12		-* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
13		-* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052)
14		-
15		-
16	16	====Bug fixes====
17	17
18		-* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
19		-* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
20		-* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
21		-* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
22		-
23		-
24		-=====Infra and image changes=====
25		-
26		-* No infra and/or image changes is this release.
	12	+* Create - Add Integrations: Integrations using the entry/exit connector, using the same message type, can now be untransferred from the create phase. (#1591)