Changes for page 271 - Secure Ship

Last modified by Erik Bakker on 2026/06/29 09:20

From version 329.1
edited by Erik Bakker
on 2026/04/20 21:48
Change comment: There is no comment for this version
To version 343.1
edited by Erik Bakker
on 2026/06/29 09:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -266 - Feel Free
1 +271 - Secure Ship
Content
... ... @@ -1,31 +1,23 @@
1 -This release has a significant impact on users. Both in delivering functional value to our end users and in moving away from a legacy construct within our platform, and taking the UI one step into the future. On top of that, we have squashed some bugs. Sadly, however, we also have to announce that the announced **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** in [[release 264>>doc:Main.Release Information.Release Blogs.264 - Strict Separation.WebHome||target="blank"]] has been pulled due to not meeting quality standards. Having said that, enjoy reading our latest updates on the platform.
1 +This release includes improvements to our certificate rotation mechanism that affect all customers using our event streaming offering. On top of that, new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** are released. Furthermore, additional accelerants for all integration developers are here. This includes improvements in how we assist users in Design, Create, and Deploy.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.266 - Feel Free.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.271 - Secure Ship.WebHome||target="blank"]].
4 4  
5 -==== Minor changes ====
5 +==== New Features ====
6 +* Create - Flow Designer: When copy-pasting flow components with support objects, if a similar support object exists in the target flow, you can choose whether to copy the support object or re-use the existing one. (#978)
6 6  
7 -* General - Event Streaming: To authenticate at DSH, our event streaming broker, we use certificates. These certificates have an expiration date, so they must be rotated. We have introduced a new way of rotating these certificates for you.
8 -** Proxy certificates must always be valid in DSH to prevent clients from encountering issues. A scheduled event runs daily during working hours to verify this.
9 -** If certificate rotation fails in the test environment, it will **not** continue to the acceptance or production environments.
10 -* Create - System: We now show the parent entity when selecting an entity or attribute in the right panel. This allows a user to identify better where in the message's structure they currently are. (#1520)
11 -* Deploy - Release: Creating a new release automatically puts you in “edit mode” for that release. (#672)
12 -* Create - Add Integrations: Improved how we autogenerate flows for the user.
13 -* General - Platform: Improved our general deletion behavior when deleting a model.
8 +==== Minor Changes ====
14 14  
10 +* Design - API Catalog: Removed the “Server” button from this overview, along with all unique configuration related to it, as the button no longer served a function. (#1792)
11 +* Create - Flow Designer: Selecting a parameter when configuring the XSLT parameters of the XSLT transformer can be done with a dropdown. (#1026)
12 +* Deploy - Containers: The “flows that should run on” overview has been restructured to display the main information by default, with an option to show additional information if needed. Furthermore, updated the styling in line with our best practices. (#1768)
13 +
14 +
15 15  ==== Bug fixes ====
16 16  
17 -* Deploy - Upgrade: Fixes a bug where the portainer agent could not be updated, as part of the environment template procedures, for Windows systems where portainer is installed on another drive than C:\. [CSP-1922]
18 -* Manage - Monitoring - HTTP Statistics (Other metrics): The mean and max for the response time are split into two graphs. (#1200)
19 -* Deploy - History: Entries stating 'null' will no longer be shown. (#1479)
20 -* Manage - Monitoring - Log Entries: The search/reset buttons are disabled while the reset/search is still being processed. (#1538)
21 -* Design - Edit an API integration - New/Edit resource: Added reserved keywords for the path of a resource, which can no longer be used. (#1585)
22 -* Create - Transformation - Custom XSLT snippet: Trying to save a newly edited XSLT snippet is only possible in “Edit mode”. (#1670)
23 -* Capture - Integration: Users are prevented from clicking the "Save integration" button too fast after creating a new message type to prevent a timing issue resulting in an error. The save button at the integration level is inactive until a message type is set for that integration. (#531)
24 -* Design - Catalog: The default request body is generated automatically for the POST operation when added as an integration in the Design phase.
25 -* Deploy - Architecture: Fixed an issue in the execution of the environment upgrade for models that have API MAM.
17 +* Capture - Delete System: When being prevented from deleting a system by eMagiz, you no longer are confronted with an everlasting platypus. (#1771)
18 +* Deploy - System: We fixed an issue that, on some occasions, the wrong file location is set for the H2 database if the runtime runs on an on-premises machine.
19 +* Deploy - User Management: We fixed inconsistent errors in Deploy - User Management overview, making it more reliable to manage users and their credentials.
26 26  
27 27  ==== Remarks ====
28 28  
29 -* General - Infrastructure: An update has been applied to the internal communication with the eMagiz-managed authorization server.
30 -* General - Infrastructure: An update has been applied across the platform regarding the UI. As a result, all reference selectors have been replaced with combo boxes, aligning with current best practices and enabling users to interact with the platform more effectively.
31 -** Slightly modified the creation of new message types by implementing a new type of input widget that combines drop-down selection functionality with actions.
23 +* Support employees can trigger a rollback on the intermediate certificate on the customer authorization server.