Changes for page 262 - Good News

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-261 - Taking Charge
	1	+185 - Get Ready

Content

...	...	@@ -1,16 +1,24 @@
1		-This release includes a lot of updates to our platform. We are releasing some beta features for customers utilizing our latest version of the API Gateway allowing to use multiple authentication methods. On top of that we will release a new environment template that will update a multitude of configurations on cloud and on-premise machines. Furthermore, we have a series of smaller improvements to bring delight to your everyday 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 - Taking Charge.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.185 - Get ready.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	+* Message Redelivery - admin logs improved to better analyze issues when they occur
	16	+* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality
	17	+* 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.
	19	+====Bug fixes====
	20	+* Deploy - Deployment plan. Performance of page to deploy a release increased significantly
	21	+* Store - Import resources was incorrectly done in specific cases, which is now fixed
	22	+* Store - Target namespace will be imported when imported XML Message Definition
	23	+* Store - When exporting components, if property values contains bus name, they will be updated automatically with new bus name when importing into a new bus.
	24	+* Store: Importing items from the store sometimes resulted in invalid JMS connection factories.