Changes for page 262 - Good News

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-190 - Fast Forward
	1	+257 - Changing Chameleon

Content

...	...	@@ -1,32 +1,33 @@
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.
	1	+This release features various updates to our platform, with our new event streaming broker running on DSH taking center stage. With this release, our latest event streaming functionality will be available to everyone (GA). On top of that, we will launch the previously announced new [[runtime image>>doc:Main.Release Information.Runtime Images.V341.WebHome||target="blank"]] for **all** customers. On top of that, we have several smaller features and bug fixes for you to enjoy.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.257 - DSH Delight.WebHome||target="blank"]].
4	4
5		-=====New features=====
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.
	5	+==== New features ====
8	8
9		-=====Major changes=====
	7	+* General - Event Streaming: The KPN DSH event streaming broker has been set as the default event streaming broker for models that start using event streaming for the first time. Please get in touch with your partner manager about the possibilities of using event streaming in your models.
	8	+* General - Runtime Image: A new runtime image is introduced that fixes several issues reported by customers, updates the Java version, and prepares all models for migration to our MAM feature if they are ready.
10	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.
	10	+==== Minor changes ====
12	12
13		-=====Minor changes=====
	12	+* Event Streaming - Data Retention: When DSH retention time is changed on the company level, deleting the topic by excluding it in Design > Architecture and applying the change in Deploy > Architecture and including it again in Design > Architecture and applying the change in Deploy > Architecture results in the retention time being updated in DSH.
	13	+** Note that this action will delete the topic and therefore will result in **data loss**.
	14	+* Design - System: Importing an Open Specification V2 has been deprecated, and it’s not supported anymore at eMagiz.
	15	+* Design - System Message: Users can go from Design to the Create phase for all message types. (#1607)
	16	+* Create - Flow testing: The properties that start with “emagiz.dsh“ are provided with a value automatically in the background.
	17	+* Deploy - Releases: In case of activating a new release and there is trouble at the step of creating new certificates, the previous valid certificate will be reused.
14	14
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	24
25		-====Bug fixes====
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.
	20	+==== Bug fixes ====
32	32
	22	+* Create - Flow Designer: Users are correctly redirected to their request/response message based on the XSD they are selecting in the flow. (#1555)
	23	+* Create - Transformation - Value mappings for a “string to enumeration” transformer are now visible after reopening the window. (#1715)
	24	+* Create - System Message: The navigation from Create to Design has been fixed for event streaming. Additionally, improvements have been made for synchronous messaging so that the currently visualized message (request or response) is correctly considered when using the “Open in Design” button.
	25	+* Create - Add Integrations: We fixed an issue where, when your model is migrating or migrated to the new Event streaming broker, you get an error message for security reasons, sometimes when you un-transfer integrations from the Create.
	26	+* Create - Processes: We fixed an issue where opening an entry or exit connector with multiple integrations of the eMagiz Mendix connector system did not open the correct flow. The flows are now displayed in the same order as the topics in the center panel when you focus on a system. This ensures that when you select a flow, the correct one opens as expected.
	27	+* Deploy - Architecture: We have fixed a bug for DSH-enabled event streaming models, which may have prematurely lost read/write access to deleting topics if the topic was still in use in the active release.
	28	+* Deploy - Releases: We have fixed a bug for DSH-event streaming-enabled models, where updating one flow connecting to the DSH event streaming broker would result in containers hosting other such flows to be redeployed unintentionally as well.
	29	+* Deploy - Unused Properties: Users can select multiple properties across pages and delete the selections all at once. (#1730)
	30	+* Manage - Topic Triggers: All DSH topics have topic triggers. Removing topics without a topic trigger does not result in an error.
	31	+* Manage - Triggers: Manage phase access rights have been updated to allow users with the proper access to view and edit correctly.
	32	+* Manage - Error Messages: Increased the maximum number of displayed error message headers from 40 to 60. (#1309)
	33	+