Changes for page 208 - Controlled State
Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 96.1
edited by Erik Bakker
on 2023/06/22 13:26
on 2023/06/22 13:26
Change comment:
There is no comment for this version
To version 154.2
edited by Danniar Firdausy
on 2023/11/07 11:44
on 2023/11/07 11:44
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 0-UnchartedTerritories1 +208 - Controlled State - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.dfirdausy - Content
-
... ... @@ -1,27 +1,23 @@ 1 -In the last sprint cycle, we focused on i mprovingvarious aspects of theportalfunctionality.Amongothers,we focusedonthenext-generationarchitecture and others.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 0-UnchartedTerritories.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.208 - Controlled State .WebHome||target="blank"]]. 4 4 5 5 =====Minor changes===== 6 6 7 -* Create - Flow Designer: it is possible to select multiple components by area selection on the area with a scrollbar. 8 -* Create - Flow designer: The new best practices have updated Kafka components' default values. Updated values are: 9 -** For Kafka templates: 10 -*** Batch size: 200000 11 -*** Linger: 300 12 -** For Kafka message listener containers 13 -*** Fetch min. amount: 100000 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 - {{warning}}The existing Kafka components in your flows will automatically be updated with the new best practice values. To make deployingthese changes more effortless for you, we will create a new version of your flows after updating the values (versions will be created in the name of model contacts) and transfer them to the Deploy phase. You can then create and deploy a new release with updated flow versions.{{/warning}}13 +====Bug fixes==== 16 16 17 -* Deploy - CloudTemplates:New Cloud Templatesare availableforsingle-lane anddouble-lane environments.Pleasecheckout thecloudtemplate[[releasenotes>>Main.Release Information.CloudTemplates.WebHome||target="blank"]] for moreinformation.18 -* Deploy - Architecture: We removedthe deprecated reminderpopup to updateyour cloudslottemplate.Theautomatedupgrade feature replacesit alongsidethe"Upgrade"functionality in Deploy - Architecture.19 -* Deploy - Deployment plan: Weupdated the right paneof thedeploymentplanto makeit morecompatible withthe new runtime generation.Now, you cansee all relatedlogsregarding yourdeployment. By default,weonlyshowsomeecessarylogs, suchas error logs, warning logs, and startedruntime informationlogs. You can usethefilterlogsconsatthe topofthelistto show moreinformation.20 -* Deploy-Deployment plan:Weupdatedthe logicwithin our deployment plan functionality.The deploymentstep that disablesallenabled triggers fromtheManage phasedisables triggerstill you exit thedeployment plan overview.Thatmeans that those triggerswillbere-enabledafter youmoveawayfromthe deploymentprocess orclose the browser.Furthermore, there isno deploymentstepconfigurationto "enable"triggers anymore.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. 21 21 22 -====Bug fixes==== 23 23 24 -* Deploy - Architecture: We improved timeout settings to give Stop, Restart, and Reset runtime actions enough time to execute. (#957) 25 -* Design - Store: Importing into "Design" from the store is possible, even if the integration is not in Create yet. 26 -* Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases. Note that this functionality requires a newly deployed release. (#956) 27 -* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964) 21 +=====Infra and image changes===== 22 + 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.