Changes for page 220 - Patch Parade

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-207 - Aligned State
	1	+201 - Be Informed

Author

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

Content

...	...	@@ -1,27 +1,30 @@
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 the last sprint cycle, we focused on planning ahead, finishing up and working on the Hackathon to fix several smaller items.
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.201 - Be Informed.WebHome||target= "blank"]].
4	4
5	5	=====Minor changes=====
6	6
7		-* Design - Message Mapping: The button 'Import from Store' will directly open the store.
8		-* Design - Performance: Performance improvements for the Flow Designer have been implemented.
9		-* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
10		-* 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. (#1045)
11		-* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
12		-* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
13		-* Manage - Data Sink: Data sink page has been moved to the “Explore” tab. (#946)
14		-* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
15		-* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
16		-* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
	7	+* Portal - Menu: the back button is changed to have text so it shows clearer the navigation target. (#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 improvements to the edit integration page. (#954)
	11	+* Create - Flow Designer: When deleting one or multiple components, you will not be able to change the selection before confirming or cancelling the delete action. (#969)
	12	+* Create - Migrate to 3rd Generation: In the event one or more flows break during migration, a popup will inform the fows containing errors after migration is finished. (#983)
	13	+* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to environment. (#979)
	14	+* Deploy-Architecture: Upon pressing the button “Apply to environment”, a confirmation page is shown. Here all changes made in the portal that will have an effect in your running environment are listed. These changes can be applied to environment or reverted. (#828)
	15	+** Changes made in Deploy Architecture with an effect to 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	17
18	18	====Bug fixes====
19	19
20		-* 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. (#1055)
21		-* Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term.
	20	+* Design - Solutions: We fixed an issue that a message mapping error is displayed 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 Gen3 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 you 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)
22	22
23		-
24		-
25	25	=====Infra and image changes=====
26	26
27		-* 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.
	29	+* Changed the endpoint that is used for sending errormessages to the eMagiz Control Tower.
	30	+* Updated the Spring version of the gateway supporting deploy and manage phase operations.