Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 242.1
edited by Carlijn Kokkeler
on 2024/05/06 14:23
on 2024/05/06 14:23
Change comment:
There is no comment for this version
To version 44.1
edited by Erik Bakker
on 2023/01/23 13:49
on 2023/01/23 13:49
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 220 -PatchParade1 +190 - Fast Forward - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,25 +1,32 @@ 1 - In the lastsprint cycle, wehaveworkedonanew[[runtimeimage>>doc:Main.ReleaseInformation.RuntimeImages.V306.WebHome||target="blank"]]that containsafixfor anssueregardingSFTP sessions. Furthermore, wedid severalsmallimprovementsandmanybug 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. 220 -PatchParade||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 -===== New features ===== 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.V120.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. 6 6 7 -* Capture - Integrations: Information about the integration pattern of a selected message type has been added to the new integration pop-up. (#1214) 8 -* Design - Architecture: When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted. (#1296) 9 -* Create - Flow designer: A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 10 -* Deploy - Architecture: Changes can now be deployed on SSL level without creating a new version of a flow in Create. 11 -* Deploy - Releases: Search boxes in the properties overview are now shown by default. (#1325) 12 -* Manage - Explore: We fixed an issue where navigating to the “Explore” tab in “Manage” phase would sometimes redirect users to the homepage.(#1237) 13 -* Manage - History: All events that relate to message queues (delete message, delete all messages or delete queue) are now logged in the Manage phase instead of the Deploy phase. (#1278) 9 +=====Major changes===== 14 14 15 - =====Bug fixes=====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. 16 16 17 -* Design - Message mapping: It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. (#1179) 18 -* Create - Flow designer: It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. (#852) 19 -* Create - Flow designer: The copy to clipboard button now copies the actual value of passwords instead of the masked value of them. (#1303) 20 -* Deploy - Architecture: Machines deleted in Design are excluded from the memory health check. (#1282) 21 -* Deploy - Architecture: Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] has been released. 22 -* Deploy- Deployment plan: We have implemented changes that should prevent the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) to not correspond with the actual execution of relevant steps. (#1315) 23 -* Manage - Explore: Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. (#1287) 24 -* Manage - Overview pages: We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. (#1122) 25 -* Manage - Redelivery: We fixed an issue where a large message would be shown at the bottom of the Redelivery page instead of the right side of the page. (#1290) 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 +====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 +