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	+195 - Easter Party

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	+As the quarter has ended, we went silent for a couple of weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple 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.195 - Easter Party.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	+* General - Control Tower: Changed several generic triggers for more predictable behavior.
	8	+* Administration - License Tracker: The license tracker has been updated for new license models and features.
	9	+* Administration - License Tracker: When the feature ‘Data sink’ is enabled, the number of message packs of the contract will be displayed when you hover with the mouse over the feature.
	10	+* Capture - Settings: Editing message types are now consistent between new and existing ones. (#884)
	11	+* Design - API Gateway: Default HTTP responses are generated automatically (#417)
	12	+* Design - Solution design: An additional option is added to the context menu that navigates to the message definition added to event streaming topics without processors. (#850)
	13	+* Create - Add Integrations: We used the name of the API integration that you set in the Design phase to display on the Transfer screen. That helps you choose the correct integrations to add to the Create phase more quickly.
	14	+* Create - 3rd Generation Migration: You can toggle the custom error handling option for your event processors while migrating your event processing container to the 3rd Generation Runtime.
	15	+* Deploy - Deployment plan: When you run your deployment plan in your model using the new generation runtimes, you will be able to be the logs that relate to an executing deployment step.
	16	+* Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan.
	17	+* Deploy - Architecture: Certificates only editable by system admin.
	18	+* Manage - Jobs: In case the model has containers that contain jobs in one of its flows, users can inspect job managers, job executions, and job step executions. Note that this only works for the 3rd generation runtime.
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.
	22	+* General - Runtime Image: 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.V140.WebHome||target="blank"]].
	23	+* Design - API Gateway: Improved generation of Open API JSON and example messages for API gateway operations to handle cases where an element in your gateway definition is used multiple times. (#440)
	24	+* Design - API Gateway: We fixed an issue where changing the message format of a gateway message did not result in an update of the OpenAPI (i.e., Swagger) document.
	25	+* Design - System message: We fixed an issue that led to importing towards the wrong message definition when the option "Import from XSD" was chosen on a synchronous message. (#818)
	26	+* Create - Message: When viewing or editing an enumeration, it is no longer deleted when the cancel button is pressed.
24	24
25		-====Infra and image changes====
	28	+====Remarks====
26	26
27		-* Infra: New logging feature enabling us to make better choices in encryption standards.
28		-
29		-
30		-
31		-
32		-
33		-
	30	+* Deploy - Releases: We removed the existing snapshots of release property values.