Correct links to incorrect versions of API definitions

MarkvanMents · MarkvanMents · commit 545ea9d5fc5f · 2025-07-25T12:24:04.000+02:00
diff --git a/content/en/docs/refguide/modeling/integration/odata-services/consumed-odata-services/consumed-odata-service.md b/content/en/docs/refguide/modeling/integration/odata-services/consumed-odata-services/consumed-odata-service.md
@@ -115,7 +115,7 @@ The microflow should have an argument of type `System.HttpResponse`. If the ODat
 
 The microflow must return a `String` containing the error message. If it returns `empty`, the original generic message is used.
 
-Note for developers of Java actions: the message returned by the error handling microflow can be caught as a [UserException](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/systemwideinterfaces/core/UserException.html).
+Note for developers of Java actions: the message returned by the error handling microflow can be caught as a [UserException](https://apidocs.rnd.mendix.com/11/runtime/com/mendix/systemwideinterfaces/core/UserException.html).
 
 ### Metadata
 
diff --git a/content/en/docs/refguide/modeling/resources/task-queue.md b/content/en/docs/refguide/modeling/resources/task-queue.md
@@ -87,7 +87,7 @@ Core.microflowCall("AModule.SomeMicroflow")
   .executeInBackground(context, "AModule.SomeQueueName");
 ```
 
-The method `executeInBackground` takes two parameters: a context and a queue name. The context is only used for creating the task; the task will run with a [new, but equivalent context](#context). See the [API documentation](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/core/Core.html#microflowCall(java.lang.String)) for more information.
+The method `executeInBackground` takes two parameters: a context and a queue name. The context is only used for creating the task; the task will run with a [new, but equivalent context](#context). See the [API documentation](https://apidocs.rnd.mendix.com/11/runtime/com/mendix/core/Core.html#microflowCall(java.lang.String)) for more information.
 
 ### Queueing Java Actions
 
@@ -109,7 +109,7 @@ Core.userActionCall("AModule.SomeJavaAction")
   .executeInBackground(context, "AModule.SomeQueueName");
 ```
 
-The method `executeInBackground` takes two parameters: a context and a queue name. The context is only used for creating the task; the task will be run with a [new, but equivalent context](#context). See the [API documentation](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/core/Core.html#userActionCall(java.lang.String)) for more information.
+The method `executeInBackground` takes two parameters: a context and a queue name. The context is only used for creating the task; the task will be run with a [new, but equivalent context](#context). See the [API documentation](https://apidocs.rnd.mendix.com/11/runtime/com/mendix/core/Core.html#userActionCall(java.lang.String)) for more information.
 
 ### Task scheduling {#scheduling}
 
@@ -189,7 +189,7 @@ In case where **Apply entity access** is set to *true*, the following rules appl
 
 There is one exception to the above rules:
 
-* When a system context is used to schedule the task using the [Mendix Runtime Java API](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/core/actionmanagement/ActionCallBuilder.html#executeInBackground(com.mendix.systemwideinterfaces.core.IContext,java.lang.String)), the task will be run in a new system context, regardless of the **Apply entity access** setting.
+* When a system context is used to schedule the task using the [Mendix Runtime Java API](https://apidocs.rnd.mendix.com/11/runtime/com/mendix/core/actionmanagement/ActionCallBuilder.html#executeInBackground(com.mendix.systemwideinterfaces.core.IContext,java.lang.String)), the task will be run in a new system context, regardless of the **Apply entity access** setting.
 
 ### Task Status
 
diff --git a/content/en/docs/refguide/modeling/xpath/xpath-constraints/_index.md b/content/en/docs/refguide/modeling/xpath/xpath-constraints/_index.md
@@ -93,7 +93,7 @@ You can type your constraint by selecting the option **XPath expression**.
 
 To apply XPath constraints in Java, you should use a complete XPath expression as described in [XPath](/refguide/xpath/). This includes the entity context plus your constraint expression and (optionally) an aggregate function and attribute to retrieve.
 
-The XPath should be used in a [core.createXPathQuery](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/core/Core.html#createXPathQuery(java.lang.String)) call. You can then call [XPathQueryBase.execute](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/datastorage/XPathQueryBase.html#execute(com.mendix.systemwideinterfaces.core.IContext)) which will return the list of objects filtered using the XPath you provided.
+The XPath should be used in a [core.createXPathQuery](https://apidocs.rnd.mendix.com/11/runtime/com/mendix/core/Core.html#createXPathQuery(java.lang.String)) call. You can then call [XPathQueryBase.execute](https://apidocs.rnd.mendix.com/11/runtime/com/mendix/datastorage/XPathQueryBase.html#execute(com.mendix.systemwideinterfaces.core.IContext)) which will return the list of objects filtered using the XPath you provided.
 
 For example, to retrieve all customers named Jansen:
 
diff --git a/content/en/docs/refguide/runtime/mendix-client/_index.md b/content/en/docs/refguide/runtime/mendix-client/_index.md
@@ -271,7 +271,7 @@ When the Mendix client is running, it sets a number of technical cookies to reco
 | **XASSESSIONID**² | Runtime | Holds the ID of the user's session | `/` | 1 year for offline sessions¹, otherwise based on the session timeout |  `true` | 
 | **useAuthToken** | Runtime | Lets the runtime know whether to generate an authtoken or not | `/` | until the end-user closes their browser (session cookie) |  `true` | 
 | **authtoken** | Runtime | Used to hold the authentication token | `/` | until the authentication token expires |  `true` | 
-| **clear_cache** | Runtime | Instructs the client to clear the cached session data whenever a new end-user signs in to an offline application. If the client is not directly used for the sign-in functionality, you can use the newly added Java API, [addSessionCookies](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/m2ee/api/IMxRuntimeResponse.html#addSessionCookies), which sets all necessary cookies related to the session. | `/` | until client starts or end-user closes their browser | `false`³ | 
+| **clear_cache** | Runtime | Instructs the client to clear the cached session data whenever a new end-user signs in to an offline application. If the client is not directly used for the sign-in functionality, you can use the newly added Java API, [addSessionCookies](https://apidocs.rnd.mendix.com/11/runtime/com/mendix/m2ee/api/IMxRuntimeResponse.html#addSessionCookies), which sets all necessary cookies related to the session. | `/` | until client starts or end-user closes their browser | `false`³ | 
 
 ¹*Offline sessions* are sessions created for users using an offline or native mobile [navigation profile](/refguide/navigation/#profiles).
 
diff --git a/content/en/docs/refguide/runtime/mendix-client/react.md b/content/en/docs/refguide/runtime/mendix-client/react.md
@@ -69,7 +69,7 @@ JavaScript actions must not use any of the following client APIs:
 
 These APIs are related to Dojo and are no longer needed. For opening pages, please use the nanoflow [Show Page](/refguide/show-page/) action instead.
 
-Fore more information on React and APIs in Mendix, see our [Mendix 10 React Client API](https://apidocs.rnd.mendix.com/10/client-react/index.html) documentation.
+Fore more information on React and APIs in Mendix, see our [Mendix 11 React Client API](https://apidocs.rnd.mendix.com/11/client-react/index.html) documentation.
 
 ### Enable React Client{#enable-react}
 
diff --git a/content/en/docs/refguide/runtime/metrics.md b/content/en/docs/refguide/runtime/metrics.md
@@ -413,7 +413,7 @@ It is recommended to use a common prefix that uniquely defines your organization
 
 The following deprecated usages will be removed in the future releases,
 
-1. The [`Core.metrics()` Mendix Runtime Java API methods](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/metrics/Metrics.html) `counter()`, `timer()`, `gauges()`, and `sets()`, and the corresponding `Counters`, `Timers`, `Gauges` and `Sets` interfaces are deprecated.
+1. The [`Core.metrics()` Mendix Runtime Java API methods](https://apidocs.rnd.mendix.com/11/runtime/com/mendix/metrics/Metrics.html) `counter()`, `timer()`, `gauges()`, and `sets()`, and the corresponding `Counters`, `Timers`, `Gauges` and `Sets` interfaces are deprecated.
 
 ## Logging {#logging}
 
diff --git a/content/en/docs/refguide8/modeling/domain-model/entities/_index.md b/content/en/docs/refguide8/modeling/domain-model/entities/_index.md
@@ -142,7 +142,7 @@ We do not support displaying this system member of the System.User entity or its
 {{% /alert %}}
 
 {{% alert color="warning" %}}
-The `changedDate` value is not updated if you update the object directly in Java using calls which resolve to use the [`com.mendix.systemwideinterfaces.core.IMendixObject.setValue​(IContext context, java.lang.String memberName, java.lang.Object value)`](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/systemwideinterfaces/core/IMendixObject.html#setValue(com.mendix.systemwideinterfaces.core.IContext,java.lang.String,java.lang.Object)) method (for example, `Entity.setValue(IContext, String)`). If you need `changedDate` to be updated when using Java, use the [`com.mendix.core.Core.change​(IContext context, IMendixObject object, java.util.Map<java.lang.String,​java.lang.String> changes)`](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/core/Core.html#change(com.mendix.systemwideinterfaces.core.IContext,com.mendix.systemwideinterfaces.core.IMendixObject,java.util.Map)) method.
+The `changedDate` value is not updated if you update the object directly in Java using calls which resolve to use the [`com.mendix.systemwideinterfaces.core.IMendixObject.setValue​(IContext context, java.lang.String memberName, java.lang.Object value)`](https://apidocs.rnd.mendix.com/8/runtime/com/mendix/systemwideinterfaces/core/IMendixObject.html#setValue(com.mendix.systemwideinterfaces.core.IContext,java.lang.String,java.lang.Object)) method (for example, `Entity.setValue(IContext, String)`). If you need `changedDate` to be updated when using Java, use the [`com.mendix.core.Core.change​(IContext context, IMendixObject object, java.util.Map<java.lang.String,​java.lang.String> changes)`](https://apidocs.rnd.mendix.com/8/runtime/com/mendix/core/Core.html#change(com.mendix.systemwideinterfaces.core.IContext,com.mendix.systemwideinterfaces.core.IMendixObject,java.util.Map)) method.
 {{% /alert %}}
 
 #### Store 'owner' 
diff --git a/content/en/docs/refguide9/modeling/domain-model/entities/_index.md b/content/en/docs/refguide9/modeling/domain-model/entities/_index.md
@@ -156,7 +156,7 @@ We do not support displaying this system member of the System.User entity or its
 {{% /alert %}}
 
 {{% alert color="warning" %}}
-The `changedDate` value is not updated if you update the object directly in Java using calls which resolve to use the [`com.mendix.systemwideinterfaces.core.IMendixObject.setValue​(IContext context, java.lang.String memberName, java.lang.Object value)`](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/systemwideinterfaces/core/IMendixObject.html#setValue(com.mendix.systemwideinterfaces.core.IContext,java.lang.String,java.lang.Object)) method (for example, `Entity.setValue(IContext, String)`). If you need `changedDate` to be updated when using Java, use the [`com.mendix.core.Core.change​(IContext context, IMendixObject object, java.util.Map<java.lang.String,​java.lang.String> changes)`](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/core/Core.html#change(com.mendix.systemwideinterfaces.core.IContext,com.mendix.systemwideinterfaces.core.IMendixObject,java.util.Map)) method.
+The `changedDate` value is not updated if you update the object directly in Java using calls which resolve to use the [`com.mendix.systemwideinterfaces.core.IMendixObject.setValue​(IContext context, java.lang.String memberName, java.lang.Object value)`](https://apidocs.rnd.mendix.com/9/runtime/com/mendix/systemwideinterfaces/core/IMendixObject.html#setValue(com.mendix.systemwideinterfaces.core.IContext,java.lang.String,java.lang.Object)) method (for example, `Entity.setValue(IContext, String)`). If you need `changedDate` to be updated when using Java, use the [`com.mendix.core.Core.change​(IContext context, IMendixObject object, java.util.Map<java.lang.String,​java.lang.String> changes)`](https://apidocs.rnd.mendix.com/9/runtime/com/mendix/core/Core.html#change(com.mendix.systemwideinterfaces.core.IContext,com.mendix.systemwideinterfaces.core.IMendixObject,java.util.Map)) method.
 {{% /alert %}}
 
 #### Store 'owner' {#store-owner}
