Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 241.1
edited by Carlijn Kokkeler
on 2024/05/06 14:18
Change comment: There is no comment for this version
To version 81.1
edited by Erik Bakker
on 2023/05/16 09:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -220 - Patch Parade
1 +197 - Pay Attention
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,25 +1,26 @@
1 -In the last sprint cycle, we have worked on a new runtime image LINK that contains a fix for an issue regarding SFTP sessions. Furthermore, we did several small improvements and many bug fixes.
1 +Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.220 - Patch Parade||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.197 - Pay Attention.WebHome||target= "blank"]].
4 4  
5 -===== New features =====
5 +=====New features=====
6 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
7 +* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
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 +=====Minor changes=====
14 14  
15 -===== Bug fixes =====
11 +* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated.
12 +* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute."
13 +* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments.
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 LINK 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)
15 +====Bug fixes====
16 +
17 +* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item.
18 +* Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952)
19 +* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947)
20 +* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
21 +* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again. Note that to make this functionality available a new "base image" was created which will automatically be applied to all gen two karaf containers when you create a new release and deploy it via the deployment plan causing redeployments.
22 +* Design - Message Definitions: "Message format" button is also available in view mode. (#919)
23 +
24 +====Remarks====
25 +
26 +* Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture. Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off.