Changes for page 189 - Private Eye
Last modified by Carlijn Kokkeler on 2024/05/22 13:43
From version 37.1
edited by Erik Bakker
on 2022/12/08 08:52
on 2022/12/08 08:52
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -18 9-PrivateEye1 +185 - Get Ready - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e bakker1 +XWiki.eMagiz - Content
-
... ... @@ -1,33 +1,22 @@ 1 - Thereleasebringsa privateoreto our communityand makesthe latestruntimeimageavailablefor ourcustomersrunningonthe3rd generationarchitecture.Furthermore, weintroduce severalimprovementstoour 3rdgeneration runtimenditsinteractionwith theportal.1 +Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.18 9-PrivateEye.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.185 - Get ready.WebHome||target="blank"]]. 4 4 5 5 =====New features===== 6 -* A newruntimeimage forcustomermodels running onthe3rd generationruntime.Pleasefind outmoreonour[[Runtime Imagereleasenotes>>Main.ReleaseInformation.RuntimeImages.V110.WebHome||target="blank"]].6 +* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file. 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 - EventStreaming: Eventstreamingis nowavailablefor modelsmigrating to the3rdgenerationruntime.19 - *Create-Transformation:sourcefilteron attributewithmpty fieldismorereadablein read-onlymode.(#732)20 - *Create-Migration: Improvedcompatibility checksrelated to the 3rd generation runtime migration.21 - *Deploy-Check properties: Informativeerrormessageswhen savingorcreating a property. (#576)22 -* Deploy -Deploymentplan:Weimproved thedeploymentplantoavoidit causing problems whenexecuting a deploymentplan containing loads of steps.23 -* Deploy-Architecture:Addedresetfeaturefor3rdgeneration runtimes.10 +* Design System. Changed the look and feel across the portal altogether. Changes can be seen in: 11 + ** Datagids, where there is now on hover action for example. 12 + ** Pop ups 13 + ** Context menus, also have on hover action 14 +* Message Redelivery - admin logs improved to better analyze issues when they occur 15 +* Create - Flow Designer: small bugs ( copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed 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 - 32 -====Remarks==== 33 -* Mendix Runtime has been upgraded to Mendix 9.19.0. 18 +* Deploy - Deployment plan. Performance of page to deploy a release increases significantly 19 +* Store - Import resources was incorrectly done in specific cases, which is now fixed 20 +* Store - Target namespace will be imported when imported XML Message Definition 21 +* Store - When exporting components, if property values contains bus name, they will be updated automatically with new bus name when importing into a new bus. 22 +* Store: Importing items from the store sometimes resulted in invalid JMS connection factories.