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 98.1
edited by Erik Bakker
on 2023/07/17 21:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -253 - Rince Repeat
1 +201 - Be Informed
Content
... ... @@ -1,21 +1,30 @@
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 planning the upcoming quarter, finishing up, and working on the Hackathon to fix several smaller items.
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.201 - Be Informed.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 +* Portal - Menu: The back button is changed to have text on it to make the navigation much clearer. (#949)
8 +* Design-Architecture: Topic Storage detail page contains help text. (#994)
9 +* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832)
10 +* Design - API Gateway: Small styling improvement on the "Edit integration page." (#954)
11 +* Create - Flow Designer: When deleting one or multiple components, you cannot change the selection before confirming or canceling the delete action. (#969)
12 +* Create - Migrate to 3rd Generation: If one or more flows break during migration, a popup will inform the flows containing errors after the migration. (#983)
13 +* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979)
14 +* Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown. All changes made in the portal that will affect your running environment are listed here. These changes can be applied to the environment or reverted. (#828)
15 +** Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release.
16 +** Changes with a direct effect will not be listed (for example, restarting a machine).
8 8  
9 -==== Minor changes ====
18 +====Bug fixes====
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.
20 +* Design - Solutions: We fixed an issue that displayed a message mapping error despite having a passthrough API gateway. (#935)
21 +* Design - Settings: The full length of the contract number can now be registered. (#958)
22 +* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen 3 will not block migration. (#982)
23 +* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990)
24 +* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972)
25 +* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
15 15  
16 -==== Bug fixes ====
27 +=====Infra and image changes=====
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)
29 +* Changed the endpoint for sending error messages to the eMagiz Control Tower.
30 +* Updated the Spring version of the gateway supporting deploy and manage phase operations.