Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 162.1
edited by CarlijnKokkeler
on 2023/11/22 15:02
Change comment: There is no comment for this version
To version 306.1
edited by Erik Bakker
on 2026/02/10 08:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +261 - Taking Charge
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,33 +1,16 @@
1 -In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
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.209 - Max Verstappen.WebHome||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 -* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties.
8 -* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 -* All - The next generation architecture is the default now. New models will use this generation as default.
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.
10 10  
11 -=====Minor changes=====
11 +==== Remarks ====
12 12  
13 -* Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
14 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
15 -* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
16 -* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
17 -
18 -====Bug fixes====
19 -
20 -* Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
21 -* Create - Flow Designer: We added a migration step to set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
22 -* Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.
23 -* Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
24 -
25 -====Infra and image changes====
26 -
27 -* Infra: New logging feature enabling us to make better choices in encryption standards.
28 -
29 -
30 -
31 -
32 -
33 -
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.