Changes for page 277 - First Farewell

Last modified by Erik Bakker on 2026/09/23 16:09

From version 195.1
edited by CarlijnKokkeler
on 2024/02/13 10:33
Change comment: There is no comment for this version
To version 355.1
edited by Erik Bakker
on 2026/09/10 08:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -214 - System Symphony
1 +276 - API, API
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,21 +1,20 @@
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 various smaller improvements throughout the various phases of the platform. On top of that, it introduces a structured and simple way to navigate to our API MAM functionality for all models using the API Pattern in combination with the API Key security option.
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.276 - API, API.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 +* General - API MAM Migration: Migration wizard for API MAM for API Key API gateway models. This migration wizard enables you to transform your API gateway environment to support multiple authentication methods (OAuth, API key, and basic auth).
9 9  
10 -=====Minor changes=====
9 +==== Minor Changes ====
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. (1141)
11 +* General - Platform: Replaced several older widgets with newer equivalents. As a result, the look and feel of various parts of the platform have changed.
14 14  
15 -====Bug fixes====
13 +===== Bug Fixes ====
16 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. (#802)
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.
15 +* Flow Designer - Save and Create New Version: We fixed a bug that prevented users from transferring their flows to Deploy when their initial action was to create an “Autosaved version” of the flow. (#1816)
16 +* Deploy - Release: We improved the release activation logic to prevent some uncertainty issues during the deployment of the release in the Deploy phase.
20 20  
18 +==== Remarks ====
21 21  
20 +* Updated our //__emagiz.com__// certificate.