Changes for page 203 - Fast Paced

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-189 - Private Eye
	1	+190 - Fast Forward

Content

...	...	@@ -1,24 +1,32 @@
1		-The release brings a private store to our community and makes the latest runtime image available for our customers running on the 3rd generation architecture. Furthermore, we introduce several improvements to our 3rd generation runtime and its interaction with the portal.
	1	+The release finished many new improvements to our 3rd generation runtime offering and fixed various annoying bugs and minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.189 - Private Eye.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.WebHome||target="blank"]].
	4	+
4	4	=====New features=====
5		-* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Release blog>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
	6	+* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
	7	+* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your JMS server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
6	6
	9	+=====Major changes=====
	10	+
	11	+* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
	12	+
7	7	=====Minor changes=====
8	8
9		-* General: Code mapping is now available for models migrating to the 3rd generation runtime.
10		-* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785)
11		-* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you.
12		-* 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)
13		-** After five times, the runtime will remain in the stopped state.
	15	+* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes.
	16	+* Create - Flow designer: sensitive information stored in property values is masked. (#790)
	17	+* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions.
	18	+* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
	19	+* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
	20	+* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828)
	21	+* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
	22	+* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
	23	+* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
14	14
15	15	====Bug fixes====
16		-* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717)
17		-* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
18		-* 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)
19		-* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
20		-* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
21		-* 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.
	26	+* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
	27	+* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793)
	28	+* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
	29	+* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
	30	+* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
	31	+* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
22	22
23		-====Remarks====
24		-* Mendix Runtime has been upgraded to Mendix 9.19.0.