Changes for page 204 - Found It

Summary

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

Details

Page properties

Content

...	...	@@ -1,34 +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 finishes up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs and some minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
2	2
3	3	Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.WebHome||target="blank"]].
4	4
5	5	=====New features=====
6	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.
7	7
8	8	=====Major changes=====
9	9
10		-* Store - Private store. This release introduces the private store with the following features:
11		-** Store items will be private by default and are only accessible for users that belong to the same company as the user that exported the store content. Note that the store item needs to be approved before it is visible to users.
12		-** A new user role, "Store Exporter," will be introduced and can be assigned to the users who can create and update store items.
13		-** Approval of a store item will be executed by eMagiz personnel, who can also set a store item to be public.
14		-** Public store items will be importable by all users.
	11	+* Manage - Redelivery: You are able to explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Beside that, you are also able to redeliver the message(s) in this page.
15	15
16	16	=====Minor changes=====
17	17
18		-* Create - Event Streaming: Event streaming is now available for models migrating to the 3rd generation runtime.
19		-* Create - Transformation: source filter on attribute with empty field is more readable in read-only mode. (#732)
20		-* Create - Migration: Improved compatibility checks related to the 3rd generation runtime migration.
21		-* Deploy - Check properties: Informative error messages when saving or creating a property. (#576)
22		-* Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps.
23		-* Deploy - Architecture: Added reset feature for 3rd generation runtimes.
	15	+* Design - System message: 'Request' and 'Response' entities are generated and set as root entities automatically 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 user can use it to compare with the previous versions.
	18	+* Create - Flow Designer: when importing store item from another partner, a error popup will be shown instead of default error message.
	19	+* Deploy - Releases: The activate release functionality gained a performance improvement for gen 3 models.
	20	+* Deploy - Architecture: Before apply to environment, we require a confirmation from you if those are some breaking changes that may cause issues in 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 - When activating a release you will be reminded of empty runtimes. Empty runtimes are runtimes without flows in the release. These runtimes should be removed from your architecture.
24	24
25	25	====Bug fixes====
26		-* Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows.
27		-* Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances.
28		-* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish.
29		-* Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798)
30		-* Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment.
31		-* Deploy - Architecture: 3rd generation runtimes are included in runtime checks while upgrading your cloud environment.
	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 copy and paste, 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 setup step.
	29	+* Deploy - Containers: We fix 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. New menu item "Deploy agent" is added and visible for all users to show the command which can be uses to deploy agent on premises machine.
32	32
33		-====Remarks====
34		-* Mendix Runtime has been upgraded to Mendix 9.19.0.