Changes for page 247.1 - Help Out

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-238 - Preparation Paraside
	1	+246 - Preparation Paradise

Content

...	...	@@ -1,12 +1,18 @@
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 our previous release, we released functionality to increase the stability of Windows runtimes. This time, we followed that up by adding additional safety measures on the runtime level. Additionally, we have several pieces now available to prepare for pending changes to our event streaming offering. Furthermore, we introduced several minor improvements to the platform.
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.246 - Preparation Paradise.WebHome||target= "blank"]].
4	4
5	5	====Minor Changes====
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	+* Deploy - General: Updated the Java arguments applied to Windows containers to align with the container limits, thereby improving the stability of these containers.
	8	+* Deploy - Architecture: You can now manually set the memory of your on-premise machine in design architecture. This memory is considered when checking the machine's health in "Deploy architecture."
	9	+* General - Runtime: We have two updates on the runtime level.
	10	+** A new [[runtime image>>doc:Main.Release Information.Runtime Images.V331.WebHome||target="blank"]] is available that adds support for consuming Kafka topics based on a ‘topics’ pattern instead of a fixed list of topic names.
	11	+** A new runtime version that updates our Java runtime version from Java 17.0.13 to Java 17.0.15. This is primarily a security update.
9	9
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)
	15	+* Create - Flow designer: We have fixed a bug where you could not add a new entry flow to a ‘SOAP Entry Connector’ enabled system.
	16	+* Manage - Error Messages: The non-working download button for payload content files now displays a more descriptive error message text. (#886)
	17	+* Manage - Explore (Queue Browser): Updated styling for the action buttons related to the debug functionality. (#1653)
	18	+* Q&A Forum - General: You will no longer receive an email notification about your comments on posts in the Q&A forum. (#1462)