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		-201 - Be Informed
	1	+205.1 - World Explorers

Author

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

Content

...	...	@@ -1,30 +1,9 @@
1		-In the last sprint cycle, we focused on planning the upcoming quarter, finishing up, and working on the Hackathon to fix several smaller items.
	1	+This release signifies our efforts to stabilize the management of our customer models from Manage even better. 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.201 - Be Informed.WebHome||target= "blank"]].
	3	+====Minor changes====
4	4
5		-=====Minor changes=====
	5	+* Manage - Alerting - Triggers: The non-editable trigger for Event streaming topic size has been changed to trigger on 95% of the configured size instead of 80%
	6	+* Manage - Monitoring: Viewing runtime, queue, and HTTP statistics are now limited to 7 days at a time. (Gen3 only)
	7	+* Manage - Queue statistics: They are now all visible for models with a vast number of queues. This used to be cut off. (Gen3 only)
	8	+* Manage - Monitoring: Removed time filter options for time windows longer than the last seven days in 3rd generation runtime statistics dashboards.
6	6
7		-* Portal - Menu: The back button is changed to have text on it to make the navigation much clearer. (#949)
8		-* Design-Architecture: Topic Storage detail page contains help text. (#994)
9		-* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832)
10		-* Design - API Gateway: Small styling improvement on the "Edit integration page." (#954)
11		-* Create - Flow Designer: When deleting one or multiple components, you cannot change the selection before confirming or canceling the delete action. (#969)
12		-* Create - Migrate to 3rd Generation: If one or more flows break during migration, a popup will inform the flows containing errors after the migration. (#983)
13		-* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979)
14		-* Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown. All changes made in the portal that will affect your running environment are listed here. These changes can be applied to the environment or reverted. (#828)
15		-** Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release.
16		-** Changes with a direct effect will not be listed (for example, restarting a machine).
17		-
18		-====Bug fixes====
19		-
20		-* Design - Solutions: We fixed an issue that displayed a message mapping error despite having a passthrough API gateway. (#935)
21		-* Design - Settings: The full length of the contract number can now be registered. (#958)
22		-* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen 3 will not block migration. (#982)
23		-* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990)
24		-* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972)
25		-* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
26		-
27		-=====Infra and image changes=====
28		-
29		-* Changed the endpoint for sending error messages to the eMagiz Control Tower.
30		-* Updated the Spring version of the gateway supporting deploy and manage phase operations.