Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 60.1
edited by Erik Bakker
on 2023/03/14 08:53
Change comment: There is no comment for this version
To version 310.1
edited by Erik Bakker
on 2026/02/10 09:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Giant Leap
1 +261 - Taking Charge
Content
... ... @@ -1,33 +1,16 @@
1 -The release introduces improvements to our 3rd generation runtime architecture and other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
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.194 - Giant Leap.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 -* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]].
8 -* Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers, and waking up a cloud slot will start those containers. (#889)
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 -* Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you use custom error handling on your event processors.
13 -* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807)
14 -* Deploy - User Management: Roles are sorted alphabetically. (#806)
15 -* Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup. Please use the ‘Upgrade’ feature to keep your cloud architecture up-to-date.
16 -* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and chart, and made minor visual improvements.
17 -* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
18 -
19 -====Bug fixes====
20 -
21 -* Generic: We fixed an issue in that you may see a screen with a broken styling when switching among phases.
22 -* Create - Flow Designer: Removed the option to create a new resource on the resource selection popup of a simple XSD schema support object.
23 -* Create - Flow designer: We fixed the flow generation of entry flows for API Key secured API Gateway operations. This problem was introduced in version 193 (2023-02-04). (#902)
24 -* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filenames (>100 characters).
25 -* Deploy - Releases: You need edit rights in the test environment of the deploy phase to execute the “Update flows to latest versions” action.
26 -* Manage - Dashboard: We update the view to visualize the split entries after you migrate combined entries.
27 -* Manage - Logging: When a container cannot be started due to an incorrect stylesheet, the error message will include what the error is and in which stylesheet it occurred (#825)
28 -* Manage - Logging: Reduced the occurrence of 'Failed to send to Elastic' log messages which trigger alerts. (#898)
29 -* Manage - Alerting: Editable column shows the correct value.
30 -
31 -====Remarks====
32 -
33 -* Create - Flow designer: After the deployment, the ‘Version Compare' and 'Version Restore’ features will be unavailable for a few hours because of data migration. You will get an error stating that the version is incompatible with the selected feature until the migration is finished.
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.