Changes for page 220 - Patch Parade

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Max Verstappen
	1	+201 - Be Informed

Author

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

Content

...	...	@@ -1,33 +1,30 @@
1		-In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
	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.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.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		-=====New features=====
6		-
7		-* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties.
8		-* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9		-* All - The next generation architecture is the default now. New models will use this generation as default.
10		-
11	11	=====Minor changes=====
12	12
13		-* Deploy - Releases: We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
14		-* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
15		-* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
16		-* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
	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	17
18	18	====Bug fixes====
19	19
20		-* Create - Flow Designer: An issue has been fixed in the flow designer where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
21		-* Create - Flow Designer: We added a migration step to set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
22		-* Deploy - Deployment plan: We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped.
23		-* Manage - Monitoring - We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that has just migrated to the next generation architecture.
	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)
24	24
25		-====Infra and image changes====
	27	+=====Infra and image changes=====
26	26
27		-* Infra: New logging feature enabling us to make better choices in encryption standards.
28		-
29		-
30		-
31		-
32		-
33		-
	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.