Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 150.1
edited by CarlijnKokkeler
on 2023/10/26 11:28
Change comment: There is no comment for this version
To version 315.1
edited by Erik Bakker
on 2026/02/20 13:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +262 - Good News
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,37 +1,28 @@
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 we did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
1 +This release includes many updates to our platform. We are releasing some beta features for customers using our latest version of the API Gateway, allowing them to use multiple authentication methods. On top of that, we have also launched a new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers. Furthermore, we have a series of smaller improvements to enhance your everyday work.
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.262 - Good News.WebHome||target="blank"]].
4 4  
5 -=====Runtime release notes=====
5 +==== Minor changes ====
6 6  
7 -There is a new eMagiz Mendix connector available because a memory leak was found, only affecting customers that have been fully migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture.
7 +* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers is available.
8 +* Create - Flow Designer: The help text for the Result Type attribute of the JSON to XML transformer has been improved. (#1553)
9 +* Deploy - Releases: The on‑hover text for a release also displays the most recent date and time the release was edited. (#341)
10 +* Create - Flow Designer: Unused support objects can be deleted with a single button. (#794)
11 +* Deploy - User Management: For models that have been migrated to our latest functionality for both our event streaming and API offering, changes to users in the Deploy phase will be applied immediately for both manually created users and system users.
12 +* Deploy - Architecture: The Apply to Environment pop-up has been updated to reflect progressive changes made to specific objects. Any pending changes on Container, Router, Certificate, Instance, and AWS resources are now stacked and displayed to the user. The list is ordered from the earliest change at the top to the most recent at the bottom, allowing users to clearly see all modifications made to a specific object until the Apply to Environment button is clicked. These changes will remain active for future operations. (#1537)
13 +* Deploy - Architecture - Routes: The View and Edit pages for Routers have been updated to remove the Endpoint DNS Name and Flow Symbolic Name fields. (#1537)
14 +* Manage - Alerting: For Log and Error triggers, a custom subject can now be specified under ‘notifications’. This enables you to sort incoming alerts in your mailbox more easily.
15 +* Manage - Alerting: We have tightened the allowed characters for the triggers to reduce further the likelihood of HTML injection into the bodies of alerting emails sent by eMagiz.
16 +** Note: if you already have existing alert rules that contain characters that are now considered illegal, you will need to change them when you make any change to that trigger.
8 8  
9 -=====Minor changes=====
18 +==== Bug fixes ====
10 10  
11 -* Design - Message Mapping: The button 'Import from Store' will directly open the store.
12 -* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented.
13 -* Create - Flow Designer: When importing items from the store, flow fragments that are hidden in Design will be listed under the versions in Create. (#1044)
14 -* Create - Flow Designer: Resources without names won't trigger error messages when users select components. (#950)
15 -* Create - Flow Designer: A migration step has been added, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
16 -* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read-only mode.
17 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
18 -* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
19 -* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 7, 14 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
20 -* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
21 -* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
22 -* Manage - Data Sink: The data sink page has been moved to the “Explore” tab. (#946)
23 -* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of the configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
24 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
25 -* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
20 +* Create - FlowDesigner: When using DSH support objects, the required admin-only fields are automatically filled in. (#1755)
21 +* Create - Untransfer integration: We fixed an issue where you could not remove an integration of the Mendix connector system, which was migrated from the Legacy eMagiz Mendix Connector to the current eMagiz Mendix Connector in Create.
22 +* Design - Catalog: Help texts related to “content”, “Json format”, and “Gateway message definition” are updated. (#1082)
23 +* Create - Store: When importing a store component with properties, validation feedback will now be provided if the property value does not align with the expected type. (#1276)
24 +* Manage - Explore: Error message is much more descriptive when the container is not running (#1321)
26 26  
27 -====Bug fixes====
26 +==== Remarks ====
28 28  
29 -* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
30 -* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
31 -* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087)
32 -* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
33 -
34 -
35 -=====Infra and image changes=====
36 -
37 -* 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.
28 +* General - Infrastructure: We updated our image builder for Windows images to use the latest Java versions for images. Effectively, this means that any image built for Windows from this release onwards that uses a base image 3.4.0 or above, will use Java 21.0.10 as baseline. Images below version //3.4.0// will now use Java 17.0.18. Therefore, new (property) releases that use the same eMagiz base image, will still use a different Java version, and may therefore have some changed behavior. Normally that would not be noticable, but since these Java version increases drops support for some weak cipher suites, connectivity may be affected. For more information, please refer to the release notes of image 3.5.1.