Changes for page 263 - User Update
Last modified by Erik Bakker on 2026/03/10 12:40
From version 54.1
edited by Erik Bakker
on 2023/03/03 11:32
on 2023/03/03 11:32
Change comment:
There is no comment for this version
To version 321.1
edited by Erik Bakker
on 2026/03/10 12:40
on 2026/03/10 12:40
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 193 -FanOut1 +263 - User Update - Content
-
... ... @@ -1,24 +1,19 @@ 1 -Th erelease introducesREST/XMLas optionforyourgateway operations as well asnewfeaturesforour3rd generationruntime,anew runtime image, and newcloud templates.Subsequently, we willreleaseseveralminorfeedbackpoints and bug fixes.1 +This release includes many user-driven updates to our platform to enhance your everyday work. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 193 -FanOut.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.263 - User Update.WebHome||target="blank"]]. 4 4 5 -==== =Newfeatures=====5 +==== Minor changes ==== 6 6 7 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V130.WebHome||target="blank"]]. 8 -* 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. 9 -* 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) 7 +* Create - Flow Designer: Improved the help text of the advanced ‘Match value’ attribute of the XPath filter, so it is clear how this option of the XPath filter can be used. (#1542) 10 10 11 -==== =Minorchanges=====9 +==== Bug fixes ==== 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 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. 11 +* Deploy - Deployment plan execution: The failure message shown during release preparation has been improved to be more descriptive. (#1568) 12 +* Deploy - Releases: We fixed an issue where the UI of the Create phase and Deploy phase were not aligned since the Releases screen did not show the new additions, but you can find them in the Release details popup. (#1675) 13 +* Manage - Explore - Topic browser: We fixed two problems with the topic browser. 14 +** When navigating to the last page of messages on a topic’s partition, the amount of messages shown in the paging will now correspond to the number of messages on that partition (#1714) 15 +** The first page of messages on a topic’s partition will now include the last message, with offset 1 below the ‘last offset’. 16 +* Manage - Export - Data sink: When opening this page on an empty data sink bucket, there will be a warning on top of the page (“no results found”). (#1096) 17 +==== Remarks ==== 17 17 18 -====Bug fixes==== 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 to not 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) 19 +* General - Portal: We have removed part of our platform's functionality as it was not used anymore.