Skip to Content

Changes for page 247.1 - Help Out

Last modified by Erik Bakker on 2025/06/25 19:51
From version 43.1
edited by Erik Bakker
on 2023/01/18 11:41
Change comment: There is no comment for this version
To version 257.1
edited by Erik Bakker
on 2025/06/02 09:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +246 - Preparation Paradise
Content
... ... @@ -1,32 +1,18 @@
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 +In our previous release, we released functionality to increase the stability of Windows runtimes. This time, we followed that up by adding additional safety measures on the runtime level. Additionally, we have several pieces now available to prepare for pending changes to our event streaming offering. Furthermore, we introduced several minor improvements to the platform.
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>>Main.Release Information.Release Blogs.246 - Preparation Paradise.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 +====Minor Changes====
8 8  
9 -=====Major changes=====
7 +* Deploy - General: Updated the Java arguments applied to Windows containers to align with the container limits, thereby improving the stability of these containers.
8 +* Deploy - Architecture: You can now manually set the memory of your on-premise machine in design architecture. This memory is considered when checking the machine's health in "Deploy architecture."
9 +* General - Runtime: We have two updates on the runtime level.
10 +** A new [[runtime image>>doc:Main.Release Information.Runtime Images.V331.WebHome||target="blank"]] is available that adds support for consuming Kafka topics based on a ‘topics’ pattern instead of a fixed list of topic names.
11 +** A new runtime version that updates our Java runtime version from Java 17.0.13 to Java 17.0.15. This is primarily a security update.
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.
12 -
13 -=====Minor changes=====
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 -
25 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.
32 32  
15 +* Create - Flow designer: We have fixed a bug where you could not add a new entry flow to a ‘SOAP Entry Connector’ enabled system.
16 +* Manage - Error Messages: The non-working download button for payload content files now displays a more descriptive error message text. (#886)
17 +* Manage - Explore (Queue Browser): Updated styling for the action buttons related to the debug functionality. (#1653)
18 +* Q&A Forum - General: You will no longer receive an email notification about your comments on posts in the Q&A forum. (#1462)