Changes for page 263 - User Update
Last modified by Erik Bakker on 2026/03/10 12:40
From version 307.1
edited by Erik Bakker
on 2026/02/10 09:00
on 2026/02/10 09:00
Change comment:
There is no comment for this version
To version 320.1
edited by Erik Bakker
on 2026/03/09 13:25
on 2026/03/09 13:25
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 1-TakingCharge1 +263 - User Update - Content
-
... ... @@ -1,16 +1,20 @@ 1 -This release includes a lot of updates to our platform. Weare releasingsome beta featuresfor customers utilizing ourlatestversionof the API Gateway allowing touse multipleauthentication methods.Ontopof that we willreleasea new environment template that will update a multitude ofconfigurations on cloud and on-premisemachines. Furthermore,wehave a series of smaller improvements to bring delighttoyour everyday work.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 1-TakingCharge.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 -* API gateways using the latest Multiple Authentication Methods feature can now configure the [[Authorization Code OAuth2 grant type>>https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow||target="blank"]] for their gateway users. Note that the following timeouts apply: 8 -** The authorization code is valid for **5 minutes**, meaning it should be used to obtain an access token within that period. 9 -** Clients that obtain an access token with authorization code will also obtain a ~~refresh token~~, that can be used to obtain a subsequent access token without user intervention. This refresh token is valid for *24 hours*, meaning that the client application has to call the eMagiz API gateway at least that often, otherwise manual intervention is needed to authorize the call again. 7 +* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers is available. 8 +* 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 10 +==== Bug fixes ==== 11 + 12 +* Deploy - Deployment plan execution: The failure message shown during release preparation has been improved to be more descriptive. (#1568) 13 +* 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) 14 +* Manage - Explore - Topic browser: We fixed two problems with the topic browser. 15 +** 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) 16 +** The first page of messages on a topic’s partition will now include the last message, with offset 1 below the ‘last offset’. 17 +* 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) 11 11 ==== Remarks ==== 12 12 13 -* The advised Docker version for on-premises deployments has been updated from 24.0.7 to 29.1.3. Documentation on how to update Docker can be found at: 14 -** [[Linux>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-linux-installguide.WebHome||target="blank"]] 15 -** [[Windows>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-windows-installguide.WebHome||target="blank"]] 16 -* An infrastructure change has been applied to the container registry to improve how traffic is managed within our own environment. 20 +* General - Portal: We have removed part of our platform's functionality as it was not used anymore.