Changes for page 232 - Bug Busters
Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 289.1
edited by Carlijn Kokkeler
on 2024/08/12 11:58
on 2024/08/12 11:58
Change comment:
There is no comment for this version
To version 89.1
edited by Erik Bakker
on 2023/06/09 10:12
on 2023/06/09 10:12
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 - 227-FixFrenzy1 +199 - Home Improvements - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,16 +1,19 @@ 1 - During our recentsprintcycle,wehave ......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 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 227-FixFrenzy||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 -====Minor changes==== 6 -* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview. 5 +=====Minor changes===== 7 7 7 +* Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store. 8 +* 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) 9 +* 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. 10 +* 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. 11 +* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960) 12 +* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it. 13 +* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower. 14 + 8 8 ====Bug fixes==== 9 -* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking. 10 -* Create - Flow Testing: The tracing information for errorChannel messages has been improved. 11 -* Create - Message Definitions: The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes to your namespaces in your message definitions. 12 -* Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted. 13 -* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version. 14 -* Manage - Alerting: We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating. 15 -* Manage - Alerting: You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly. 16 -* Manage - Alerting: We have fixed a case where a tenant-queue-trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime. 16 + 17 +* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864) 18 +* 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) 19 +