Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 63.1
edited by Erik Bakker
on 2023/04/11 10:00
Change comment: There is no comment for this version
To version 282.1
edited by Erik Bakker
on 2025/09/21 21:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +253 - Rince Repeat
Content
... ... @@ -1,30 +1,22 @@
1 -As the quarter has ended, we went silent for a couple of weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.195 - Easter Party.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +==== Major Changes ====
6 6  
7 -* General - Control Tower: Changed several generic triggers for more predictable behavior.
8 -* Administration - License Tracker: The license tracker has been updated for new license models and features.
9 -* Administration - License Tracker: When the feature ‘Data sink’ is enabled, the number of message packs of the contract will be displayed when you hover with the mouse over the feature.
10 -* Capture - Settings: Editing message types are now consistent between new and existing ones. (#884)
11 -* Design - API Gateway: Default HTTP responses are generated automatically (#417)
12 -* Design - Solution design: An additional option is added to the context menu that navigates to the message definition added to event streaming topics without processors. (#850)
13 -* Create - Add Integrations: We used the name of the API integration that you set in the Design phase to display on the Transfer screen. That helps you choose the correct integrations to add to the Create phase more quickly.
14 -* Create - 3rd Generation Migration: You can toggle the custom error handling option for your event processors while migrating your event processing container to the 3rd Generation Runtime.
15 -* Deploy - Deployment plan: When you run your deployment plan in your model using the new generation runtimes, you will be able to be the logs that relate to an executing deployment step.
16 -* Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan.
17 -* Deploy - Architecture: Certificates only editable by system admin.
18 -* Manage - Jobs: In case the model has containers that contain jobs in one of its flows, users can inspect job managers, job executions, and job step executions. Note that this only works for the 3rd generation runtime.
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)
19 19  
20 -====Bug fixes====
9 +==== Minor changes ====
21 21  
22 -* General - Runtime Image: A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V140.WebHome||target="blank"]].
23 -* Design - API Gateway: Improved generation of Open API JSON and example messages for API gateway operations to handle cases where an element in your gateway definition is used multiple times. (#440)
24 -* Design - API Gateway: We fixed an issue where changing the message format of a gateway message did not result in an update of the OpenAPI (i.e., Swagger) document.
25 -* Design - System message: We fixed an issue that led to importing towards the wrong message definition when the option "Import from XSD" was chosen on a synchronous message. (#818)
26 -* Create - Message: When viewing or editing an enumeration, it is no longer deleted when the cancel button is pressed.
27 27  
28 -====Remarks====
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.
29 29  
30 -* Deploy - Releases: We removed the existing snapshots of release property values.
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)
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.