Changes for page 220 - Patch Parade

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-220 - Patch Parade
	1	+211 - Log Luminary

Content

...	...	@@ -1,25 +1,27 @@
1		-In the last sprint cycle, we have worked on a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] that ensures that Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. Furthermore, we did several small improvements and many bug fixes.
	1	+In the last sprint cycle, we focused on improving several aspects related to overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.220 - Patch Parade||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]].
4	4
5		-===== New features =====
	5	+=====New features=====
6	6
7		-* Capture - Integrations: Information about the integration pattern of a selected message type has been added to the new integration pop-up. (#1214)
8		-* Design - Architecture: When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted. (#1296)
9		-* Design - Message mapping: It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. (#1179)
10		-* Create - Flow designer: A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
11		-* Deploy - Architecture: Changes can now be deployed on SSL level without creating a new version of a flow in Create.
12		-* Deploy - Releases: Search boxes in the properties overview are now shown by default. (#1325)
13		-* Manage - Explore: We fixed an issue where navigating to the “Explore” tab in “Manage” phase would sometimes redirect users to the homepage.(#1237)
14		-* Manage - History: All events that relate to message queues (delete message, delete all messages or delete queue) are now logged in the Manage phase instead of the Deploy phase. (#1278)
	7	+* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
	8	+* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
15	15
16		-===== Bug fixes =====
	10	+=====Minor changes=====
17	17
18		-* Create - Flow designer: It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. (#852)
19		-* Create - Flow designer: The copy to clipboard button now copies the actual value of passwords instead of the masked value of them. (#1303)
20		-* Deploy - Architecture: Machines deleted in Design are excluded from the memory health check. (#1282)
21		-* Deploy - Architecture: Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] has been released.
22		-* Deploy- Deployment plan: We have implemented changes that should prevent the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) to not correspond with the actual execution of relevant steps. (#1315)
23		-* Manage - Explore: Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. (#1287)
24		-* Manage - Overview pages: We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. (#1122)
25		-* Manage - Redelivery: We fixed an issue where a large message would be shown at the bottom of the Redelivery page instead of the right side of the page. (#1290)
	12	+* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
	13	+* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
	14	+* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
	15	+* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
	16	+* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
	17	+* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
	18	+
	19	+====Bug fixes====
	20	+
	21	+* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
	22	+* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
	23	+* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
	24	+* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
	25	+* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)
	26	+
	27	+