Changes for page 188 - Close Encounters

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+185 - Get Ready

Author

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

Content

...	...	@@ -1,22 +1,23 @@
1		-The release brings several improvements to our 3rd generation runtime and its interaction with the portal. On top of that, we have several feedback items and bug fixes.
	1	+Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.185 - Get ready.WebHome||target="blank"]].
4	4
5		-====Minor changes====
	5	+=====New features=====
	6	+* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
6	6
7		-* General: Code mapping is now available for models migrating to the 3rd generation runtime.
8		-* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785)
9		-* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you.
10		-* Deploy - Deployment plan: For 3rd generation runtimes we have changed the restart behavior in case of startup problems. This means that when a runtime is being deployed, which is constantly crashing and thereby causing problems, the restart of the runtime is limited to just five times. (#720)
11		-** After five times, the runtime will remain in the stopped state.
	8	+=====Minor changes=====
12	12
13		-====Bug fixes====
14		-* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717)
15		-* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
16		-* Deploy - Deployment plan: Before when you tried to deploy a Release via the Deploy functionality the widget could crash randomly. With this fix we ensured the widget will always load correctly. (#362)
17		-* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
18		-* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
19		-* Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture.
	10	+* Design System. Changed the look and feel across the portal altogether. Changes can be seen in:
	11	+ ** Datagids, where there is now on hover action for example.
	12	+ ** Pop ups
	13	+ ** Context menus, also have on hover action
	14	+ ** Styling of scrollbars
	15	+* Message Redelivery - admin logs improved to better analyze issues when they occur
	16	+* Create - Flow Designer: small bugs ( copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
20	20
21		-====Remarks====
22		-* Mendix Runtime has been upgraded to Mendix 9.19.0.
	18	+====Bug fixes====
	19	+* Deploy - Deployment plan. Performance of page to deploy a release increases significantly
	20	+* Store - Import resources was incorrectly done in specific cases, which is now fixed
	21	+* Store - Target namespace will be imported when imported XML Message Definition
	22	+* Store - When exporting components, if property values contains bus name, they will be updated automatically with new bus name when importing into a new bus.
	23	+* Store: Importing items from the store sometimes resulted in invalid JMS connection factories.