Skip to Content

Changes for page 189 - Private Eye

Last modified by Carlijn Kokkeler on 2024/05/22 13:43
From version 27.1
edited by Erik Bakker
on 2022/11/21 14:16
Change comment: There is no comment for this version
To version 37.1
edited by Erik Bakker
on 2022/12/08 08:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +189 - Private Eye
Content
... ... @@ -1,22 +1,33 @@
1 -The release brings several improvements to our 3rd generation runtime and its interaction with the portal. On top of that, we have several feedback items and bug fixes.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.189 - Private Eye.WebHome||target="blank"]].
4 4  
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 +
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 +
5 5  =====Minor changes=====
6 6  
7 -* General: Code mapping is now available for models migrating to the 3rd generation runtime.
8 -* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785)
9 -* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you.
10 -* Deploy - Deployment plan: When a runtime is being deployed, which is constantly crashing and thereby causing problems, the restart of the runtime is limited to just five times. (#720)
11 -** After five times, the runtime will remain in the stopped state.
12 -* Deploy - Releases: The activate release functionality performance for models that use the 3rd generation runtime is improved.
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 13  
14 14  ====Bug fixes====
15 -* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717)
16 -* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
17 -* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
18 -* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
19 -* Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture.
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.
20 20  
21 21  ====Remarks====
22 22  * Mendix Runtime has been upgraded to Mendix 9.19.0.