Changes for page 225 - Pop-up Party

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-212 - Failover Fiesta
	1	+219 - Creation Carousel

Content

...	...	@@ -1,27 +1,13 @@
1		-In the last sprint cycle, we focused on ....
	1	+In the last sprint cycle, we focused on releasing new [[environment templates>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for docker single and double lane. Moreover, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] that contains a fix regarding SFTP sessions. Furthermore, we worked on new version of our eMagiz Mendix connector to support Mendix version 10 and higher. Lastly, we did several bug fixes.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Feedback Fiesta||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.218 - Sprightly Spring||target="blank"]].
4	4
5	5	=====New features=====
6	6
7		-* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
8		-* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
	7	+* Architecture: Several components are affected by the migration to Spring 6. Please check out our [[release blog>>Main.Release Information.Release Blogs.218 - Sprightly Spring||target="blank"]] for specifications.
	8	+* Architecture: Moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]].
9	9
10	10	=====Minor changes=====
	11	+* Manage - Monitoring: Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
	12	+* Deploy - Cloud: Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
11	11
12		-* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13		-* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
14		-* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
15		-* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
16		-* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17		-* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
18		-
19		-====Bug fixes====
20		-
21		-* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
22		-* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
23		-* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
24		-* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
25		-* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)
26		-
27		-