Skip to Content

Changes for page 266 - Feel Free

Last modified by Erik Bakker on 2026/04/20 22:05
From version 242.1
edited by Erik Bakker
on 2025/04/08 16:39
Change comment: There is no comment for this version
To version 330.1
edited by Erik Bakker
on 2026/04/20 22:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -242 - Stability Score
1 +266 - Feel Free
Content
... ... @@ -1,20 +1,31 @@
1 -In the last sprint, we released several items to improve the platform's stability across the various ILM phases. Our biggest change is a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] that allows models running on our current-generation architecture to better utilize their CPU within the cloud models. In addition, we have released various improvements to the platform regarding clarity and stability.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.242 - Stability Score.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.266 - Feel Free.WebHome||target="blank"]].
4 4  
5 -====New Features====
5 +==== Minor changes ====
6 6  
7 -* Cloud - Templates: We have implemented a feature for Cloud models to improve resource management control within your production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]].
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 +* General - Platform: Improved our general deletion behavior when deleting a model.
11 +* 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)
12 +* Create - Add Integrations: Improved how we autogenerate flows for the user.
13 +* Deploy - Release: Creating a new release automatically puts you in “edit mode” for that release. (#672)
8 8  
9 -====Minor Changes====
15 +==== Bug fixes ====
10 10  
11 -* Design - Message Definition: When editing a system, CDM, or Gateway message, you can now add and remove attributes to an entity in the message model using an improved version of the ‘Add attribute(s)’ popup in the message designer.
12 -* Store - Overview: The statistics tab in Store item details shows the number of imports and the models where a store item has been imported to, which is only visible to store admins. (#799)
13 -* eMagiz Connector - Softcrow: Softcrow restoration has been added to the eMagiz Connector.
17 +* 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)
18 +* Design - Catalog: The default request body is generated automatically for the POST operation when added as an integration in the Design phase.
19 +* Design - Edit an API integration - New/Edit resource: Added reserved keywords for the path of a resource, which can no longer be used. (#1585)
20 +* Create - Transformation - Custom XSLT snippet: Trying to save a newly edited XSLT snippet is only possible in “Edit mode”. (#1670)
21 +* Deploy - Architecture: Fixed an issue in the execution of the environment upgrade for models that have API MAM.
22 +* 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]
23 +* Deploy - History: Entries stating 'null' will no longer be shown. (#1479)
24 +* Manage - Monitoring - HTTP Statistics (Other metrics): The mean and max for the response time are split into two graphs. (#1200)
25 +* Manage - Monitoring - Log Entries: The search/reset buttons are disabled while the reset/search is still being processed. (#1538)
14 14  
15 -====Bug fixes====
27 +==== Remarks ====
16 16  
17 -* Create - Transformation: In the Transformation tab of the Create phase. Newly created attribute operations of type aggregator can freely switch positions with a destination filter using the move left or right buttons. (#1307)
18 -* Create - Flow Designer: Updated help texts and documentation references that pointed to Joda time with the relevant Java DateTimeFormatter options to reflect the current state of libraries supported in the runtime images.
19 -* Manage - Triggers: You can no longer add HTML in the trigger fields for our current generation of alerts. This is to prevent potential malicious code from ending up in emails sent to customers.
20 -
29 +* General - Infrastructure: An update has been applied to the internal communication with the eMagiz-managed authorization server.
30 +* General - Platform: 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.