Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 109.1
edited by Carlijn Kokkeler
on 2023/09/18 11:21
Change comment: There is no comment for this version
To version 154.2
edited by Danniar Firdausy
on 2023/11/07 11:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +208 - Controlled State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.dfirdausy
Content
... ... @@ -1,26 +1,23 @@
1 -In the last sprint cycle, we focused on what we show in Manage concerning the next-generation architecture. Furthermore, we will release a new cloud template. On top of that, we will release several minor changes with a potentially significant impact.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.205 - World Explores.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.208 - Controlled State .WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -
7 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template release notes for more information.
8 -
9 9  =====Minor changes=====
10 10  
11 -* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
12 -* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
13 -* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052)
7 +* Design - Message Mapping: The button 'Import from Store' will directly open the store.
8 +* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented.
9 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
10 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
11 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
14 14  
15 -
16 16  ====Bug fixes====
17 17  
18 -* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
19 -* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
20 -* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
21 -* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
15 +* 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)
16 +* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
17 +* 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)
18 +* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
22 22  
23 23  
24 24  =====Infra and image changes=====
25 25  
26 -* No infra and/or image changes is this release.
23 +* 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.