Changes for page 277 - First Farewell

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

From version 355.1
edited by Erik Bakker
on 2026/09/10 08:00
Change comment: There is no comment for this version
To version 266.1
edited by Erik Bakker
on 2025/06/17 09:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -276 - API, API
1 +247 - Help Out
Content
... ... @@ -1,20 +1,12 @@
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.
1 +This release focuses on helping our community by improving various aspects of our platform in anticipation of some of the larger features that are just around the corner. So, without further ado, let's take a look at what's on the menu today!
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.276 - API, API.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.247 - Help Out.WebHome||target="blank"]].
4 4  
5 -==== New Features ====
5 +==== Bug fixes ====
6 6  
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).
8 -
9 -==== Minor Changes ====
10 -
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.
12 -
13 -===== Bug Fixes ====
14 -
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.
17 -
18 -==== Remarks ====
19 -
20 -* Updated our //__emagiz.com__// certificate.
7 +* Design - Architecture: A change is made to ensure that the "Design architecture" is correctly updated based on message type changes in the Capture phase. (#1614)
8 +* Design - System: New help text is generated for the “SOAP entry connector” check box. The check box is present in the "Design phase" while editing the system. (#1413)
9 +* Create - Flow designer: On the "File item reader message source," various help texts have been added to give additional clarity on what the component does. (#1463)
10 +* Create - Flow Designer: Resetting a flow and deploying the changes from the reset flow are corrected so that the flow is deployed with the correct flow version and component list. (#1618)
11 +* Deploy - Architecture: Deploy architecture for displaying the retention bytes is aligned with the Design architecture. It shows the topic retention bytes, as users are only allowed to modify this variable. (#1358)
12 +* Manage - Explore: The bug is fixed so that all the options within the explore section of the Manage phase are responsive at all times. (#1524)