Changes for page 204 - Found It
Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 104.1
edited by Carlijn Kokkeler
on 2023/09/18 11:05
on 2023/09/18 11:05
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -20 4-FoundIt1 +200 - Uncharted Territories - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,21 +1,27 @@ 1 -In the last sprint cycle, we focused on the scalabilityandstabilityof ourinfrastructure. Onopofthat, wewill releaseseveral minor changeswitha potentiallysignificantimpact.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 5-WorldExplorers.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.200 - Uncharted Territories.WebHome||target= "blank"]]. 4 4 5 -==== Newfeatures====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 7 8 - =====Minor changes=====15 +{{warning}}The existing Kafka components in your flows will automatically be updated with the new best practice values. To make deploying these 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}} 9 9 10 -* 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. 17 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 18 +* Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture. 19 +* Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation. Now, you can see all related logs regarding your deployment. By default, we only show some necessary 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. 20 +* Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser. Furthermore, there is no deployment step configuration to "enable" triggers anymore. 11 11 12 12 ====Bug fixes==== 13 13 14 -* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970) 15 -* Manage - Error messages: Error messages with a lengthy message history will also be displayed. This change only impacts containers that work on the 3rd generation architecture. 16 -* Deploy - Releases: When a user activates a release containing nested properties and the property is not created, we show it now as missing. We add the property placeholder after the user tries to activate the release. 17 -* Manage - Error messages: Error messages with a stack trace larger than 32kb will also be displayed. This change only impacts containers that work on the 3rd generation architecture. 18 - 19 -=====Infra and image changes===== 20 - 21 -* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage. 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)