Changes for page 189 - Private Eye
Last modified by Carlijn Kokkeler on 2024/05/22 13:43
From version 40.1
edited by Erik Bakker
on 2022/12/22 13:15
on 2022/12/22 13:15
Change comment:
There is no comment for this version
To version 23.1
edited by Erik Bakker
on 2022/11/21 13:13
on 2022/11/21 13:13
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -18 9-Private Eye1 +188 - Close Encounters - Content
-
... ... @@ -1,34 +1,25 @@ 1 -The release brings a pr ivatestore to ourcommunity andmakes thelatestruntimeimageavailable for our customersrunning onthe3rd generationarchitecture.Furthermore, weintroduce severalimprovements to our 3rdgenerationruntime anditsinteraction with the portal.1 +The release brings several improvements to our 3rd generation runtime and the interaction with it. On top of that, we have several feedback items and bug fixes. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.18 9-Private Eye.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.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"]]. 6 +* Design - Store: It is now possible to import Transformations and Data Models from the store into a model. 7 +** The Design Store can also be opened from the Mapping and Data Model screens. 8 +** The Design Store now offers search options for store items, including Transformations and Data Models. 9 +** When importing a Store item with a Transformation or Data Model, a new merge tool is available to link the Store Items data model to the users' data model or to add new attributes/entities to the user data model. 10 +** When importing a Store item with a data model that has been previously linked, the links are automatically restored, allowing for easy updating of store-based Integrations and easier installation of multiple Store items with the same data model. 7 7 8 -=====Major changes===== 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. 14 +* Create - Flow Designer: Code mapping is now available for models migrating to the 3rd generation runtime 15 +* Create - eMagiz Mendix Connector exit: Download buttons are added for non-legacy eMagiz Mendix connectors. 16 +* Create - Overview: You will now see your errors within a flow but on the Create - Overview. To activate this, open your flow, and the number of errors you have in it, if any, will update so that next time, you don't have to navigate inside the flow to check how many alerts you have. 24 24 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. 19 +====Bug fixes==== 20 +* Design - Store: Importing store items from response messages doesn't cause issues anymore. 21 +* Design - Store: Importing response messages and transformation to API integration is possible. 22 +* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document. (#783) 23 +* Create - Flow Designer: Ensure that the copy and pasting experience works for all flows. 24 +* Create - Flow Designer - Store: We fixed the maintaining selection of flow fragments from the store. 25 +* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed. (#744)