Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 41.1
edited by Erik Bakker
on 2023/01/18 11:22
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 -190 - Fast Forward
1 +196 - The Last Post
Content
... ... @@ -1,34 +1,39 @@
1 -The release brings a private store to our community and makes the latest runtime image available for our customers running on the 3rd generation architecture. Furthermore, we introduce several improvements to our 3rd generation runtime and its interaction with the portal.
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.190 - Fast Forward.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 -* 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.V110.WebHome||target="blank"]].
7 7  
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.
8 +
8 8  =====Major changes=====
9 9  
10 -* Store - Private store. This release introduces the private store with the following features:
11 -** Store items will be private by default and are only accessible for users that belong to the same company as the user that exported the store content. Note that the store item needs to be approved before it is visible to users.
12 -** A new user role, "Store Exporter," will be introduced and can be assigned to the users who can create and update store items.
13 -** Approval of a store item will be executed by eMagiz personnel, who can also set a store item to be public.
14 -** Public store items will be importable by all users.
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.
15 15  
16 16  =====Minor changes=====
17 17  
18 -* Create - Event Streaming: Event streaming is now available for models migrating to the 3rd generation runtime.
19 -* Create - Transformation: source filter on attribute with empty field is more readable in read-only mode. (#732)
20 -* Create - Migration: Improved compatibility checks related to the 3rd generation runtime migration.
21 -* Deploy - Check properties: Informative error messages when saving or creating a property. (#576)
22 -* Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps.
23 -* Deploy - Architecture: Added reset feature for 3rd generation runtimes.
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)
24 24  
25 25  ====Bug fixes====
26 -* Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows.
27 -* Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances.
28 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish.
29 -* Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798)
30 -* Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment.
31 -* Deploy - Architecture: 3rd generation runtimes are included in runtime checks while upgrading your cloud environment.
32 32  
33 -====Remarks====
34 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
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.