Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 285.1
edited by Erik Bakker
on 2025/10/21 10:07
Change comment: There is no comment for this version
To version 318.1
edited by Erik Bakker
on 2026/02/23 08:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -255 - Fine Form
1 +262 - Good News
Content
... ... @@ -1,23 +1,28 @@
1 -This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready. Additionally, we will release a new **[[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]]** for selected customers and on our flow testing engine.
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>>doc:Main.Release Information.Release Blogs.255 - Fine Form.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 5  ==== Minor changes ====
6 6  
7 -* General - Runtime: A new [[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]], for selected customers and our flow testing will be made available.
8 -* General - eMagiz Store: Introduced a new state generation license type for store items. This license is now required for models intending to utilize store items that depend on state generation capabilities. (#1400)
9 -* Capture - Settings - Integrations: Update column label to be more consistent (#1710)
10 -* Design - Data model: When you change the data type of the attribute in the Design phase while a flow has a transformation in Create, before saving the changes, you will see the confirmation popup with the warning message because the changes will impact your transformation in Create. (#1163)
11 -* Create - Flow testing: Specifying the type of a header on a test message has been made simpler: Instead of having to type the class name, the most common types can now be selected in a dropdown menu instead. It is still possible to provide a custom type. (#1711)
12 -* Deploy - Architecture: We added the refresh button in the footer of the “Runtime details” popup in the Deploy Architecture. (#1708)
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.
13 13  
14 14  ==== Bug fixes ====
15 15  
16 -* Create - Flow designer: Resolved the issue where resizing columns in the ‘Java mail sender’ support object would make the columns ‘stick’ to the mouse. (#1320)
17 -* Create - Flow designer: Several broken Spring documentation references in help texts are updated to new documentation pages. (#1534)
18 -* Deploy - Releases: Changed the text on the wrench icon when hovering for the create phase release to “Property configuration“ to differentiate it from regular property releases. (#1571)
19 -* Deploy - Releases: Resolved the issue where resizing columns in the 'Compare properties' would prevent further interactions with the popup. (#1668)
20 -* Deploy - Releases: Warning message showing the set advised number of flows per container is fixed to show the correct number when a release is approved for the next environment. (#1059)
21 -* Deploy - eMagiz Connector: Resolved the issue where, in some edge cases, downloading the latest release when staring the eMagiz Connector could lead to an error, preventing the connector from starting.
20 +* Create - Flow Designer: 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)
22 22  
26 +==== Remarks ====
23 23  
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.