Changes for page 204 - Found It

Summary

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

Details

Page properties

Content

...	...	@@ -1,32 +1,32 @@
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.
	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	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	+* 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.
8	8
9	9	=====Major changes=====
10	10
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.
	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	12
13	13	=====Minor changes=====
14	14
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.
	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	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)
	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	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.
	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.
24	24
25	25	====Bug fixes====
26	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)
	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	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.
	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.
32	32