Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 104.1
edited by Erik Bakker
on 2023/09/13 07:16
Change comment: There is no comment for this version
To version 85.1
edited by Erik Bakker
on 2023/06/05 16:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +199 - Home Improvements
Content
... ... @@ -1,27 +1,20 @@
1 -In the last sprint cycle, we focused on what we show in Manage concerning the next-generation architecture. Furthermore, we will release a new cloud template. On top of that, we will release several minor changes with a potentially significant impact.
1 +In the last sprint cycle we have focused on improving various aspects of the portal functionality. Among others we focused on the next-generation architecture, the store, security and certificate management.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.205 - World Explorers.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]].
4 4  
5 -=====New features=====
6 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
7 -
8 8  =====Minor changes=====
9 9  
10 -* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
11 -* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
12 -* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1046)
13 -* Manage - Alerting - Triggers: The non-editable trigger for Event streaming topic size has been changed to trigger on 95% of the configured size instead of 80%.
14 -* Manage - Monitoring: Viewing runtime, queue, and HTTP statistics are now limited to 7 days at a time. (3rd generation only)
7 +* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately 3 months before the expiration dates of event streaming users' access certificates.
8 +* Deploy - Release: After successful machine deployments, unused runtime images will be automatically removed. This can be disabled by changing the machine step in your deployment plan.
9 +* Manage - Monitoring: HTTP statistics page now displays all of the resources.
10 +* Manage - Alerting: congestion control wil be enabled by default with 10 alerts per 10 minutes and user cannot see or change it.
11 +* General - Infra: Changed the library used for storing metadata in the eMagiz Control Tower.
15 15  
16 16  ====Bug fixes====
17 17  
18 -* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
19 -* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
20 -* Manage - Queue statistics: Models with a vast number of queues will now show all queues. This used to be cut off. (Gen3 only)
21 -* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
22 -* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
15 +* Create - Store: Spring Reserved words that contain * are not incorrectly replaced with the prefix of the flow.
16 +* Manage - Monitoring: When an application failed to start, not all log messages were visible in the manage phase.
23 23  
18 +====Remarks====
24 24  
25 -=====Infra and image changes=====
26 -
27 -* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.
20 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.