Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 145.1
edited by Carlijn Kokkeler
on 2023/10/24 09:06
on 2023/10/24 09:06
Change comment:
There is no comment for this version
To version 90.1
edited by Erik Bakker
on 2023/06/20 07:54
on 2023/06/20 07:54
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 7-AlignedState1 +200 - Uncharted Territories - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,33 +1,17 @@ 1 -In the last sprint cycle, we focused on deliveringstate generationcomponents.On top of that, wemade severalimprovements regarding thealignmentof components,and did someperformanceimprovementsand bug fixes. Moreover, we madeaangeinthemetrics storageduration.1 +In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture, and others. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.20 7-AlignedState3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.200 - Uncharted Territories.WebHome||target= "blank"]]. 4 4 5 5 =====Minor changes===== 6 6 7 -* Design - Message Mapping: The button 'Import from Store' will directly open the store. 8 -* Design - Performance: Performance improvements for the Flow Designer have been implemented. 9 -* Create - Flow Designer: When importing items from the store, flowfragments that are hidden in Design will be listed under the versions in Create. (#1044) 10 -* Create - Flow Designer: Resources without name won't trigger error messages when users select components. (#950) 11 -* Create - Flow Designer: We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. 12 -* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read only mode. 13 -* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well. 14 -* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028) 15 -* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045) 16 -* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards. 17 -* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched. 18 -* Manage - Data Sink: Data sink page has been moved to the “Explore” tab. (#946) 19 -* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match. 20 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022) 21 -* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687) 7 +* Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. It is replaced by the automated upgrade feature. 8 +* Deploy - Deployment plan: We updated the place to display the logs in the right pane of the deployment plan to make it more compatible with the new runtime generation. Now, you can see all related logs with your deployment. By default, we only show some important logs, such as error logs, warning logs, and started runtime information logs. You can use the filter logs icons at the top of the list to show more information. 9 +* Create - Flow Designer: it is possible to select multiple components by area selection on the area which has scrollbar. 22 22 23 23 ====Bug fixes==== 24 24 25 -* Create &Deploy -Styling:Thestylingoftheevent streamingcanvas intheCreateandDeploy phases has been slightlyalteredtomake topic andevent-processornamesmorereadable. (#1055)26 -* De ploy-Architecture:Containersareset inactivewhen theyareemovedinDesign andunused.27 -* Deploy-Releases:Wefixedanissuethatalotoferrorpopupswereshownwhenyoupromotedareleaseversionoa nextenvironment. (#1087)28 -* Manage - Triggers:Besidescheckingerrorheader,theerror triggerisconfiguredto check ifanerror messagecontainsaterm.13 +* Deploy - Architecture: We improved timeout settings to give Stop, Restart and Reset runtime actions, enough time to execute. (#957) 14 +* Design - Store: Import into design from store is possible, even if the integration is not in Create yet. 15 +* 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) 16 +* Manage - Manage Dashboards: The speed of loading the screen is improved greatly for all models. This is most noticeably for larger models. (#964) 29 29 30 - 31 -=====Infra and image changes===== 32 - 33 -* 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.