Merge branch 'development' into document-call-depth-loop-count-limit-options

Author: MarkvanMents

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/multi-user-task.md

@@ -64,7 +64,7 @@ In case **Target users using** (an XPath or a microflow) results in an empty lis
 
 Specifies the expression used to assign the multi-user task. This option is displayed only when the [Target users using](#target-users) is set to **XPath**. Click **Edit** to edit the [XPath constraint](/refguide/xpath-constraints/).
 
-#### Microflow
+#### Microflow {#microflow-targeting}
 
 Specifies the microflow used to assign the multi-user task. This option is displayed only when the [Target users using](#target-users) is set to **Microflow**.
 

content/en/docs/refguide/modeling/integration/rest-services/published-rest-services/published-rest-service/published-rest-operation-parameter.md

@@ -22,6 +22,11 @@ Specify where the parameter comes from. Possible values are the following:
 * **Path** – The operation path can contain parameters as well. If you add a path parameter, make sure you also add it to the operation. For more information, see [Published REST Path Parameters](/refguide/published-rest-path-parameters/).
 * **Body** – The microflow can have 0 or 1 body parameters. A body parameter is taken from the body of the request. If the body is a file document or an image, the contents will be filled with the body of the request. If the body parameter is another type of object or a list, an [import mapping](/refguide/import-mappings/) is needed to convert the body content of the request into an object or a list. `GET`, `HEAD`, and `OPTIONS` operations should not have body parameters.
 * **Header** – The value of a header parameter is taken from the (first) request header with that name.
+
+{{% alert color="info" %}}
+Certain reserved keywords in **OpenAPI 3.0** cannot be used as header parameter names. For example, using `Authorization` as a custom header key can cause conflicts since it is already reserved by the specification. Using those reserved keywords only impacts OpenAPI v3 in the Swagger UI and not the actual API endpoints. For more details and alternative names, see [OpenAPI 3.0: Reserved header parameter names](https://swagger.io/docs/specification/v3_0/describing-parameters/#header-parameters).
+{{% /alert %}}
+
 * **Form** – The value of a form parameter is taken from the body part with that name (these are available for `multipart/form-data` requests).
 
 ### Name

content/en/docs/refguide/modeling/integration/rest-services/published-rest-services/published-rest-technical-details/open-api.md

@@ -51,6 +51,3 @@ Each operation generates an `Operation` object:
 | `responses` | The OK response. If security is enabled, this is also the unauthorized response. |
 | `deprecated` | Set to true when the operation is marked as deprecated. |
 
-## Limitations
-
-- Certain [reserved keywords](https://swagger.io/docs/specification/v3_0/describing-parameters/#header-parameters) in OpenAPI 3.0 cannot be used as header parameter names. For example, using `Authorization` as a custom header key can cause conflicts since it is already reserved by the specification.

content/en/docs/refguide/modeling/xpath/xpath-constraints/_index.md

@@ -182,10 +182,10 @@ This query retrieves all users that have the role Administrator:
 {{< tabpane >}}
   {{% tab header="Environments:" disabled=true /%}}
   {{< tab header="Studio Pro" lang="StudioPro" >}}
-    [id = '[%UserRole_Administrator%]']
+    [System.UserRoles/System.UserRole[id = '[%UserRole_Administrator%]']]
     {{% /tab %}}
   {{< tab header="Java" lang="JavaQuery" >}}
-     //Sales.User[id = '[%UserRole_Administrator%]']
+     //Sales.User[System.UserRoles/System.UserRole[id = '[%UserRole_Administrator%]']]
     {{% /tab %}}
 {{< /tabpane >}}
 

content/en/docs/refguide/runtime/tracing-in-runtime.md

@@ -54,3 +54,45 @@ The Java Agent can be configured through system properties, which can be added t
 | `otel.exporter.otlp.traces.client.certificate` | The path to the file containing trusted certificates to use when verifying a trace client's TLS credentials. The file should contain one or more X.509 certificates in PEM format. | By default no certificate file is used. |
 | `mendix.tracing.max.microflow.depth` | Specifies the maximum nesting level of microflow calls for which the system will generate tracing spans. | 10 |
 | `mendix.tracing.max.loop.iteration` | Defines the maximum number of loop iterations for which individual tracing spans will be generated within a single microflow loop. | 10 |
+
+## Enabling Tracing for Deployed Applications
+
+To enable tracing for your deployed Mendix application, configure the following JVM parameters:
+
+```
+-javaagent:mxinstallation/runtime/agents/opentelemetry-javaagent.jar
+-Dotel.javaagent.extensions=mxinstallation/runtime/agents/mendix-opentelemetry-agent-extension.jar
+-Dotel.service.name=MyServiceName
+```
+
+{{% alert color="info" %}}
+Replace `MyServiceName` with a meaningful identifier for your service.
+{{% /alert %}}
+
+### OpenTelemetry Collector on Different Host
+
+If the OpenTelemetry Collector is not running on the same host as your application, you must also specify the trace export endpoint:
+
+```
+-Dotel.exporter.otlp.traces.endpoint=http://collector-host:port
+```
+
+{{% alert color="info" %}}
+Replace `collector-host` and `port` with the host and port of your OpenTelemetry collector.
+{{% /alert %}}
+
+### Docker-Based Deployment
+
+For Docker deployments, you can set the JVM parameters using the `JAVA_TOOL_OPTIONS` environment variable. For example:
+
+```
+docker run MyMendixApp \
+  -e JAVA_TOOL_OPTIONS="-javaagent:mxinstallation/runtime/agents/opentelemetry-javaagent.jar \
+  -Dotel.javaagent.extensions=mxinstallation/runtime/agents/mendix-opentelemetry-agent-extension.jar \
+  -Dotel.service.name=MyServiceName \
+  -Dotel.exporter.otlp.traces.endpoint=http://collector-host:port"
+```
+
+{{% alert color="info" %}}
+Replace `MyServiceName` with a meaningful identifier for your service and `collector-host` and `port` with the host and port of your OpenTelemetry collector.
+{{% /alert %}}

content/en/docs/refguide10/modeling/integration/rest-services/published-rest-services/published-rest-service/published-rest-operation-parameter.md

@@ -22,6 +22,11 @@ Specify where the parameter comes from. Possible values are the following:
 * **Path** – The operation path can contain parameters as well. If you add a path parameter, make sure you also add it to the operation. For more information, see [Published REST Path Parameters](/refguide10/published-rest-path-parameters/).
 * **Body** – The microflow can have 0 or 1 body parameters. A body parameter is taken from the body of the request. If the body is a file document or an image, the contents will be filled with the body of the request. If the body parameter is another type of object or a list, an [import mapping](/refguide10/import-mappings/) is needed to convert the body content of the request into an object or a list. `GET`, `HEAD`, and `OPTIONS` operations should not have body parameters.
 * **Header** – The value of a header parameter is taken from the (first) request header with that name.
+
+{{% alert color="info" %}}
+Certain reserved keywords in **OpenAPI 3.0** cannot be used as header parameter names. For example, using `Authorization` as a custom header key can cause conflicts since it is already reserved by the specification. Using those reserved keywords only impacts OpenAPI v3 in the Swagger UI and not the actual API endpoints. For more details and alternative names, see [OpenAPI 3.0: Reserved header parameter names](https://swagger.io/docs/specification/v3_0/describing-parameters/#header-parameters).
+{{% /alert %}}
+
 * **Form** – The value of a form parameter is taken from the body part with that name (these are available for `multipart/form-data` requests).
 
 ### Name

content/en/docs/refguide10/modeling/integration/rest-services/published-rest-services/published-rest-technical-details/open-api.md

@@ -55,6 +55,3 @@ Each operation generates an `Operation` object:
 | `responses` | The OK response. If security is enabled, this is also the unauthorized response. |
 | `deprecated` | Set to true when the operation is marked as deprecated. |
 
-## Limitations
-
-- Certain [reserved keywords](https://swagger.io/docs/specification/v3_0/describing-parameters/#header-parameters) in OpenAPI 3.0 cannot be used as header parameter names. For example, using `Authorization` as a custom header key can cause conflicts since it is already reserved by the specification.

content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md

@@ -12,6 +12,16 @@ For information on the current status of deployment to Mendix on Kubernetes and
 
 ## 2025
 
+### September 16, 2025
+
+#### Mendix Operator v2.23.1 {#2.23.1}
+
+* We have updated storage provisioners that create Azure Workload identitites. This update helps ensure that errors like *Cannot validate Microsoft Entra ID user ... because the OID isn't found in the tenant* are detected and handled correctly.
+
+    After creating a new workload identity, it might take some time before the workload identity (user) becomes fully functional. This error is not an issue (just a temporary status) and in this situation the Mendix Operator can just retry after waiting for some time.
+
+  Because Microsoft Azure previously changed the error text, older Mendix Operator versions might not correct this error.
+
 ### September 4, 2025
 
 #### Portal Improvements

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

@@ -136,6 +136,7 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for
 * We fixed an issue where Studio Pro crashed when opening the **History** dialog if the metadata was corrupted
 * In the Dojo client, we fixed a pop-up window resizing issue that occurred upon interacting with a combobox widget inside the popup on mobile devices.
 * We fixed a conversion issue affecting sorting in the **Gallery** widget, specifically when upgrading the data widgets Marketplace module to version 3.0.0 or above.
+* We introduced a set of pre-commit checks to ensure generated content is up to date before committing. This prevents generated content from being updated without any user input after committing, which limited the user from completing other version control operations (like a **Pull** from the server).
 
 ### Known Issues
 

content/en/docs/releasenotes/studio-pro/11/11.1.md

@@ -124,6 +124,7 @@ weight: 99
 * In the Dojo client, we fixed pop-up windows resizing while interacting with a Combobox inside the pop-up window on mobile devices.
 * When upgrading to a data widgets module version 3.0.0 or above, we fixed conversion issues affecting both grid-wide filtering configurations (when filter widgets were wrapped in containers) and drop-down filter settings for associations on Data grid 2 columns during widget updates.
 * We fixed an error that appeared when trying to use the [Radio buttons](/refguide/radio-buttons/) widget.
+* We introduced a set of pre-commit checks to ensure generated content is up to date before committing. This prevents generated content from being updated without any user input after committing, which limited the user from completing other version control operations (like a **Pull** from the server).
 
 ### Breaking Changes