Skip to Content

Changes for page 241 - Wild West

Last modified by Erik Bakker on 2025/03/27 09:08
From version 235.1
edited by Erik Bakker
on 2025/03/24 09:05
Change comment: There is no comment for this version
To version 238.1
edited by Erik Bakker
on 2025/03/27 09:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,6 +2,11 @@
2 2  
3 3  Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]].
4 4  
5 +====New Features====
6 +
7 +* Deploy - Releases: A comparison feature for the Deploy phase is added. The comparison feature allows users to compare releases to track the differences in property values of those releases. The feature also provides information on who made the changes. The differences are categorized by “InRelease” and “NotInRelease,” which means that the additional property value is either in the first selected release (InRelease) or the second selected release (NotInRelease).
8 +** This functionality only works for releases created **after** this release.
9 +
5 5  ====Minor Changes====
6 6  
7 7  * Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
... ... @@ -10,6 +10,7 @@
10 10  * Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
11 11  * Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
12 12  * Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
18 +* Infra - Security: Improved security by implementing additional safeguards for AWS native services.
13 13  
14 14  ====Bug fixes====
15 15  
... ... @@ -29,3 +29,7 @@
29 29  * Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
30 30  * Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore moves the user to the queue browser of the correct environment. (#1408)
31 31  * Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed. (#1550)
38 +
39 +====Remarks====
40 +
41 +* New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with **Java 21**, and functionality works as expected.