Changes for page 262 - Good News

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-214 - System Symphony
	1	+261 - Taking Charge

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.CarlijnKokkeler
	1	+XWiki.ebakker

Content

...	...	@@ -1,21 +1,16 @@
1		-In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
	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.214 - System Symphony||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		-=====New features=====
	5	+==== New Features ====
6	6
7		-* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once.
8		-* Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
	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.
9	9
10		-=====Minor changes=====
	11	+==== Remarks ====
11	11
12		-* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore.
13		-* Manage - Monitoring: New functionality to ensure that the monitoring graphs in Manage can show data from the last thirty days. To utilize this, a new runtime image, [[V.2.1.1>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.1/||target="blank"]], is needed.
14		-
15		-====Bug fixes====
16		-
17		-* Create - Flow Designer: The help text of the Group attribute has been improved.
18		-* Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test.
19		-* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen.
20		-
21		-
	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.