Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55

From version 247.1
edited by Carlijn Kokkeler
on 2024/05/21 12:11
Change comment: There is no comment for this version
To version 96.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 -221 - Swift Shift
1 +200 - Uncharted Territories
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,18 +1,27 @@
1 -In the last sprint cycle, we have worked on .
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.221 - Swift Shift||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 -===== New features =====
5 +=====Minor changes=====
6 6  
7 -* Q & A: Search results are now persisted when pressing the back button after opening a question in the community Q & A. (#1324)
8 -* Catalog: We have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
9 -* Design - CDM/System message: A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. (#151)
10 -* Design - System message: Moving an attribute in the datamodel is now directly shown in the tree structure as well. (#151)
11 -* Design - CDM/API Data model/ES data model and system message: The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. (#151)
12 -* Deploy - Deploy release: When executing a start/stop action on a group, the description of the step now contains the name of the group.
13 -* Deploy - Architecture: When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
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
14 14  
15 -===== Bug fixes =====
16 -* Design - System messages: When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. (#140)
17 -* Deploy - Containers: The delete behaviour of containers in the container overview has been improved. (#1053)
18 -* Deploy - API Gateway: We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.
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}}
16 +
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.
21 +
22 +====Bug fixes====
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)