Changes for page 247.1 - Help Out

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-207 - Aligned State
	1	+246 - Preparation Paradise

Author

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

Content

...	...	@@ -1,23 +1,18 @@
1		-In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
	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.207 - Aligned State .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		-=====Minor changes=====
	5	+====Minor Changes====
6	6
7		-* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively.
8		-* Design - Message Mapping: The button 'Import from Store' will directly open the store.
9		-* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking.
10		-* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
11		-* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
	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.
12	12
13		-
14		-
15	15	====Bug fixes====
16	16
17		-* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable.
18		-
19		-
20		-
21		-=====Infra and image changes=====
22		-
23		-* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.
	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)