Changes for page 204 - Found It
Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 86.1
edited by Erik Bakker
on 2023/06/05 16:04
on 2023/06/05 16:04
Change comment:
There is no comment for this version
To version 88.1
edited by Erik Bakker
on 2023/06/06 08:36
on 2023/06/06 08:36
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,21 +1,20 @@ 1 -In the last sprint cycle we havefocused on improving various aspects of the portal functionality. Among others we focused on the next-generation architecture, the store, security and certificate management.1 +In the last sprint cycle, we 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 3 Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]]. 4 4 5 5 =====Minor changes===== 6 6 7 -* * 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. 8 -* 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. 9 -* 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. 10 -* Manage - Monitoring: HTTP statistics page now displays all of the resources. 11 -* Manage - Alerting: congestion control wil be enabled by default with 10 alerts per 10 minutes and user cannot see or change it. 12 -* General - Infra: Changed the library used for storing metadata in the eMagiz Control Tower. 7 +* Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store. 8 +* 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. 9 +* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899) 10 +* 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 three months before event streaming users' access certificates expire. 11 +* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan. 12 +* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960) 13 +* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it. 14 +* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower. 13 13 14 14 ====Bug fixes==== 15 15 16 -* Create - Store: Spring Reserved words thatcontain * are not incorrectly replaced with the prefixof the flow.17 -* Manage - Monitoring: When an application failed to start,not alllog messageswerevisiblein the manage phase.18 +* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864) 19 +* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937) 18 18 19 -====Remarks==== 20 - 21 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.