Changes for page 266 - Feel Free
Last modified by Erik Bakker on 2026/04/20 22:05
From version 328.1
edited by Erik Bakker
on 2026/04/20 21:48
on 2026/04/20 21:48
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 -26 6-Feel Free1 +263 - User Update - Content
-
... ... @@ -1,31 +1,19 @@ 1 -This release has a significant impact onusers.Both in delivering functional value to our endusers andin moving away from a legacy constructwithin ourplatform, andtakingtheUI onestepintothe future. On top of that, we have squashed some bugs. Sadly, however,we also have to announce that the announced **[[environment template>>Main.Release Information.CloudTemplates.WebHome||target="blank"]]**in [[release 264>>doc:Main.Release Information.ReleaseBlogs.264 - StrictSeperation.WebHome||target="blank"]] has been pulled due to not meeting qualitystandards. Having said that, enjoyreadingourlatest updates on the platform.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>>doc:Main.Release Information.Release Blogs.26 6-Feel Free.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 5 ==== Minor changes ==== 6 6 7 -* General - Event Streaming: To authenticate at DSH, our event streaming broker, we use certificates. These certificates have an expiration date, so they must be rotated. We have introduced a new way of rotating these certificates for you. 8 -** Proxy certificates must always be valid in DSH to prevent clients from encountering issues. A scheduled event runs daily during working hours to verify this. 9 -** If certificate rotation fails in the test environment, it will **not** continue to the acceptance or production environments. 10 -* Create - System: We now show the parent entity when selecting an entity or attribute in the right panel. This allows a user to identify better where in the message's structure they currently are. (#1520) 11 -* Deploy - Release: Creating a new release automatically puts you in “edit mode” for that release. (#672) 12 -* Create - Add Integrations: Improved how we autogenerate flows for the user. 13 -* General - Platform: Improved our general deletion behavior when deleting a model. 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) 14 14 15 15 ==== Bug fixes ==== 16 16 17 -* Deploy - Upgrade: Fixes a bug where the portainer agent could not be updated, as part of the environment template procedures, for Windows systems where portainer is installed on another drive than C:\. [CSP-1922] 18 -* Manage - Monitoring - HTTP Statistics (Other metrics): The mean and max for the response time are split into two graphs. (#1200) 19 -* Deploy - History: Entries stating 'null' will no longer be shown. (#1479) 20 -* Manage - Monitoring - Log Entries: The search/reset buttons are disabled while the reset/search is still being processed. (#1538) 21 -* Design - Edit an API integration - New/Edit resource: Added reserved keywords for the path of a resource, which can no longer be used. (#1585) 22 -* Create - Transformation - Custom XSLT snippet: Trying to save a newly edited XSLT snippet is only possible in “Edit mode”. (#1670) 23 -* Capture - Integration: Users are prevented from clicking the "Save integration" button too fast after creating a new message type to prevent a timing issue resulting in an error. The save button at the integration level is inactive until a message type is set for that integration. (#531) 24 -* Design - Catalog: The default request body is generated automatically for the POST operation when added as an integration in the Design phase. 25 -* Deploy - Architecture: Fixed an issue in the execution of the environment upgrade for models that have API MAM. 26 - 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) 27 27 ==== Remarks ==== 28 28 29 -* General - Infrastructure: An update has been applied to the internal communication with the eMagiz-managed authorization server. 30 -* General - Infrastructure: An update has been applied across the platform regarding the UI. As a result, all reference selectors have been replaced with combo boxes, aligning with current best practices and enabling users to interact with the platform more effectively. 31 -** Slightly modified the creation of new message types by implementing a new type of input widget that combines drop-down selection functionality with actions. 19 +* General - Portal: We have removed part of our platform's functionality as it was not used anymore.