Changes for page 277 - First Farewell
Last modified by Erik Bakker on 2026/09/23 16:09
From version 354.1
edited by Erik Bakker
on 2026/09/10 07:59
on 2026/09/10 07:59
Change comment:
There is no comment for this version
To version 268.1
edited by Erik Bakker
on 2025/06/24 10:10
on 2025/06/24 10:10
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -27 6-API,API1 +247.1 - Help Out - Content
-
... ... @@ -1,16 +1,11 @@ 1 -This release in cludesvarioussmallerimprovements throughoutthe variousphasesofthe platform.On topofthat,it introducesa structuredandsimple wayto navigate toour API MAMfunctionalityforallmodelsusingtheAPIPatternincombinationwiththeAPI Key securityoption.1 +This release introduces the ability for beta models to run on our new event broker. With this critical step being reached, we can migrate the first set of beta customers to the new event broker while simultaneously further developing this proposition. 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.2471 - Help Out.WebHome||target="blank"]]. 4 4 5 -==== MinorChanges ====5 +==== New features ==== 6 6 7 -* General - Platform: Replacedseveral olderwidgetswithnewerequivalents.As aresult,thelookandfeel ofvariousparts of theplatformhavechanged.7 +* General - Event Streaming: Run your event streaming solution on our new event broker at DSH. Please note that we will initially release this functionality as a **beta** feature. This means it is currently only available to a select number of models. Once this functionality is more developed, we will share more information on this. 8 8 9 -==== =Bug Fixes ====9 +==== Minor changes ==== 10 10 11 -* 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) 12 -* Deploy - Release: We improved the release activation logic to prevent some uncertainty issues during the deployment of the release in the Deploy phase. 13 - 14 -==== Remarks ==== 15 - 16 -* Updated our //__emagiz.com__// certificate. 11 +* Deploy - User Management: Updated the UI/UX for this overview to provide more context to our users regarding their connected system users, their roles, and their rights.