Changes for page 217 - Template Tango
Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 12.1
edited by Erik Bakker
on 2022/10/24 12:01
on 2022/10/24 12:01
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 (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 86-DaemonSwitch1 +199 - Home Improvements - Content
-
... ... @@ -1,25 +1,20 @@ 1 - Releasethatbringsthenewmonitoring stacktofruitionand bringsvariousupdatesto handlingmultiplenamespaces.Ontop ofthat, we havereleasedasleuth ofsmallerfeedbackitemsand bugfixes.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.1 86-DaemonSwitch.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 - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file. 7 - 8 8 =====Minor changes===== 9 9 10 -* Design System. Changed the look and feel across the portal altogether. Changes can be seen in: 11 - ** Datagids, where there is now on hover action for example. 12 - ** Pop ups 13 - ** Context menus, also have on hover action 14 - ** Styling of scrollbars 15 - ** Warning, info and error context labels. 16 -* Message Redelivery - admin logs improved to better analyze issues when they occur 17 -* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality 18 -* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed 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. 19 19 20 20 ====Bug fixes==== 21 -* Deploy - Deployment plan. Performance of page to deploy a release increased significantly 22 -* Store - Import resources was incorrectly done in specific cases, which is now fixed 23 -* Store - Target namespace will be imported when importing an XML Message Definition 24 -* Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model. 25 -* Store - Importing items from the store sometimes resulted in invalid JMS connection factories. 17 + 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) 20 +