Skip to Content

Changes for page 245 - Limited Exposure

Last modified by Erik Bakker on 2025/05/21 09:01
From version 249.1
edited by Erik Bakker
on 2025/05/07 15:46
Change comment: There is no comment for this version
To version 45.1
edited by Erik Bakker
on 2023/01/31 14:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -244 - Forgotten Frontiers
1 +191 - Fifty Fifty
Content
... ... @@ -1,22 +1,36 @@
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.
1 +The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.244 - Forgotten Frontiers.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]].
4 4  
5 -====New Features====
5 +=====New features=====
6 +* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
7 +** Error Message is to evaluate the headers of the original message which resulted in an error.
8 +** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
9 +** Queue Consumers is to configure for queues where more than 1 consumer is expected.
10 +** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
11 +** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow.
6 6  
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)
13 +=====Major changes=====
8 8  
9 -====Major Changes====
15 +* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
10 10  
11 -* Create - Add Integrations: We have updated the functionality behind the "Add Integration" overview to support the following deletion cases better. (#1378)
12 -** Users cannot un-transfer an integration in the Create phase if another user is editing a part of the flow attached to the integration.
13 -** Users cannot un-transfer the last integration of a System in the Create phase if another user is editing the connector infra.
14 -** 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.
17 +=====Minor changes=====
15 15  
19 +* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes.
20 +* Create - Flow designer: sensitive information stored in property values is masked. (#790)
21 +* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions.
22 +* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
23 +* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
24 +* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828)
25 +* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
26 +* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
27 +* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
28 +
16 16  ====Bug fixes====
30 +* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
31 +* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793)
32 +* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
33 +* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
34 +* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
35 +* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
17 17  
18 -* 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)
19 -* 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)
20 -* 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.
21 -** 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.
22 -** 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.