Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 44.1
edited by Erik Bakker
on 2023/01/23 13:49
Change comment: There is no comment for this version
To version 46.1
edited by Erik Bakker
on 2023/01/31 14:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +191 - Fifty Fifty
Content
... ... @@ -1,32 +1,53 @@
1 -The release finished many new improvements to our 3rd generation runtime offering and fixed various annoying bugs and minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
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.190 - Fast Forward.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 5  =====New features=====
6 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V120.WebHome||target="blank"]].
7 -* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your JMS server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
6 +* Deploy - Architecture: We added the possibility to register network shares in your container volume settings. This enables the use of network shares without having to mount them manually on the host machine and then again on container level. This option is only available for 3rd generation runtimes that run on-premises.
7 +* Deploy - Containers: In Deploy containers a ‘Debug’ option is added for flows on the 3rd generation eMagiz runtime.
8 +** This option will temporarily be available for users on the next generation runtime. It allows to easily wiretap messages from channels in a flow to a queue, which can the be browsed using the queue browser. One flow can be wiretapped at the time, per container.
9 +** To use this option, the model must be fully migrated to Gen3, including the JMS which also needs to be reset. Additionally only flows in a container that has the Gen3 Debugging components inside of the associated container infra flow can be debugged. For more information on how to setup debugging on Gen3, please consult the documentation.
10 +* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
11 +** Error Message is to evaluate the headers of the original message which resulted in an error.
12 +** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
13 +** Queue Consumers is to configure for queues where more than 1 consumer is expected.
14 +** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
15 +** 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.
8 8  
9 -=====Major changes=====
10 -
11 -* 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.
12 -
13 13  =====Minor changes=====
14 14  
15 -* 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.
16 -* Create - Flow designer: sensitive information stored in property values is masked. (#790)
17 -* 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.
18 -* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
19 -* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
20 -* 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)
21 -* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
22 -* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
23 -* 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.
19 +* Data-Limit: Set data limit per environment.
20 +* Login page: Login page /login.html now redirects to the real login page /p/login. (#671)
21 +* Create - Flow designer: Removed the unnecessary refresh button from the component creation pop-ups. (#858)
22 +* Create - Flow designer: Properties in the property overview pages are sorted as Test/Acceptance/Production. (#804)
23 +* Create - Flow designer: We improved validation and help text on Wss4J interceptors components. (#733)
24 +* Create-Flow testing: Improved the help text when adding a header type for a test message. It now clearly states which types of Java classes can be used along with some examples. (#742)
25 +* Deploy - Releases: Setting a release as active by pressing the deploy button creates an entry in the deploy history. (#823)
26 +* Deploy - Releases: We improved the notification popups of failed machine deployments.
27 +* Deploy - Releases: We added column sorting to the popup showing the missing properties. (#860)
28 +* Deploy - Architecture: New cloud slots have their auto-upgrade value set to true by default. (#841)
29 +* Deploy - Architecture: A docker container's status is more visible when you open detail page of the docker container.
30 +* Deploy - Architecture: On the detail page about an instance, the state of the instance is now visible. (#699)
31 +* Deploy - Architecture: We changed the wake-up time of cloud slots on Fridays to 6:00 UTC, so that they no longer fall within our regular deployment windows. (#559)
32 +* Deploy - Architecture: We added runtime memory checks to ‘Apply to environment’, to prevent invalid deployments. (#719)
33 +* Deploy - Properties: We improved runtime selection when copying properties. (#796)
34 +* Manage - Explore: Improved the displayed error message when a message could not be loaded in the message redelivery screen. (#696)
35 +* Manage - Explore: “Save as test message” button opens a pop-up that allows you to edit your test message’s name, description, content and headers before saving it.
36 +* Manage - HTTP statistics: Fixed a typo in HTTP statistics dashboard. (#856)
37 +* Manage - Alerting: By default, no filter is applied to Status when navigating to Notifications, or resetting the filters on Notifications. (#486)
24 24  
39 +
25 25  ====Bug fixes====
26 -* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
27 -* 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)
28 -* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
29 -* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
30 -* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
31 -* 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.
32 32  
42 +* Design - Solution design: We hide systems without functional integration now. (#714)
43 +* Create - API Gateway: Security header case insensitive
44 +* Create - Flow designer: Enabling redelivery for you integration is applied after resetting your offramp and exit flow. Before this change, you needed to remove and add the integration to Create phase to apply this setting.
45 +* Deploy - Containers: Applied styling to the error pop-up with the list of reasons why a runtime can’t be deleted to make it easier to read. (#546)
46 +* Deploy - Architecture: Deploying your model to the cloud for the first time, required you to press ‘Apply to Environment’ twice. This is no longer the case. (#508)
47 +* Deploy-Volumes: Network volumes visible when container not deployed.
48 +* Manage - Monitoring: Fix typo in Event Proccessors Metrics. (#835)
49 +
50 +====Remarks====
51 +
52 +* Mendix Runtime has been upgraded to Mendix 9.21.0.
53 +