Mx10 references and To Dos

Author: MarkvanMents

content/en/docs/refguide/general/mx-command-line-tool/_index.md

@@ -11,6 +11,8 @@ The mx tool is a Windows and Linux command-line tool that can be used to perform
 
 ## Location
 
+{{% todo %}}Should we use an Mx 11 example here?{{% /todo %}}
+
 Mendix Studio Pro comes with the mx command-line tool. You can find the executable *mx.exe* file in the same folder that contains *studiopro.exe* (for example, *C:\Program Files\Mendix\10.0.0.5003\modeler\mx.exe*). It is also included if you download [mxbuild](/refguide/mxbuild/).
 
 ## Available Commands

content/en/docs/refguide/general/mx-command-line-tool/analyze-mpr.md

@@ -42,6 +42,8 @@ Valid examples are given below:
 
 An example of the output is presented below:
 
+{{% todo %}}Should we use an Mx 11 example here?{{% /todo %}}
+
 <details>
 
 <summary>Expand for code sample</summary>

content/en/docs/refguide/general/mx-command-line-tool/app.md

@@ -94,11 +94,7 @@ These are the return codes:
 
 ## mx show-java-version Command{#show-java-version}
 
-{{% alert color="info" %}}
-This command is available from 10.14 onwards and in MTS versions 10.6.12+ and 10.12.2+.
-{{% /alert %}}
-
-The `mx show-java-version` command reports what the configured Java version of the app is.
+{The `mx show-java-version` command reports what the configured Java version of the app is.
 
 The input is a single MPR file.
 

content/en/docs/refguide/general/mx-command-line-tool/merge.md

@@ -144,6 +144,8 @@ At the end of the file, add a `[merge "custom"]` block like this:
     driver = [MX.EXE_PATH] merge %O %A %B
 ```
 
+{{% todo %}}Should we put a Mx 11 example here?{{% /todo %}}
+
 Replace `[MX.EXE_PATH]` with a full path to your *mx.exe* file in the Unix format (for example, `'/c/Program Files/Mendix/10.0.0.8753/modeler/mx.exe'`).
 
 Under the `[core]` section, add the following:

content/en/docs/refguide/general/mx-command-line-tool/module.md

@@ -133,6 +133,8 @@ Exit code 111
 
 or
 
+{{% todo %}}Should we use an Mx 11 example here?{{% /todo %}}
+
 ```bash
 > mx.exe module-import Module.mpk App.mpr
 The mpr file version is '10.3.0-dev'.

content/en/docs/refguide/general/sbom-generation.md

@@ -31,6 +31,8 @@ The SBOM is based on the [CycloneDX 1.4 JSON format](https://cyclonedx.org/docs/
 
 Since a full SBOM contains all project details, this is only a partial representation of a full example. To simplify, below is one of the Java libraries that is packaged. The `dependencies` field will contain the dependency relationship from Mendix Marketplace Modules to npm modules and Java libraries.
 
+{{% todo %}}Should we put Mx 11 examples in this doc?{{% /todo %}}
+
 ```json
 
 {

content/en/docs/refguide/java-programming/managed-dependencies.md

@@ -9,8 +9,6 @@ description: "Describes how to use the managed dependencies feature in Studio Pr
 
 Mendix Studio Pro allows you to manage your Java dependencies. By specifying Java dependencies and their versions per module, Studio Pro can automatically download them and resolve conflicts by leveraging Gradle.
 
-In versions of Mendix below 10.3.0, Java dependencies were put into the `userlib` folder manually. This process has been simplified using managed dependencies, although the `userlib` folder can still be used for custom `.jar`s. For more information see [Unmanaged Dependencies](#unmanaged), below.
-
 ## Adding or Updating Managed Dependencies{#add-dependency}
 
 You can specify Java dependencies through the module settings of each module. For each module, you can configure your dependencies on the **Java Dependencies** tab of [Module settings](/refguide/module-settings/).

content/en/docs/refguide/mobile/getting-started-with-mobile/prerequisites.md

@@ -64,6 +64,8 @@ The Make It Native app allows developers to preview, test, and debug native mobi
 
 Depending on the Mendix version used to build your app, you have to use a different version of Make It Native. The following list explains which version to use:
 
+{{% todo %}}I don't think we need all these versions in the Mx 11 version of the refguide. But will there be a MIN 11 which should be used for Mx11?{{% /todo %}}
+
 * **Latest Mendix Version** - Latest version of Make It Native 10 ([Android](https://play.google.com/apps/testing/com.mendix.developerapp.mx10), [iOS](https://testflight.apple.com/join/bQfLf27w))
     * Please note that the latest version of Make It Native 10 is offered in online stores' beta version programs. Simply follow the instructions on those sites to download and install the latest version of MIN 10.
 * **10.18.x** – Make It Native 10 MTS ([Android](https://play.google.com/store/apps/details?id=com.mendix.developerapp.mx10), [iOS](https://apps.apple.com/app/make-it-native-10/id6450037464))

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md

@@ -55,10 +55,6 @@ The **Output** section shows what the action returns and allows you to rename it
 
 If the action returns an entity that has associations, you can select the associations that you want to have populated in the resulting variable. You can then use the **Retrieve** activity to retrieve the associated objects over the association. 
 
-{{% alert color="info" %}}
-Support for retrieving associations from external actions was introduced in Studio Pro [10.12.0](/releasenotes/studio-pro/10.12/).
-{{% /alert %}}
-
 ## Documentation Tab {#public-documentation}
 
 In the **Documentation** tab, you can find a **Summary** and a **Description**. These fields contain public documentation provided by the author of the service.
@@ -72,7 +68,3 @@ The **Edit External Action Parameter Mapping** dialog allows you to set the valu
 Every parameter must have a value specified. When **Can be empty** is true, the selected variable or expression may evaluate to `empty`. When the value cannot be empty, the microflow will throw an error if the value evaluates to `empty`.
 
 If you have selected a variable for an entity that has associations, you can select which associations you want to include in the arguments that you call the external action with.
-
-{{% alert color="info" %}}
-Support for including associations in parameters of external actions was introduced in Studio Pro [10.12.0](/releasenotes/studio-pro/10.12/).
-{{% /alert %}}

content/en/docs/refguide/modeling/integration/odata-services/consumed-odata-services/_index.md

@@ -43,10 +43,6 @@ You can create associations between local [persistable entities](/refguide/persi
 When a service defines an entity without an entity set, it means that this entity is not persistable. You can add it to the domain model as a non-persistable entity.
 The definition of this entity is read-only and is controlled in the service that publishes it. This means that you cannot add attributes or change them.
 
-{{% alert type="info" %}}
-Support for importing non-persistable entities from a consumed OData service was introduced in Studio Pro [10.8.0](/releasenotes/studio-pro/10.8/).
-{{% /alert %}}
-
 ### External Enumerations
 
 When you consume an external entity that has an attribute of an enumeration type, the corresponding enumeration will be added to your project if it did not previously exist. The enumeration is created according to the definition in the OData service contract, meaning that all allowed values will be automatically added to your enumeration.