Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+190 - Fast Forward

Content

...	...	@@ -1,25 +1,32 @@
1		-The release brings several improvements to our 3rd generation runtime and the interaction with it. On top of that, we have several feedback items and bug fixes.
	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.188 - Close Encounters.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
5	5	=====New features=====
6		-* Design - Store: It is now possible to import Transformations and Data Models from the store into a model.
7		-** The Design Store can also be opened from the Mapping and Data Model screens.
8		-** The Design Store now offers search options for store items, including Transformations and Data Models.
9		-** When importing a Store item with a Transformation or Data Model, a new merge tool is available to link the Store Items data model to the users' data model or to add new attributes/entities to the user data model.
10		-** When importing a Store item with a data model that has been previously linked, the links are automatically restored, allowing for easy updating of store-based Integrations and easier installation of multiple Store items with the same data model.
	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.
11	11
12		-=====Minor changes=====
	9	+=====Major changes=====
13	13
14		-* Create - Flow Designer: Code mapping is now available for models migrating to the 3rd generation runtime
15		-* Create - eMagiz Mendix Connector exit: Download buttons are added for non-legacy eMagiz Mendix connectors.
16		-* Create - Overview: You will now see your errors within a flow but on the Create - Overview. To activate this, open your flow, and the number of errors you have in it, if any, will update so that next time, you don't have to navigate inside the flow to check how many alerts you have.
	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.
17	17
	13	+=====Minor changes=====
18	18
	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.
	24	+
19	19	====Bug fixes====
20		-* Design - Store: Importing store items from response messages doesn't cause issues anymore.
21		-* Design - Store: Importing response messages and transformation to API integration is possible.
22		-* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document. (#783)
23		-* Create - Flow Designer: Ensure that the copy and pasting experience works for all flows.
24		-* Create - Flow Designer - Store: We fixed the maintaining selection of flow fragments from the store.
25		-* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed. (#744)
	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.
	32	+