10.12.9 Studio Pro Release Notes

content/en/docs/releasenotes/studio-pro/10/10.12.md

@@ -8,14 +8,38 @@ mts: true
 # KI: "Line endings": SOLP-1794 
 # KI: "A finished parallel split path": WOR-1623
 # KI: "Positioning error": LFX-712
-# KI: "When importing Marketplace modules": APPEXT-796
 ---
 
 {{% alert color="info" %}}
 This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for apps in production.
 {{% /alert %}}
 
-## 10.12.8
+## 10.12.9 {#10129}
+
+**Release date: October 28, 2024**
+
+{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/10.12.9" text="Go to Marketplace" title="Download version 10.12.9 from the Marketplace" %}}
+
+### Improvements
+
+* Logs generated from Git (our version control system) are now automatically directed into a dedicated subdirectory within the main logs folder.
+
+### Fixes
+
+
+* We fixed an exception (the **Oops** pop-up window) that occurred when an unknown variable was being used in the microflow expression editor. (Ticket 222410)
+* We fixed an issue in offline apps that after synchronization an object was not found by the **Retrieve By Association** action in case of a reverse association traversal. (Ticket 231027)
+* We fixed an issue that resulted in an **Oops** pop-up window when using the Combo Box widget and accessing its **Properties** pane. (Ticket 231451)
+
+### Known Issues
+
+* Line endings in CSS files are not being handled properly, so when using [Revert All Changes](/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](/refguide/version-control-menu/#show-changes) dialog box.
+  * Workaround: For details, see [this section](/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*.
+* A finished parallel split path that is removed from a running workflow instance wrongly leads to a versioning conflict. Please note that "path" was called "branch" in earlier versions.
+* There is a positioning error in the logic editors when you are dragging a large element, such as a loop, into a sequence flow, it overlaps with the existing elements.
+* Studio Pro on Mac loads user settings from the previous version of the application.
+
+## 10.12.8 {#10128}
 
 **Release date: October 18, 2024**
 
@@ -32,15 +56,13 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 
 ### Known Issues
 
-* When importing Marketplace modules with Studio Pro, their version numbers do not represent the module's version. Instead they mention the current Studio Pro version. This does not affect previously imported Marketplace modules.
-  * Fixed in [10.14.0](/releasenotes/studio-pro/10.14/#fix-marketplace-modules).
 * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](/refguide/version-control-menu/#show-changes) dialog box.
   * Workaround: For details, see [this section](/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*.
 * A finished parallel split path that is removed from a running workflow instance wrongly leads to a versioning conflict. Please note that "path" was called "branch" in earlier versions.
 * There is a positioning error in the logic editors when you are dragging a large element, such as a loop, into a sequence flow, it overlaps with the existing elements.
 * Studio Pro on Mac loads user settings from the previous version of the application.
 
-## 10.12.7
+## 10.12.7 {#10127}
 
 **Release date: October 11, 2024**
 
@@ -69,8 +91,6 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 
 ### Known Issues
 
-* When importing Marketplace modules with Studio Pro, their version numbers do not represent the module's version. Instead they mention the current Studio Pro version. This does not affect previously imported Marketplace modules.
-  * Fixed in [10.14.0](/releasenotes/studio-pro/10.14/#fix-marketplace-modules).
 * <a id="import-platform-supported-module"></a>Importing a platform-supported Marketplace module containing a Java action fails when the project does not have managed Java dependencies or when Gradle synchronization for managed Java dependencies is disabled. In these cases there is no `vendorlib` folder in the project directory, causing the import to fail.
   * Fixed in [10.6.17](/releasenotes/studio-pro/10.6/#fix-import-platform-supported-module) and [10.12.8](#fix-import-platform-supported-module).
 * <a id="upgrade-platform-supported-module"></a>Upgrading a platform-supported Marketplace module containing a Java action fails. Or adding a platform supported module that contains Java dependencies that are already used by the project fails. In these cases the project `vendorlib` directory already contains the same *.jar* files as the new module, which will fail the import process.
@@ -82,7 +102,7 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 * Studio Pro on Mac loads user settings from the previous version of the application.
 
 
-## 10.12.6
+## 10.12.6 {#10126}
 
 **Release date: September 30, 2024**
 
@@ -115,10 +135,8 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 * We fixed an issue where an **Oops** dialog was shown when the [Data Widgets](https://marketplace.mendix.com/link/component/116540?_gl=1*jpe0m1*_gcl_au*MTg4MTk2NjAyMi4xNzIxODA1MDU2) module was updated to version 2.24.0 or above, when a data grid 2 was configured with a column using the `owner` or `changedBy` system association.
 ### Known Issues
 
-* When importing Marketplace modules with Studio Pro, their version numbers do not represent the module's version. Instead they mention the current Studio Pro version. This does not affect previously imported Marketplace modules.
-    * Fixed in [10.14.0](/releasenotes/studio-pro/10.14/#fix-marketplace-modules).
 * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](/refguide/version-control-menu/#show-changes) dialog box.
-  * Workaround: For details, see [this section](/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*.
+    * Workaround: For details, see [this section](/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*.
 * A finished parallel split path that is removed from a running workflow instance wrongly leads to a versioning conflict. Please note that "path" was called "branch" in earlier versions.
 * There is a positioning error in the logic editors when you are dragging a large element, such as a loop, into a sequence flow, it overlaps with the existing elements.
 * Studio Pro on Mac loads user settings from the previous version of the application.
@@ -155,8 +173,6 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 
 ### Known Issues
 
-* When importing Marketplace modules with Studio Pro, their version numbers do not represent the module's version. Instead they mention the current Studio Pro version. This does not affect previously imported Marketplace modules.
-    * Fixed in [10.14.0](/releasenotes/studio-pro/10.14/#fix-marketplace-modules).
 * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](/refguide/version-control-menu/#show-changes) dialog box.
     * Workaround: For details, see [this section](/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*.
 * A finished parallel split path that is removed from a running workflow instance wrongly leads to a versioning conflict. Please note that "path" was called "branch" in earlier versions.