Changes for page 262 - Good News

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-236 - Another Agent
	1	+261 - Taking Charge

Content

...	...	@@ -1,20 +1,16 @@
1		-In the last sprint cycle, we focused on delivering new [[cloud templates>>Main.Release Information.Cloud Templates||target="blank"]] for docker single and docker double lane. Moreover, we have addressed several key feedback points within our platform.
	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.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.236 - Another Agent||target="blank"]].
	3	+Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.261 - Taking Charge.WebHome||target="blank"]].
4	4
5		-====Major Changes====
	5	+==== New Features ====
6	6
7		-* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
	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	8
9		-====Minor Changes====
	11	+==== Remarks ====
10	10
11		-* Create - Flow Designer: Improved help texts for the FTP & SFTP local filter options.
12		-* Deploy - Overview: Spring6 pop-up has been removed.
13		-* Manage - Alerting: The recipients tab for the new Alerting triggers has seen a small update in regards of UX: You will get an explanation when you are trying to enable notifications when no recipients are selected yet.
14		-
15		-====Bug fixes====
16		-
17		-* Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456)
18		-* Create - Transfer Settings: You can now increase and decrease the number of runtimes for existing Systems. And transfer them from Design Architecture to Deploy Architecture. This can be done in “Create – Settings - Transfer Settings from Design”. (#1543)
19		-* Manage - Alerting: Inactive users in your model are removed from the list of selectable recipients.
20		-
	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.