Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 09:59
From version 113.1
edited by Carlijn Kokkeler
on 2023/10/11 13:38
Change comment: There is no comment for this version
To version 94.1
edited by Erik Bakker
on 2023/06/22 13:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +200 - Uncharted Territories
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,43 +1,27 @@
1 -In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
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.206 - Situational Deployment.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 -
6 6  =====Minor changes=====
7 7  
8 -* Design - Framework: The framework used in the flow designer has been updated to the latest version.
9 -* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier.
10 -* Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
11 -* Create - SSL: Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
12 -* Deploy - Architecture: The title of the'apply to environment' action for changing topic retention size has been changed to be less confusing.
13 -* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum.
14 -* Deploy - Deployment plan: A change in the memory settings of the JMS triggers a redeployment of the container.
15 -* Deploy - Logging: New logging feature enabling us to make better choices in deprecating old encryption standards.
16 -* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
17 -* Deploy - Release properties: The description of a property can be changed by editing the property.
18 -* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
19 -* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
20 -* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
21 -* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment.
22 -* Manage - Alerting: Inactivated users should be removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
23 -* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes.
24 -* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default.
25 -* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
26 -* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform of the action.
27 -* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
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
28 28  
29 29  
30 -====Bug fixes====
31 31  
32 -* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
33 -* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
34 -* Design - Store: We fixed an issue that static copies were missing when importing store items.
35 -* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
36 -* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release.
37 -* Manage - Monitoring: It is now possible to search on messages partially in Manage Monitoring.
38 -* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
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.
39 39  
22 +====Bug fixes====
40 40  
41 -=====Infra and image changes=====
42 -
43 -* No infra and/or image changes is this release.
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)