Skip to Content

Changes for page 249 - Amendment Avalanche

Last modified by Erik Bakker on 2025/07/14 08:06
From version 132.1
edited by Carlijn Kokkeler
on 2023/10/23 16:26
Change comment: There is no comment for this version
To version 270.1
edited by Erik Bakker
on 2025/07/14 07:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +249 - Amendment Avalanche
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,44 +1,35 @@
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.
1 +This release is characterized by many updates to our platform, both from a user perspective and from a technical perspective regarding our backend services. This sets us up to allow all users to prepare their Mendix systems for a migration to DSH (if applicable). Furthermore, it enables us to assist our users more effectively as they develop within the platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.249 - Amendment Avalanche.WebHome||target="blank"]].
4 4  
5 +==== New features ====
5 5  
6 -=====Minor changes=====
7 +* General - License Tracker: You can now see licensed flows on the model level alongside the company level after we have registered the correct configuration. (#859)
8 +* Event Streaming - DSH Connection: The eMagizConnector base image has been updated as preparation to support event streaming integrations on DSH. This allows all users to prepare their Mendix systems to connect to DSH.
9 +** Note that all users running the new eMagiz Connector will receive this update with their next release. **If you already have a running eMagiz Connector, you need to restart the application to retrieve the latest information after the new release is prepared for you. **
7 7  
8 -* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
9 -* Create - Framework: The framework used in the flow designer has been updated, improving performance.
10 -* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
11 -* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
12 -* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
13 -* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
14 -* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
15 -* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
16 -* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
17 -* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
18 -* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
19 -* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
20 -* 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)
21 -* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
22 -* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
23 -* 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.
24 -* 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.
11 +==== Minor changes ====
25 25  
13 +* Event Streaming - User Management: When adding new event streaming integrations that link to an **existing** event streaming processor, you **must** transfer them to the Create phase via the adding integrations tooling in the Create. This will trigger eMagiz to update the Deploy user management accordingly.
14 +** This functionality applies to both the old and new event broker.
15 +* Design - Message Definition: The overview of the attributes shown in the entity overview of the data model (i.e., CDM) and the system message now also shows the description of the attribute. (#1671)
16 +* Create - Flow Designer: The circuit breaker option under the request handler advice chain can now also be filled with a property placeholder. (#1619)
17 +* Create - Flow Designer: The overwrite option of the headers of a standard header enricher is now placed in the 'Basic' tab instead of the 'Advanced' tab. (#1666)
18 +* Create - Flow Testing: When creating a new test message and selecting the option "from existing file", the default option is now "Create" instead of "Capture". (#1659)
19 +* Create - Flow Testing: Each trace entry in the "Traces" overview now contains a timestamp. (#1661)
20 +* Capture - Overview: Deleting systems/integrations/tenants in Capture now shows a progress bar. (#1665)
21 +* Deploy - Unused Properties: For the unused properties functionality on the Create Phase Release, it is adjusted so that only the properties that are not used in any of your releases across environments are shown. They can be deleted without impacting any of the existing releases. (#1244)
22 +** Context is added to guide users through the following actions.
23 +** Performance has improved significantly. As a result, the process takes less time than before.
24 +* Deploy - Releases: Promoting a release to the next environment does not trigger the auto-delete behaviour of releases anymore. (#1318)
25 +* Deploy - Containers: Only the active containers are updated when a user adds or removes something from a release. Consequently, when a new integration is added, inactive containers will not contain the new integration. They can be reactivated if desired to enable automatic updates again. (#986)
26 26  
27 +==== Bug fixes ====
27 27  
28 -====Bug fixes====
29 -
30 -* 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.
31 -* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
32 -* 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.
33 -* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
34 -* 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)
35 -* 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.
36 -* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
37 -* 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.
38 -* 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".
39 -
40 -
41 -
42 -=====Infra and image changes=====
43 -
44 -* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.
29 +* Create - Add Integrations: We fixed several issues regarding untransferring and transferring integrations. Among other things, we addressed the following specific cases.
30 +* Re-transferring integrations to Deploy
31 +* Untransfering the last integration of a system
32 +* Create - Flow Designer: The user can now completely read the alerts in the flow designer with a hover text. (#1168)
33 +* Create - Flow Designer: The "Allow empty array" checkbox in Create can now be used without it throwing an error. (#1640)
34 +* Create - Flow Designer: We ensured that the order in which you create flow versions for flows belonging to an "exit/entry" construction can be random. As a result, this will prevent users from ending up with only a part of the flows belonging to this construction in Deploy, while all flow versions are indeed created in Create.
35 +* Manage - Alerting - Triggers (Error): Error alerts with ‘not equal to’ and ‘does not contain’ evaluations on ‘exception class’ and/or ‘exception message’ will now only trigger if both the first and last exception don’t equal/contain the value. (#1576)