Changes for page 237.1 - Fabulous Flow

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-197 - Pay Attention
	1	+206 - Wrap Up

Author

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

Content

...	...	@@ -1,22 +1,15 @@
1		-Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments.
	1	+This release signifies our efforts to wrap up our quarter. It consists of several much-needed functionalities for specific use cases regarding the next-generation architecture.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.197 - Pay Attention.WebHome||target= "blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Wrap Up.WebHome||target="blank"]].
4	4
5		-=====New features=====
6		-* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
7		-* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
8		-
9	9	=====Minor changes=====
10	10
11		-* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated.
12		-* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute."
13		-* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments.
	7	+* Deploy - Releases: The related unused images in the on-premises machines will also be removed when the release is removed.
	8	+* Create - Transfer settings from Design: Added a migration step. If the custom error handling is set to false, we set the error channel to “errorChannel” for all inbounds in a flow.
	9	+* Create - Transfer settings from Design: Added a check in the migration that validates whether every targetNamespace is filled in when a SOAP web service is migrated and split as part of the migration to the next-generation architecture.
	10	+* Create - Transfer settings from Design: Added a check in the migration that validates whether a specific old component, the Jetty server support object, remains in a flow after the migration. If so, the user is notified that they need to take action on this.
14	14
15		-====Bug fixes====
	12	+=====Infra and image changes=====
16	16
17		-* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item.
18		-* Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952)
19		-* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947)
20		-* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
21		-* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again.
22		-* Design - Message Definitions: "Message format" button is also available in view mode. (#919)
	14	+* New logging feature enabling us to make better choices in deprecating old encryption standards.
	15	+* Carwash change to enable our direct connect offering for customers on the next-generation architecture.