Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 88.1
edited by Erik Bakker
on 2023/06/06 08:36
Change comment: There is no comment for this version
To version 291.1
edited by Erik Bakker
on 2025/11/04 12:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +256 - Power Up
Content
... ... @@ -1,20 +1,15 @@
1 -In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture, the store, security, and certificate management.
1 +This release features various updates to our platform, with a user-centric focus, as we work on improved functionality for our new event streaming broker and API Gateway. All those improvements will be shared in the future once everything is ready. Additionally, we want to raise awareness that several new **[[environment templates>> Main.Release Information.Cloud Templates.WebHome||target="blank"]]** have been released that need to be updated before **December, 14th**. So if you have yet to update please take the necessary actions.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.256 - Power Up.WebHome||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +==== Bug fixes ====
6 6  
7 -* Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store.
8 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 -* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899)
10 -* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately three months before event streaming users' access certificates expire.
11 -* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan.
12 -* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960)
13 -* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.
14 -* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.
7 +* Design - System Message: Improved performance of saving entities whith a large number of attributes. (#1731)
8 +* Design - Store: Two fixes on importing store items for synchronous messages. (#1579)
9 +** From store functionality for API Gateway is restored.
10 +** Additionally, users can import store item to synchronous system message - response message.
11 +* Design - Create - System Message (API integrations) - The request system message correctly displays the message definition (#1713)
12 +* Create - Add Integrations: We have fixed a bug where some Mendix systems could face an error when trying to add an event streaming integration in Create.
13 +* Deploy - Containers: Debug icon has on hover text (#1725)
14 +* Manage - Alerting: Partial words from an alert's description can be searched and still return accurate results. (#1726)
15 15  
16 -====Bug fixes====
17 -
18 -* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864)
19 -* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937)
20 -