Changes for page 250 - Fix Fest

Last modified by Erik Bakker on 2025/07/28 12:18

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 272.1
edited by Erik Bakker
on 2025/07/28 11:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -249 - Amendment Avalanche
1 +250 - Fix Fest
Content
... ... @@ -1,35 +1,49 @@
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 +This release features numerous updates to our platform, with a user-centric focus. This release, we once again embarked on our traditional Hackathon journey, focused on making the lives of our day-to-day platform users easier.
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.250 - Fix Fest.WebHome||target="blank"]].
4 4  
5 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 +* Create - Flow Designer: Custom resources in the form of XSLT files and Groovy scripts can be previewed and edited directly in the flow designer. (#1115)
8 +* Create - Flow Designer: Two navigation buttons (Start/Stop editing and “Open in Design“) are added to the following pages. (#1607)
9 +** Messaging:
10 +*** System message
11 +*** CDM message
12 +** API gateway:
13 +*** Gateway message
14 +*** System message
15 +** Event streaming:
16 +*** Topic in
17 +*** Topic out
10 10  
11 11  ==== Minor changes ====
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)
21 +* General - Export: When exporting to PNG, the filename now has a logical name, containing the technical name of your model, the phase that was exported, and the time of the export. (#266)
22 +* Capture - Settings: This overview will now show the technical names, when known, of systems as well as their display name. (#810)
23 +* Capture - System: Users can quickly create multiple tenants in a multi-tenant system by using the new button called “Save and add new”. The button saves the previously created tenant and opens a new page to create a new tenant. (#1527)
24 +* Design - Settings: Make clear that only the model owner can alter the settings displayed under Design - Settings (#1638)
25 +* Create - Flow Designer: The expressions of recipient routers are visible in the grid to show the conditions along with them. Additionally, the grid has been updated to Data Grid 2, which offers a more visually appealing display. (#1649)
26 +* Create - Transformation: When viewing a transformation with a datatype conversion from or to ‘date’, ‘time’, or ‘datetime’, the time zone used in the formatting is now shown without the need to enter edit mode. (#945)
27 +* Deploy - Releases: We have updated the UI and user experience in Release > Details > Flow versions and Integrations tabs. Furthermore, we have added the option to display the integration name rather than the message type name, allowing you to see which API operation you are adding or removing from a release. (#1581)
28 +* Deploy - Architecture: Cloudslots that do not have an active environment will not be planned to be upgraded anymore, removing unnecessary emails being delivered to model owners. (#1594)
29 +* Deploy - Properties: Updated hover text of the generate button to reflect that values will be replaced. (#1160)
30 +* Manage - Error Messages: Users with view rights in Manage can now change the status of error messages. (#1669)
26 26  
27 27  ==== Bug fixes ====
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)
34 +* Design - Message Tree: Attribute order is exchanged between the moved attributes rather than making an algebraic calculation to obtain a new value to avoid double jumps during the movement. (#1593)
35 +* Create - Flow Designer: Validation in JDBC stored procedure inbound channel adapter is now shown on the right element. (#1557)
36 +* Create - Message Definition: A Longer time is given to the user to change the fields. Additionally, the pattern field is no longer time-bound, as it requires a longer input. (#1575)
37 +* Create - Flow Designer: Wiretap channel does not cause an error when its ID is too long. (#1606)
38 +* Create - Flow Designer: When changing a filter with a discard channel to start throwing exceptions on rejection instead of sending them to the discard channel, the UI will now correctly reflect this. (#1621)
39 +* Create - Flow Designer: when copying a component which have a field value longer than 64 characters and contains the flow’s name, then pasting, the field will not be limited to 64 characters. (#1398)
40 +* Create - Components: Linetokenizer -> Strict of the Flat file to XML transformer and 'Allow empty array' of the system message are not editable anymore when not in 'start editing'. (#1612)
41 +* Create - Transformation: Users are now able to switch between “Custom XPath” and “Convert datatype” options for the “Transform from date/time” transformer. (#1662)
42 +* Create - Transformation: Users can return to the correct design phase message mapping. (#1348)
43 +* Create - Transformation: User permissions are modified for the From Boolean Transformer so that the user can see the Value Mappings. (#1622)
44 +* Create - Flow Testing: Flow tests that contain Kafka Message Listener Adapter components can be executed again. (#1672)
45 +* Create - Create Flow Version: We fixed an issue where you got an error, which requires Deploy permission, when you create and transfer the new API operation to Deploy, since you only have permission in Capture, Design, and Create. (#1677)
46 +* Deploy - Architecture: You were able to remove pending changes from Deploy Architecture without applying them when pressing cancel after applying changes for a double lane model. (#1651)
47 +* Deploy - Architecture: Resolved the issue where enabling/disabling SSL-configuration in runtime settings could lead to duplicated help text. (#1455)
48 +* Deploy - User Management: We fixed an issue where the list of API operations did not show since these API operations were assigned to the related user. (#1678)
49 +** Additionally, help text is converted to the latest help text format.