Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 46.1
edited by Erik Bakker
on 2023/01/31 14:51
Change comment: There is no comment for this version
To version 74.1
edited by Erik Bakker
on 2023/04/28 08:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +196 - The Last Post
Content
... ... @@ -1,53 +1,39 @@
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.
1 +Here is our first release of this quarter. We have delivered additional minor (bug) fixes in this release and released the Live Flow testing feature. The last is a real improvement during the development process of a flow. Furthermore, you will find several enhancements in working in nextGen environments.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.196 - The Last Post.WebHome||target= "blank"]].
4 4  
5 5  =====New features=====
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.
16 16  
17 -=====Minor changes=====
7 +* Create - Flow Testing: Till now, Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), running them, and comparing the actual and expected messages. In this release, "Live Mode Testing" is introduced, making testing communication with an actual "live" endpoint possible. As a result, an "HTTP outbound gateway" can be set in "Live Mode." When you do this, the HTTP outbound gateway will send its request to the endpoint. Consequently, the response will be handled by the flow in the flow test so you can determine whether the actual endpoint behaves as expected.
18 18  
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)
9 +=====Major changes=====
38 38  
11 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target= "blank"]] for more information.
39 39  
40 -====Bug fixes====
13 +=====Minor changes=====
41 41  
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)
15 +* Design - Store: You can encounter a warning message when you import a transformation from the store because your imported transformation requires information from the related store fragment. To avoid a non-functional transformation in the Create phase, you should include that store fragment. Afterward, we will update your default flow component transformer to make it work correctly.
16 +* Design - Store: We updated importing to help you avoid an error while importing store items that will break your message definition in some cases.
17 +* Design - Store: We fixed an issue that you import the message definition(s), and a specialized DataType of imported message definition(s) is not matched with the exported message definition(s). Now, they are matched, and your transformation won't get issues.
18 +* Create - Store: We automatically excluded resources that are not good enough from the exporting wizard. Then you will find it easy to recognize a problem and avoid creating unusable store items.
19 +* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can only change the CDM message definition, Gateway message definition, or even Event streaming message definition with the proper rights. (#690)
20 +* Create - Flow designer: Model resources tab removed on the resources page when adding a resource to a validating filter. (#921)
21 +* Create - Flow designer: Improve the responsiveness of the resources tab on the right panel.
22 +* Create - Flow Designer: Resources in the "Unused resources" section can be marked as used when components refer to the resources through property placeholders or in custom SPeL expressions.
23 +* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests if that parameter was not supplied, so please reset your entry flow to apply the fix.
24 +* Create - API Gateway: We fixed an issue where API-Key secured requests would fail with error code 500 instead of code 401 if no API-Key was supplied. Please reset your entry flow to apply the fix.
25 +* Create - Resources: When viewing a resource, its full name will be shown, removing the need to download the resource to obtain its name. (#922)
26 +* Deploy - Releases: We reduced the time it takes to prepare a release before it can be deployed. The process of building runtime images has been optimized.
27 +* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
28 +* Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543)
29 +* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are run.
30 +* Manage - Explore: A new queue delete button is added. This button is only visible to authorized personnel.
31 +* Administration -User management: Company contact can edit permissions of models that fall under child companies. (#895)
32 +* Administration - Overview: Contracts page removed. (#907)
49 49  
50 -====Remarks====
34 +====Bug fixes====
51 51  
52 -* Mendix Runtime has been upgraded to Mendix 9.21.0.
53 -
36 +* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They better explain what you need them for and mention essential security considerations.
37 +* Create - Flow designer: Various minor (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
38 +* Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514)
39 +* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.