Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 80.1
edited by Erik Bakker
on 2023/05/12 09:14
Change comment: There is no comment for this version
To version 52.1
edited by Erik Bakker
on 2023/03/03 08:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +193 - Fan Out
Content
... ... @@ -1,26 +1,21 @@
1 -Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments.
1 +The release introduces REST/XML as option for your gateway operations as well as new features for our 3rd generation runtime, a new runtime image, and new cloud templates. Subsequently, we will release several minor feedback points and bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.197 - Pay Attention.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.193 - Fan Out.WebHome||target= "blank"]].
4 4  
5 5  =====New features=====
6 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
7 -* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
6 +* Deploy - Releases: New release properties pop-up that shows all properties in your release, grouped by containers that they are assigned to. This pop-up can be accessed by pressing the wrench shaped icon, which becomes available once a release is set as active.
7 +* Design - Settings: We added XML support to API Management. To enable this feature, change the 'Default message format' in the Design settings section. You can change individual operations by changing the message format of your gateway message. Migrating existing operations requires a reset of the exit flow and a change in the catalog in Design. For more information see the release blog post. (#815)
8 8  
9 9  =====Minor changes=====
10 10  
11 -* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated.
12 -* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute."
13 -* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments.
11 +* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
12 +* Design - API Catalog: When you change a path in Design phase, your HTTP inbound gateways that use the changed path will also be updated in Create phase if you have edit rights. (#524)
13 +* Manage - Error messages: Message history is sorted by timestamp descending.
14 14  
15 15  ====Bug fixes====
16 16  
17 -* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item.
18 -* Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952)
19 -* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947)
20 -* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
21 -* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again.
22 -* Design - Message Definitions: "Message format" button is also available in view mode. (#919)
23 -
24 -====Remarks====
25 -
26 -* Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture. Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off.
17 +* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming (#908)
18 +* Create - Migration: We fixed a third generation migration issue, where the legacy error handling flow components were not removed from the asynchronous routing flow.
19 +* Create - Flow designer: when migrating a container’s flows from gen2 to gen 3, “global wire tap” components and their relevant components will be removed.
20 +* Deploy - Release: We fixed an issue that caused images to not be built in specific situations when running in the new runtime generation runtime.
21 +* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)