Skip to Content

Changes for page 266 - Feel Free

Last modified by Erik Bakker on 2026/04/20 22:05
From version 328.1
edited by Erik Bakker
on 2026/04/20 21:48
Change comment: There is no comment for this version
To version 249.1
edited by Erik Bakker
on 2025/05/07 15:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -266 - Feel Free
1 +244 - Forgotten Frontiers
Content
... ... @@ -1,31 +1,22 @@
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 Seperation.WebHome||target="blank"]] has been pulled due to not meeting quality standards. Having said that, enjoy reading our latest updates on the platform.
1 +In the last sprint, we released several stability options, mainly regarding the deletion behavior within the platform. We also released an update to the flow configuration of Mendix systems to avoid conflicts with another module that you could be using in Mendix, the Excel Importer.
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>>Main.Release Information.Release Blogs.244 - Forgotten Frontiers.WebHome||target="blank"]].
4 4  
5 -==== Minor changes ====
5 +====New Features====
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.
7 +* General - Support: System admins can manually log out other users with active sessions. This is added to cover certain edge cases regarding locked flows. (#1197)
14 14  
15 -==== Bug fixes ====
9 +====Major Changes====
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.
11 +* Create - Add Integrations: We have updated the functionality behind the "Add Integration" overview to support the following deletion cases better. (#1378)
12 +** Users cannot un-transfer an integration in the Create phase if another user is editing a part of the flow attached to the integration.
13 +** Users cannot un-transfer the last integration of a System in the Create phase if another user is editing the connector infra.
14 +** Users can un-transfer the Exit/Entry connector in the Create phase either by selecting one of the integrations or both of the integrations of the Exit/Entry connector. This process is also successful when the Exit/Entry connector is in the Deploy phase.
26 26  
27 -==== Remarks ====
16 +====Bug fixes====
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.
18 +* Design - API Data Model: Users can remove entities that were once part of a gateway message of an API operation that has been removed/un-transferred from the Create Phase. (#1577)
19 +* Create - Flow Designer: Create phase - The help text of the “Max fetch size” property of the “IMAP idle channel adapter” better reflects its behavior and usage. (#1410)
20 +* eMagiz Connector - Flow Configuration: The issue where the new eMagizConnector Mendix module would cause conflicts with the Mendix Excel Importer module has now been resolved.
21 +** If you already have a synchronous messaging flow for a Mendix connector system, this flow must be reset before creating a new release. Make sure this new version is included in your next release. Failing to do so can break error handling for these synchronous entry flows.
22 +** After setting the new release as active, the Mendix application has to be stopped and started to use the new image. This doesn’t have to be done right away, you can await the following restart.