Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 112.1
edited by CarlijnKokkeler
on 2023/10/11 12:53
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 -206 - Situational Deployment
1 +262 - Good News
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,26 +1,28 @@
1 -In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
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.206 - Situational Deployment.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 -=====New features=====
5 +==== Minor changes ====
6 6  
7 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
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 -* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
12 -* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
13 -* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052)
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)
14 14  
26 +==== Remarks ====
15 15  
16 -====Bug fixes====
17 -
18 -* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
19 -* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
20 -* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
21 -* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
22 -
23 -
24 -=====Infra and image changes=====
25 -
26 -* No infra and/or image changes is this release.
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.