Changes for page 262 - Good News
Last modified by Erik Bakker on 2026/02/23 08:06
From version 308.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 11.1
edited by Erik Bakker
on 2022/10/24 11:56
on 2022/10/24 11:56
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 - 261 -TakingCharge1 +186 - Daemon Switch - Content
-
... ... @@ -1,16 +1,25 @@ 1 - This releaseincludesalotofupdates to our platform. We arereleasingsomebeta features forcustomersutilizing ourlatestversionofthe API Gateway allowingto use multipleauthentication methods. On top of that wewillrelease a newenvironmenttemplatethat will update a multitude of configurations on cloudand on-premisemachines. Furthermore,wehavea series of smallerimprovements to bring delightto youreveryday work.1 +Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities. 2 2 3 -Please find out more on our [[Release blog>> doc:Main.Release Information.Release Blogs.261 -TakingCharge.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.186 - Daemon Switch.WebHome||target="blank"]]. 4 4 5 -==== New Features ==== 5 +=====New features===== 6 +* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file. 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. 8 +=====Minor changes===== 10 10 11 -==== Remarks ==== 10 +* Design System. Changed the look and feel across the portal altogether. Changes can be seen in: 11 + ** Datagids, where there is now on hover action for example. 12 + ** Pop ups 13 + ** Context menus, also have on hover action 14 + ** Styling of scrollbars 15 + ** Warning, info and error context labels. 16 +* Message Redelivery - admin logs improved to better analyze issues when they occur 17 +* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality 18 +* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed 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 +====Bug fixes==== 21 +* Deploy - Deployment plan. Performance of page to deploy a release increased significantly 22 +* Store - Import resources was incorrectly done in specific cases, which is now fixed 23 +* Store - Target namespace will be imported when importing an XML Message Definition 24 +* Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model. 25 +* Store - Importing items from the store sometimes resulted in invalid JMS connection factories.