Changes for page 208 - Controlled State
Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 105.1
edited by Bouke Reitsma
on 2023/09/14 15:09
on 2023/09/14 15:09
Change comment:
There is no comment for this version
To version 154.8
edited by Danniar Firdausy
on 2023/11/07 11:56
on 2023/11/07 11:56
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -20 5-WorldExplorers1 +208 - Controlled State - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. BoukeReitsma1 +XWiki.dfirdausy - Content
-
... ... @@ -1,27 +1,28 @@ 1 -In the last sprint cycle, we focused on what weshowinManageconcerning thenext-generationarchitecture.Furthermore, wewill releaseanewcloudtemplate.Ontopofthat,wewillreleaseseveralminorchangeswitha potentiallysignificantimpact.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.20 5-WorldExplorers.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 -* 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>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 7 - 8 8 =====Minor changes===== 9 9 10 -* Create-3rd Generationruntimemigration:Yourcontainerswillbe validated to function with the 3rd generation structure beforeyouapprove themigration.11 -* Deploy - Architecture: The container calculations areimproved.Foreventstreamingcontainers,theseshowthenumber of topic proccessorsdeployed. Gatewaycontainers representthe amount of operationsdeployedon a container.For JMS containers,these represent the numberofmessagequeues deployed. The other typesofcontainers displaytheamount of integrations deployed.(#544) (#869)12 -* Manage -Monitoring:Variable valuesinHTTP statisticsdetailsdashboardsaresorted,refreshedon timechange,andcan bemultiplyselected.(#1046)13 -* Manage -Alerting- Triggers:The non-editabletriggerfor Event streamingtopicsizehas beenchangedto triggeron95%oftheconfiguredsizeinstead of80%.14 -* Manage -Monitoring:Viewingruntime,queue,andHTTPstatisticsarenow limitedto 7 daysat a time.(3rd generationonly)7 +* Design - Message Mapping: The button 'Import from Store' will directly open the store. 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. 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. 11 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well. 15 15 13 + 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. 15 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched. 16 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022) 17 + 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 -* Manage - Queue statistics: Models with a vast number of queues will now show all queues. This used to be cut off. (Gen3 only) 21 -* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed. 22 -* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues. 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) 21 +* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused. 22 +* 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) 23 +* 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 25 25 =====Infra and image changes===== 26 26 27 -* No infra and/orchangeshisrelease.28 +* 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.