Changes for page 256 - Power Up
Last modified by Erik Bakker on 2025/11/04 12:44
From version 289.2
edited by Erik Bakker
on 2025/11/04 12:44
on 2025/11/04 12:44
Change comment:
There is no comment for this version
To version 241.1
edited by Erik Bakker
on 2025/04/07 14:39
on 2025/04/07 14:39
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 56-PowerUp1 +242 - Stability Score - Content
-
... ... @@ -1,15 +1,20 @@ 1 - Thisrelease featuresvariousupdates to ourplatform, withauser-centric focus,asweworkonimprovedfunctionalityforour new eventstreamingbrokerand API Gateway. All thoseimprovementswillbe sharedin the futureonce everythingisready. Additionally, wewant to raiseawarenessthat severalnew**[[environmenttemplates>>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]**havebeen released thatneedto be updatedbefore**December,14th**. Soifyouhaveyettoupdatepleasetake thenecessary actions.1 +In the last sprint, we released several items to improve the platform's stability across the various ILM phases. Our biggest change is a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] that allows models running on our current-generation architecture to better utilize their CPU within the cloud models. In addition, we have released various improvements to the platform regarding clarity and stability. 2 2 3 -Please find out more on our [[Release blog>> doc:Main.Release Information.Release Blogs.256-PowerUp.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.242 - Stability Score.WebHome||target="blank"]]. 4 4 5 -==== Bug fixes====5 +====New Features==== 6 6 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) 7 +* Cloud - Templates: We have implemented a feature for Cloud models to consume an unlimited amount of CPU burst on their production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]. 15 15 9 +====Minor Changes==== 10 + 11 +* Design - Message Definition: When editing a system, CDM, or Gateway message, you can now add and remove attributes to an entity in the message model using an improved version of the ‘Add attribute(s)’ popup in the message designer. 12 +* Store - Overview: The statistics tab in Store item details shows the number of imports and the models where a store item has been imported to, which is only visible to store admins. (#799) 13 +* eMagiz Connector - Softcrow: Softcrow restoration has been added to the eMagiz Connector. 14 + 15 +====Bug fixes==== 16 + 17 +* Create - Transformation: In the Transformation tab of the Create phase. Newly created attribute operations of type aggregator can freely switch positions with a destination filter using the move left or right buttons. (#1307) 18 +* Create - Flow Designer: Updated help texts and documentation references that pointed to Joda time with the relevant Java DateTimeFormatter options to reflect the current state of libraries supported in the runtime images. 19 +* Manage - Triggers: You can no longer add HTML in the trigger’s fields for our current generation of alerts. This is to prevent potential malicious code from ending up in emails sent to customers. 20 +