Skip to Content

Changes for page 245 - Limited Exposure

Last modified by Erik Bakker on 2025/05/21 09:01
From version 237.1
edited by Erik Bakker
on 2025/03/24 14:46
Change comment: There is no comment for this version
To version 250.1
edited by Erik Bakker
on 2025/05/07 15:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -241 - Wild West
1 +244 - Forgotten Frontiers
Content
... ... @@ -1,36 +1,19 @@
1 -In the last sprint, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] containing a much-needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.
1 +In the last sprint, we released several stability options, mainly regarding the deletion behavior within the platform. We also released an update to the flow configuration of Mendix systems to avoid conflicts with another module that you could be using in Mendix, the Excel Importer.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.244 - Forgotten Frontiers.WebHome||target="blank"]].
4 4  
5 -====Minor Changes====
5 +====Major Changes====
6 6  
7 -* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
8 -* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture because this field was not visible enough in the rest of the portal. (#1608)
9 -* Capture / Design: For new systems, message types, machines, tenants, and models, hyphens are **no longer allowed** in the technical name. The technical name can only consist of lowercase letters and digits and must start with a letter. This also applies to systems, message types, and tenants that have not yet been transferred from design to creation. The portal will give an error message while transferring, and the hyphen has to be removed manually.
10 -* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
11 -* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
12 -* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
13 -* Infra - Security: Improved security by implementing additional safeguards for AWS native services.
7 +* General - Support: System admins can manually log out other users with active sessions. This is added to cover certain edge cases regarding locked flows. (#1197)
8 +* Create - Add Integrations: We have updated the functionality behind the "Add Integration" overview to support the following deletion cases better. (#1378)
9 +** Users cannot un-transfer an integration in the Create phase if another user is editing a part of the flow attached to the integration.
10 +** Users cannot un-transfer the last integration of a System in the Create phase if another user is editing the connector infra.
11 +** Users can un-transfer the Exit/Entry connector in the Create phase either by selecting one of the integrations or both of the integrations of the Exit/Entry connector. This process is also successful when the Exit/Entry connector is in the Deploy phase.
14 14  
15 15  ====Bug fixes====
16 16  
17 -* Capture - Add System: A loading bar is displayed before showing the pop-up when a user tries to create or edit a system. (#1228)
18 -* Capture - Edit System: When editing a system, the validation now considers that the name cannot be an empty string. (#1562)
19 -* Design - Message Definition: Two minor improvements are introduced:
20 -** The widget prevents users from adding the same message attribute within a message definition multiple times.
21 -** When adding a new message entity within your message definition and expanding the existing message definition, it doesn’t throw an exception when the user presses the Save button multiple times in a short time frame.
22 -* Design - Catalog: When creating the Swagger JSON, all custom examples users add will be shown correctly when displaying the Swagger. (#1597)
23 -* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513)
24 -* Create - Add Integrations: Users can untransfer a flow even when there is a property attached to the flow. (#1590)
25 -* Create - Add Integrations: When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned.
26 -* Create - Components: The browser page now displays the correct page title (#1509)
27 -* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
28 -* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560)
29 -* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already an existing property description. (#1526)
30 -* Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
31 -* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore moves the user to the queue browser of the correct environment. (#1408)
32 -* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed. (#1550)
33 -
34 -====Remarks====
35 -
36 -* New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with **Java 21**, and functionality works as expected.
15 +* Design - API Data Model: Users can remove entities that were once part of a gateway message of an API operation that has been removed/un-transferred from the Create Phase. (#1577)
16 +* Create - Flow Designer: Create phase - The help text of the “Max fetch size” property of the “IMAP idle channel adapter” better reflects its behavior and usage. (#1410)
17 +* eMagiz Connector - Flow Configuration: The issue where the new eMagizConnector Mendix module would cause conflicts with the Mendix Excel Importer module has now been resolved.
18 +** If you already have a synchronous messaging flow for a Mendix connector system, this flow must be reset before creating a new release. Make sure this new version is included in your next release. Failing to do so can break error handling for these synchronous entry flows.
19 +** After setting the new release as active, the Mendix application has to be stopped and started to use the new image. This doesn’t have to be done right away, you can await the following restart.