Changes for page 248 - Smooth Sailing

Last modified by Erik Bakker on 2025/06/30 13:33

From version 271.1
edited by Erik Bakker
on 2025/06/30 09:45
Change comment: There is no comment for this version
To version 45.1
edited by Erik Bakker
on 2023/01/31 14:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -248 - Smooth Sailing
1 +191 - Fifty Fifty
Content
... ... @@ -1,21 +1,36 @@
1 -This release introduces a new [[cloud template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]], for every type of cloud we offer that connects you to our latest carwash. In addition, we have several improvements within the platform that enhance the user experience and improve interaction with the platform. See below for the details.
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>>Main.Release Information.Release Blogs.248 - Smooth Sailing.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 -==== Major changes ====
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 - Cloud Template: A new [[cloud template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]], for every type of cloud we offer, is available that enables connections to be switched to the updated carwash.
8 -* Create - Transformation: Users are allowed to move operations freely, except for Static Input, which must always be the first operation. (#1269)
9 -** Deleting the Static Input operation is not allowed if there are other operations in the row.
10 -** An error message is presented in the alert tab if there is a mismatch between the input and output of an operation to show that the order is inconsistent. The alerts can be pressed to open the edit or view screen of the operation that is causing the inconsistency.
13 +=====Major changes=====
11 11  
12 -==== 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.
13 13  
14 -* Permissions - History: The export of a model ‘permissions’ tab now has a logical name. (#857)
15 -* Design - Message Mapping: Users can now refresh their Design message mappings. (#848)
16 -* Deploy - Architecture: Previously canceled containers, machines, and connectors in Design → Architecture are no longer shown in the 'Apply to Environment' overview in Deploy. (#1646)
17 -* Deploy - Releases: Users can now add every type of flow to their release. (#948)
18 -* Deploy - Containers: The successful deletion pop-up is prevented from showing when the process is unsuccessful. This action occurred when a user tries to delete an empty container with hidden flows attached. (#1481)
19 -* Deploy - User Management: For the new screens related to DSH user management, we have fixed some undesired behavior caused by Keeper Password Manager.
20 -** Prevent auto-fill on specific fields by renaming labels
21 -** Applied styling to hide the Keeper button in input fields where undesired.
17 +=====Minor changes=====
18 +
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.
28 +
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.
36 +