Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 57.1
edited by Erik Bakker
on 2023/03/14 08:31
Change comment: There is no comment for this version
To version 102.1
edited by Erik Bakker
on 2023/08/15 12:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Giant Leap
1 +203 - Fast Paced
Content
... ... @@ -1,24 +1,19 @@
1 -The release introduces various improvements on our 3rd generation runtime architecture and various other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
1 +In the last sprint cycle, we focused on the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.194 - Giant Leap.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.203 - Fast Paced.WebHome||target= "blank"]].
4 4  
5 -=====New features=====
6 -
7 -* 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.V130.WebHome||target="blank"]].
8 -* 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)
9 -* 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.
10 -
11 11  =====Minor changes=====
12 12  
13 -* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
14 -* Design - API Catalog: When you change a path in the Design phase, your HTTP inbound gateways that use the changed path will also be updated in Create phase if you have edit rights. (#524)
15 -* 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.
16 -* Manage - Error messages: Message history is sorted by timestamp descending.
7 +* Create - Integrations: Improved the performance of adding or removing API gateway integrations for split entry configurations. (#1023)
8 +* Manage - Alerting: Identifiers of triggers are now visible in the edit screen.
17 17  
18 18  ====Bug fixes====
19 19  
20 -* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming. (#908)
21 -* Create - Migration: We fixed a third-generation migration issue where the legacy error handling flow components were not removed from the asynchronous routing flow.
22 -* 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.
23 -* Deploy - Release: We fixed an issue that caused images not to be built in specific situations when running in the new runtime generation runtime.
24 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)
12 +* Create - Flows: Fixed an issue where removing some split entry flows from Create phase was not possible after splitting your all entry/combined entry flow. (#1016)
13 +* Deploy - Releases: We fixed an issue that your release contains a JMS server flow twice with different build version numbers when adding another flow to your release. (#597)
14 +* Deploy properties: When a user activates a release containing nested properties and the property is not created, we show it now as missing. On top of that, we add the property placeholder after the user tries to activate the release.
15 +
16 +=====Infra and image changes=====
17 +
18 +* Infrastructure: Tightened security policies for a more secure infrastructure.
19 +* Infrastructure: Added and improved auto-scaling behavior for the eMagiz Control Tower