Wiki source code of 253 - Rince Repeat

Last modified by Erik Bakker on 2025/09/21 21:33

Hide last authors
Erik Bakker 281.1 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.
eMagiz 1.1 2
Erik Bakker 281.1 3 Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]].
Erik Bakker 35.1 4
Erik Bakker 281.1 5 ==== Major Changes ====
Erik Bakker 101.1 6
Erik Bakker 281.1 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)
Erik Bakker 267.1 8
9 ==== Minor changes ====
10
Erik Bakker 282.1 11
Erik Bakker 281.1 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.
Erik Bakker 270.1 15
16 ==== Bug fixes ====
17
Erik Bakker 281.1 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)
Erik Bakker 282.1 22 ** 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.