Changes for page 222 - Flee Frustration

Last modified by Bouke Reitsma on 2024/06/06 09:20

From version 37.1
edited by Erik Bakker
on 2022/12/08 08:52
Change comment: There is no comment for this version
To version 53.1
edited by Erik Bakker
on 2023/03/03 08:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +193 - Fan Out
Content
... ... @@ -1,33 +1,23 @@
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 +The release introduces REST/XML as option for your gateway operations as well as new features for our 3rd generation runtime, a new runtime image, and new cloud templates. Subsequently, we will release several minor feedback points and bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.189 - Private Eye.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.193 - Fan Out.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  
8 -=====Major changes=====
7 +* 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.V130.WebHome||target="blank"]].
8 +* Deploy - Releases: New release properties pop-up that shows all properties in your release, grouped by containers that they are assigned to. This pop-up can be accessed by pressing the wrench shaped icon, which becomes available once a release is set as active.
9 +* Design - Settings: We added XML support to API Management. To enable this feature, change the 'Default message format' in the Design settings section. You can change individual operations by changing the message format of your gateway message. Migrating existing operations requires a reset of the exit flow and a change in the catalog in Design. For more information see the release blog post. (#815)
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.
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.
13 +* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
14 +* Design - API Catalog: When you change a path in Design phase, your HTTP inbound gateways that use the changed path will also be updated in Create phase if you have edit rights. (#524)
15 +* Manage - Error messages: Message history is sorted by timestamp descending.
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 31  
32 -====Remarks====
33 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
19 +* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming (#908)
20 +* Create - Migration: We fixed a third generation migration issue, where the legacy error handling flow components were not removed from the asynchronous routing flow.
21 +* Create - Flow designer: when migrating a container’s flows from gen2 to gen 3, “global wire tap” components and their relevant components will be removed.
22 +* Deploy - Release: We fixed an issue that caused images to not be built in specific situations when running in the new runtime generation runtime.
23 +* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)