Skip to Content

Changes for page 266 - Feel Free

Last modified by Erik Bakker on 2026/04/20 22:05
From version 138.1
edited by CarlijnKokkeler
on 2023/10/23 16:42
Change comment: There is no comment for this version
To version 329.1
edited by Erik Bakker
on 2026/04/20 21:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +266 - Feel Free
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,46 +1,31 @@
1 -In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
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.207 - Aligned State .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=====
6 -* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.
5 +==== Minor changes ====
7 7  
8 -=====Minor changes=====
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.
9 9  
10 -* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
11 -* Create - Framework: The framework used in the flow designer has been updated, improving performance.
12 -* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
13 -* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
14 -* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
15 -* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
16 -* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
17 -* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
18 -* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
19 -* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
20 -* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
21 -* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
22 -* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069)
23 -* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
24 -* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
25 -* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.
26 -* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
15 +==== Bug fixes ====
27 27  
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.
28 28  
27 +==== Remarks ====
29 29  
30 -====Bug fixes====
31 -
32 -* Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
33 -* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
34 -* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
35 -* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
36 -* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027)
37 -* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
38 -* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
39 -* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
40 -* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
41 -
42 -
43 -
44 -=====Infra and image changes=====
45 -
46 -* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.
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.