Changes for page 240 - Spring Cleaning

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-238 - Preparation Paraside
	1	+217 - Template Tango

Author

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

Content

...	...	@@ -1,12 +1,17 @@
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.
	1	+In the last sprint cycle, we focused on delivering new cloud templates for docker single and docker double lane. Moreover, we have added clipboard buttons to several pages, and migrated the generic alert trigger "More than 100 messages on queue over 10 minutes" to a custom trigger. Lastly, we enabled the removal of eMagiz infra H2 databases for connector machines, and improved the checks on the runtime versions in the runtime overview.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.238 - Preparation Paradise.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.217 - Template Tango||target="blank"]].
4	4
5		-====Minor Changes====
	5	+=====New features=====
6	6
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]].
	7	+* Create - Flow Designer & Deploy: Copy to clipboard buttons have been added to various pages.
	8	+* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce the ability to clean H2 databases from the portal. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
	9	+* Manage - Alerting: The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger.
9	9
	11	+=====Minor changes=====
	12	+
	13	+* Deploy - Architecture: For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note that only H2 databases that are registered under the standard eMagiz data folder will be removed. Moreover, it is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. Lastly, for on-premise runtimes, only a reset of the runtime is needed.
	14	+
10	10	====Bug fixes====
11	11
12		-* Create - Add Integrations: Integrations using the entry/exit connector, using the same message type, can now be untransferred from the create phase. (#1591)
	17	+* Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)