Skip to Content

Changes for page 256 - Power Up

Last modified by Erik Bakker on 2025/11/04 12:44
From version 281.1
edited by Erik Bakker
on 2025/09/21 21:29
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 -253 - Rince Repeat
1 +200 - Uncharted Territories
Content
... ... @@ -1,21 +1,27 @@
1 -This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready.
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>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.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 -==== Major Changes ====
5 +=====Minor changes=====
6 6  
7 -* Deploy -> Containers: The user can now easily see the containers a flow should run on in Deploy → Containers via the button in the flow grid. Furthermore, we have overhauled the user experience on this overview to align with recent improvements to other parts of Deploy. (#976)
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
8 8  
9 -==== 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}}
10 10  
11 -* When the user wants to use the Swagger resource with the correct information, one of the API flows in Create requires a flow version push. **
12 -* Manage - Alerting - Triggers: Removed the deprecated, eMagiz-defined log trigger specified under the ‘other’ tab for Log entries. This trigger would generate an alert in the event of a runtime crash due to memory issues or failure to deliver a message.
13 -** Since the release of our new log alerting, it is possible to specify this alert rule yourself under the ‘logs’ tab if you still wish to receive these alerts. To do so, create four new log triggers as shown in our [[release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]]
14 -* Manage - Alerting - Triggers: Introduced a new ‘Quotas’ tab, where the quota limits for metrics, log, and error messages can be viewed per environment.
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.
15 15  
16 -==== Bug fixes ====
22 +====Bug fixes====
17 17  
18 -* Create - Flow Testing: Validation message is changed to make it more transparent to the user why they could not set the desired name for the flow test message. (#1702)
19 -* Create - Flow designer: You can no longer view the save button on a standard aggregator component while not in “Start Editing“ mode (#1703)
20 -* Deploy - Releases: Height of the release details pop-up is fixed to keep it consistent between all releases, including the Create Phase Release. (#1706)
21 -* API Management - Swagger (UI): NonEmptyString is now correctly represented in the swagger resource in Create, and therefore the Swagger UI that API users can check for details. (#1652)
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)