Changes for page 262 - Good News

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-259 - Improve Infinitely
	1	+191 - Fifty Fifty

Content

...	...	@@ -1,21 +1,36 @@
1		-This release features various updates to our platform, just after the holiday season. Apart from various more minor improvements, we have also launched a new [[runtime image>>doc:Main.Release Information.Runtime Images.V350.WebHome||target="blank"]] for **all** customers.
	1	+The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
2	2
3		-Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.259 - Improve Infinitely.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]].
4	4
5		-==== New features ====
	5	+=====New features=====
	6	+* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
	7	+** Error Message is to evaluate the headers of the original message which resulted in an error.
	8	+** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
	9	+** Queue Consumers is to configure for queues where more than 1 consumer is expected.
	10	+** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
	11	+** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow.
6	6
7		-* General - Runtime Image: Maintenance update where we primarily updated Spring Boot from version 3.4.1 to 3.5.8 and ensured all our external libraries are up-to-date.
	13	+=====Major changes=====
8	8
9		-==== Minor changes ====
	15	+* 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	10
11		-* Create - Flow Designer: Selector expression is added on the channel interceptors page. (#1738)
12		-* Manage - Error Messages: Search by complete flow name functionality is added to the flows with error messages page. Additionally, the grid is updated to improve the page's appearance. (#1738)
	17	+=====Minor changes=====
13	13
14		-==== Bug fixes ====
	19	+* 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.
	20	+* Create - Flow designer: sensitive information stored in property values is masked. (#790)
	21	+* 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.
	22	+* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
	23	+* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
	24	+* 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)
	25	+* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
	26	+* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
	27	+* 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.
15	15
16		-* Create - Transformation: The content section of the XSLT snippet is converted to an XML editor to beautify the field. (#1739)
17		-* Create - Flow Designer: Validation feedback is visualised on the flat file field right before the save action to provide clarity to the user. (#891)
18		-* Create - Flow Designer: The same display name was being used for two similar support objects, which caused confusion. The incorrectly labeled object has now been renamed. The second "Byte array length header (de)serializer" has been renamed to "ByteArrayRawSerializer". (#1751)
19		-* Deploy - Known Hosts String: When you create a new property and select the drop-down called “Data type”, choose the option called “Known hosting string”. Behind the “Value” field, a cog wheel appears. It leads you to a pop-up. In this pop-up, the Host and Port fields have been swapped. We did it because this ordering aligns with the common defaults used across IT systems. (#1749)
20		-* Monitoring - Runtimes: two graphs, namely “Problematic runtimes memory usage” and “Max memory usage”, are fixed and show correct information. (#1654)
	29	+====Bug fixes====
	30	+* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
	31	+* 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)
	32	+* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
	33	+* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
	34	+* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
	35	+* 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.
21	21