Skip to Content

Changes for page 262 - Good News

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -262 - Good News
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,28 +1,46 @@
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.
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.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.262 - Good News.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
4 4  
5 -==== Minor changes ====
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.
6 6  
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 +=====Minor changes=====
17 17  
18 -==== Bug fixes ====
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.
19 19  
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)
25 25  
26 -==== Remarks ====
27 27  
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.
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.