Changes for page 225 - Pop-up Party

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-198 - Great Migration
	1	+220 - Patch Parade

Author

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

Content

...	...	@@ -1,27 +1,14 @@
1		-Another couple of weeks have passed, so it is time for a new release. We have focused in this period on improving the migration process towards the next-generation architecture as well as how the user experience and interaction with the next-generation architecture works.
	1	+In the last sprint cycle, we have worked on a new runtime image LINK that contains a fix for an issue regarding SFTP sessions. Furthermore, we did several small improvements and many bug fixes.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.220 - Patch Parade||target="blank"]].
4	4
5	5	=====New features=====
	6	+Capture - Integrations: Information about the integration pattern of a selected message type has been added to the new integration pop-up. (#1214)
	7	+Create - Flow designer: A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
	8	+Deploy - Releases: Search boxes in the properties overview are now shown by default. (#1325)
	9	+Manage - History: All events that relate to message queues (delete message, delete all messages or delete queue) are now logged in the Manage phase instead of the Deploy phase. (#1278)
6	6
7	7
8		-=====Minor changes=====
9		-
10		-* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
11		-* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
12		-* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
13		-* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
14		-* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
15		-* Deploy - Architecture: You can apply your changes to environment without having an active release.
16		-* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
17		-(control tower, so Gen3 only)
18		-* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
19		-
20		-====Bug fixes====
21		-
22		-* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models.
23		-* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
24		-
25		-====Remarks====
26		-
27		-* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
	12	+=====Bug fixes=====
	13	+Design - Message mapping: It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. (#1179)
	14	+Create - Flow designer: It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. (#852)