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 200.1
edited by CarlijnKokkeler
on 2024/02/16 12:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -253 - Rince Repeat
1 +214 - System Symphony
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,21 +1,21 @@
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 failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
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.214 - System Symphony||target="blank"]].
4 4  
5 -==== Major Changes ====
5 +=====New features=====
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 +* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once. (#1141)
8 +* Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
8 8  
9 -==== Minor changes ====
10 +=====Minor changes=====
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.
12 +* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore. (#1216)
13 +* Manage - Monitoring: New functionality to ensure that the monitoring graphs in Manage can show data from the last thirty days.
15 15  
16 -==== Bug fixes ====
15 +====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)
17 +* Create - Flow Designer: The help text of the Group attribute has been improved.
18 +* Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802)
19 +* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed.
20 +
21 +