Skip to Content

Changes for page 254 - Other One

Last modified by Erik Bakker on 2025/10/09 11:13
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 269.2
edited by Erik Bakker
on 2025/07/14 07:12
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -253 - Rince Repeat
1 +249 - Amendment Avalanche
Content
... ... @@ -1,21 +1,11 @@
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 +This release introduces the ability for beta models to run on our new event broker. With this critical step being reached, we can migrate the first set of beta customers to the new event broker while simultaneously further developing this proposition.
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.2471 - Help Out.WebHome||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 +* General - Event Streaming: Run your event streaming solution on our new event broker at DSH. Please note that we will initially release this functionality as a **beta** feature. This means it is currently only available to a select number of models. Once this functionality is more developed, we will share more information on this.
8 8  
9 9  ==== 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.
15 -
16 -==== Bug fixes ====
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)
11 +* Deploy - Properties: A new data type option is introduced on the property level. This data type enables the storage of PEM certificates in their correct format, which is necessary for a secure connection to DSH.