Skip to Content

Changes for page 245 - Limited Exposure

Last modified by Erik Bakker on 2025/05/21 09:01
From version 234.1
edited by Erik Bakker
on 2025/03/24 06:40
Change comment: There is no comment for this version
To version 254.1
edited by Erik Bakker
on 2025/05/20 14:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -241 - Wild West
1 +245 - Limited Exposure
Content
... ... @@ -1,31 +1,18 @@
1 -In the last sprint, we have released a lot in terms of usability improvements both while working within the various phases of eMagiz as well as 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 functionality to increase the stability of Windows runtimes. This means that those runtimes are now better limited in the memory they can utilize to prevent resource limitations on the machine level. Furthermore, we introduced several small improvements on the platform.
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.245 - Limited Exposure.WebHome||target= "blank"]].
4 4  
5 5  ====Minor 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 not allowed in the technical name anymore. The technical name can only consist of lower case 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 create. 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.
7 +* Deploy - General: For current deployed Windows machines, the calculation of the memory limit of containers is updated, which will prevent memory leaks.
8 +* Deploy - Architecture: You can now manually set the memory of your on-premise machine in design architecture. This memory is considered when checking the machine's health in "Deploy architecture."
9 +* Q&A Forum - Moderation: Q&A Forum Moderators can choose to receive notifications by email about newly posted questions on the forum. (#1401)
10 +* General - eMagiz Connector: The new version is available in the Mendix Marketplace.
11 +** The eMagizConnector base image has been updated in preparation to support event streaming integrations.
12 +** The eMagizConnector Mendix module has been updated in preparation for event streaming support.
13 13  
14 14  ====Bug fixes====
15 15  
16 -* Capture - Add System: When a user tries to creates a system or edits a system, loading bar is displayed before showing the pop-up. (#1228)
17 -* Capture - Edit System: When editing a system, the validation now takes into account that the name cannot be an empty string. (#1562)
18 -* Design - Message Definition: small improvements are introduced:
19 -** the widget can prevent user multiple message attributes on a message entity for the same attribute in datamodel.
20 -** when adding a new message entity to a current message entity, it doesn’t throw exception when user double click to many times in Save button
21 -* Design - Catalog: When exporting swagger json, in case an operation has example in request, the example will be shown correctly in swagger. (#1597)
22 -* 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)
23 -* Create - Add Integrations: Users are able to untransfer a flow even when there is a property attached to the flow. (#1590)
24 -* Create - Add Integrations: Flow, flow versions and the corresponding integration in the Deploy phase is cleaned when an integration is utransferred from the Create phase.
25 -* Create - Components: The browser page now displays the correct page title (#1509)
26 -* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
27 -* 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)
28 -* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already a property description in place. (#1526)
29 -* Deploy - Environment Template: Fixed a bug where upgrading a fully on-premise environment would incorrectly exclude some machines.
30 -* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore now moves the user to the queue browser of the correct environment. (#1408)
31 -* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents that flows using code mappings may encounter errors when stopping their runtime and messages were still processed. (#1550)
16 +* Create - Flow designer: The help text for the "value expression" field for the "duplicate detector" support object better reflects the purpose of that field while also providing practical examples. (#1376)
17 +* Create - Flow Designer: The help text for the "virtual root "field of the "JSON source factory "support object better reflects the functionality and behavior of the field while also stating that arrays on the root level are not supported. (#1459)
18 +* General - User Access: Users with view rights in Deploy and Manage (but no rights in the other phases) can now see data in Manage grids. (#1525)