Skip to Content

Changes for page 254 - Other One

Last modified by Erik Bakker on 2025/10/09 11:13
From version 271.1
edited by Erik Bakker
on 2025/07/14 08:06
Change comment: There is no comment for this version
To version 68.1
edited by Erik Bakker
on 2023/04/13 14:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -249 - Amendment Avalanche
1 +195 - Easter Party
Content
... ... @@ -1,35 +1,43 @@
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.
1 +As the quarter has ended, we went silent for a couple of weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.249 - Amendment Avalanche.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.195 - Easter Party.WebHome||target= "blank"]].
4 4  
5 -==== New features ====
5 +=====New features=====
6 6  
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 +* Deploy - Releases: We take the first step to fix properties to a release. This gives users more control over properties. For example, they can ensure that the release contains suitable properties that are more manageable.
8 +** When this release reaches production, the first new release that users activate and have Gen3 containers/properties, the new feature becomes active. Users will see a wrench icon on the release. When they click on it, they will see an overview of the attached Gen3 properties.
9 +** These properties cannot be altered for that specific release. This only counts for Gen3 properties, properties for Gen2 runtimes/machines will still be fetched from the Deploy-Properties list and can still be altered. If users notice that a specific Gen3 property of a release not contains the correct value, users can edit the value by opening the property overview of the release. At the bottom of the overview, the option ‘Change properties’ allows users to edit the properties of a release.
10 +** A new ‘property’ release will be created when users use that option. A ‘property’ release can be identified by a suffix that contains a letter. Users can change the properties, and when they are done, they can directly activate and deploy the release. With our new improvements to the deployment plan, only the affected containers by the property change(s) will be redeployed. This will result in faster deployments.
10 10  
11 -==== Minor changes ====
12 +{{info}}Important to note is that
13 +* While changing a property in a ‘property’ release, users also have the option to alter the value in the Deploy-Properties list. By default, this is set to Yes, because when a new release is created, the values of Deploy-Properties will be used and not properties of an earlier release. When a user closes the screen for editing a property, the change will immediately be implemented.
14 +* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release.
15 +* There is a maximum of twenty-six ‘property’ releases. (twenty-six letters of the alphabet)
16 +* Only the latest release can be edited. This can be identified by checking the suffix. The suffix with the latest letter of the alphabet is editable.{{/info}}
12 12  
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)
18 +=====Minor changes=====
26 26  
27 -==== Bug fixes ====
20 +* General - Control Tower: Changed several generic triggers for more predictable behavior.
21 +* Administration - License Tracker: The license tracker has been updated for new license models and features.
22 +* Administration - License Tracker: When the feature ‘Data sink’ is enabled, the number of message packs of the contract will be displayed when you hover with the mouse over the feature.
23 +* Capture - Settings: Editing message types are now consistent between new and existing ones. (#884)
24 +* Design - API Gateway: Default HTTP responses are generated automatically (#417)
25 +* Design - Solution design: An additional option is added to the context menu that navigates to the message definition added to event streaming topics without processors. (#850)
26 +* Create - Add Integrations: We used the name of the API integration that you set in the Design phase to display on the Transfer screen. That helps you choose the correct integrations to add to the Create phase more quickly.
27 +* Create - 3rd Generation Migration: You can toggle the custom error handling option for your event processors while migrating your event processing container to the 3rd Generation Runtime.
28 +* Deploy - Deployment plan: When you run your deployment plan in your model using the new generation runtimes, you will be able to be the logs that relate to an executing deployment step.
29 +* Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan.
30 +* Deploy - Architecture: Certificates only editable by system admin.
31 +* Manage - Jobs: In case the model has containers that contain jobs in one of its flows, users can inspect job managers, job executions, and job step executions. Note that this only works for the 3rd generation runtime.
28 28  
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)
33 +====Bug fixes====
34 +
35 +* General - Runtime Image: A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V140.WebHome||target="blank"]].
36 +* Design - API Gateway: Improved generation of Open API JSON and example messages for API gateway operations to handle cases where an element in your gateway definition is used multiple times. (#440)
37 +* Design - API Gateway: We fixed an issue where changing the message format of a gateway message did not result in an update of the OpenAPI (i.e., Swagger) document.
38 +* Design - System message: We fixed an issue that led to importing towards the wrong message definition when the option "Import from XSD" was chosen on a synchronous message. (#818)
39 +* Create - Message: When viewing or editing an enumeration, it is no longer deleted when the cancel button is pressed.
40 +
41 +====Remarks====
42 +
43 +* Deploy - Releases: We removed the existing snapshots of release property values.