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	+194 - Giant Leap

Author

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

Content

...	...	@@ -1,33 +1,24 @@
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	+The release introduces various improvements on our 3rd generation runtime architecture and various other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
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.194 - Giant Leap.WebHome||target= "blank"]].
4	4
5	5	=====New features=====
6	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.
	7	+* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V130.WebHome||target="blank"]].
	8	+* Design - Settings: We added XML support to API Management. To enable this feature, change the 'Default message format' in the Design settings section. You can change individual operations by changing the message format of your gateway message. Migrating existing operations requires a reset of the exit flow and a change in the catalog in Design. For more information, see the release blog post. (#815)
	9	+* Deploy - Releases: New release properties pop-up that shows all properties in your release, grouped by containers that they are assigned to. This pop-up can be accessed by pressing the wrench-shaped icon, which becomes available once a release is set as active.
10	10
11	11	=====Minor changes=====
12	12
13		-* Deploy - Releases: We sped up the process of preparing runtime images in executing 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.
	13	+* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
	14	+* Design - API Catalog: When you change a path in the Design phase, your HTTP inbound gateways that use the changed path will also be updated in Create phase if you have edit rights. (#524)
	15	+* 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.
	16	+* Manage - Error messages: Message history is sorted by timestamp descending.
17	17
18	18	====Bug fixes====
19	19
20		-* Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms 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 of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been 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.
24		-
25		-====Infra and image changes====
26		-
27		-* Infra: New logging feature enabling us to make better choices in encryption standards.
28		-
29		-
30		-
31		-
32		-
33		-
	20	+* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming. (#908)
	21	+* Create - Migration: We fixed a third-generation migration issue where the legacy error handling flow components were not removed from the asynchronous routing flow.
	22	+* Create - Flow designer: when migrating a container’s flows from gen2 to gen 3, “global wire tap” components and their relevant components will be removed.
	23	+* Deploy - Release: We fixed an issue that caused images not to be built in specific situations when running in the new runtime generation runtime.
	24	+* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)