Wiki source code of 208 - Controlled State
Version 154.11 by Danniar Firdausy on 2023/11/07 12:02
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
153.2 | 1 | In the last sprint cycle, we focused on delivering monitoring functionality for the state generation components. On top of that, we also made several improvements on 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.1 | 2 | |
| |
154.1 | 3 | Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.208 - Controlled State .WebHome||target="blank"]]. |
| |
35.1 | 4 | |
| |
109.1 | 5 | =====Minor changes===== |
| |
93.1 | 6 | |
| |
139.1 | 7 | * Design - Message Mapping: The button 'Import from Store' will directly open the store. |
| |
154.7 | 8 | * Create - Flow Designer: Input fields for XPath expressions have been made wider and capable of expanding to facilitate longer inputs. |
| |
154.8 | 9 | * Create - Flow Designer: Small styling changes and bugfixes have been implemented for edge-cases during editing channels in the Flow Designer. |
| |
154.6 | 10 | * Deploy - Releases: During removing a release, users will be informed about the environments and the runtimes in which the release under deletion is running. |
| |
149.1 | 11 | * Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well. |
| |
154.4 | 12 | |
| 13 | |||
| |
154.3 | 14 | * 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. |
| |
140.1 | 15 | * Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched. |
| |
154.9 | 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. |
| |
93.1 | 17 | |
| |
109.1 | 18 | ====Bug fixes==== |
| |
104.1 | 19 | |
| |
141.1 | 20 | * 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) |
| |
144.1 | 21 | * Deploy - Architecture: Containers are set inactive when they are removed in Design and unused. |
| |
154.10 | 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. | ||
| |
154.11 | 24 | * Manage - Monitoring: Improved message processing in infra components that should reduce the occurance of log messages failed to be sent in Gen3 models. |
| |
101.1 | 25 | |
| |
108.1 | 26 | |
| |
109.1 | 27 | =====Infra and image changes===== |
| |
108.1 | 28 | |
| |
139.1 | 29 | * State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information. |