Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 159.1
edited by Danniar Firdausy
on 2023/11/08 16:17
Change comment: There is no comment for this version
To version 89.1
edited by Erik Bakker
on 2023/06/09 10:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -208 - Controlled State
1 +199 - Home Improvements
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -1,23 +1,19 @@
1 -In the last sprint cycle, we focused on providing users with a monitoring functionality for the state generation components. On top of that, we also made several improvements to the components interfacing the users to improve the user experience aspect of our platform. Moreover, we made some bug fixes and improvements on releases in Deploy and monitoring in Manage.
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.208 - Controlled State .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 5  =====Minor changes=====
6 6  
7 -* Create - Flow Designer: Input fields for XPath expressions have been made wider and capable of expanding to facilitate longer inputs. (#822)
8 -* Create - Flow Designer: Small styling changes and bug fixes have been implemented for edge cases during editing channels in the Flow Designer.
9 -* Deploy - Releases: During removing a release, users will be informed about the environments and the runtimes in which the release under deletion is running. (#1060)
10 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
11 -* Deploy - Deployment: The “preparing” step of the release at the beginning of the deployment is now faster due to the improved process of building the images.
12 -* Manage - Monitoring: There is a new page called "State generation statistics" that is located right under the Topic statistics navigation menu, which is only shown and accessible for models that have the add-on license for state generation.
13 -* Manage - Error messages & Log entries: Searching on entries in the next-generation architecture models now supports phrase matching, meaning that users can search entries based on phrases containing two or more words and entries with distances of 2 or incomplete search phrases.
14 -* Manage - Alerting: In Alerts, the previous "Source" column is renamed to "Source trigger" and its value is derived from the type of trigger which generates alert.
15 -* All - Toggles: We updated all instances of the toggle switch in the platform due to the latest eMagiz Design System module implementation in our platform.
16 -* All - Error Channel: Added a migration step in Gen3 migration, we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
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.
17 17  
18 18  ====Bug fixes====
19 19  
20 -* Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes.
21 -* Deploy - Deployment: We resolved an issue where sometimes older containers get deployed, while eMagiz shows the new containers are deployed.
22 -* Manage - Monitoring: Improved message processing in infra components that should reduce the occurrence of log messages failing to be sent in Gen3 models.
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)
23 23