Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 201.1
edited by Carlijn Kokkeler
on 2024/02/26 10:47
Change comment: There is no comment for this version
To version 78.1
edited by Erik Bakker
on 2023/05/12 08:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -215 - Tiny Tales
1 +197 - Pay Attention
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,15 +1,21 @@
1 -In the last sprint cycle, we focused on improving the event streaming graph. Moreover, we have done some bug fixes. First of all, the validation for queue names with respect to spaces has been improved. Moreover, it is now possible to remove an onramp that was previously linked to an all entry. Lastly, it is now possible to login to eMagiz by pressing enter when having the username field selected.
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.215 - Tiny Tales||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=====
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.
8 +
5 5  =====Minor changes=====
6 6  
7 -* Manage - Monitoring: The event streaming graph has been improved to better reflect the state of your topics. (#951)
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.
8 8  
9 9  ====Bug fixes====
10 10  
11 -* Login: In the login screen, users now have the ability to press enter to log in when having the username field selected.
12 -* Create - Flow Designer: The validation regarding undesired spaces for components that use a queue name has been improved. (#1012)
13 -* Create - Flow Designer: An issue has been fixed where it was not possible to remove an onramp that was previously linked to a combined entry. (#1021)
14 -
15 -
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: You can apply your changes to only one or both zones on 3rd generation double-lane models.
19 +* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
20 +* 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.
21 +* Design - Message Definitions: "Message format" button is also available in view mode. (#919)