Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 154.7
edited by Danniar Firdausy
on 2023/11/07 11:52
Change comment: There is no comment for this version
To version 154.10
edited by Danniar Firdausy
on 2023/11/07 12:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,6 +6,7 @@
6 6  
7 7  * Design - Message Mapping: The button 'Import from Store' will directly open the store.
8 8  * Create - Flow Designer: Input fields for XPath expressions have been made wider and capable of expanding to facilitate longer inputs.
9 +* Create - Flow Designer: Small styling changes and bugfixes have been implemented for edge-cases during editing channels in the Flow Designer.
9 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.
10 10  * Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
11 11  
... ... @@ -12,13 +12,14 @@
12 12  
13 13  * Manage - Monitoring: There is a new page called the "State generation statistics" that is located right under the Topic statistics navigation menu, which is only shown and accessible for models that has the add-on license for state generation.
14 14  * Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
15 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
16 +* 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 16  
17 17  ====Bug fixes====
18 18  
19 19  * Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
20 20  * Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
21 -* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087)
22 +* Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes.
23 +* Deploy - Deployment: We resolved an issue where sometimes older containers get deployed, while eMagiz shows the new containers are deployed.
22 22  * Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
23 23  
24 24