Merge branch 'development' into appext/1415-update-progress-dialog-behavior

quinntracy · web-flow · commit caabecf0d7b7 · 2026-07-17T14:28:44.000+02:00
diff --git a/content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md b/content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md
@@ -19,6 +19,10 @@ Apps running in Mendix Cloud are subject to certain limitations. These behaviors
 * You cannot upload files bigger than 1 GB to your app.
 * You cannot download files bigger than 1 GB from your app.
 
+## Constants Size Limit
+
+* Due to Linux limitations, the combined length of all constant keys and values cannot exceed 128 KB (approximately 32,000 characters). This limit cannot be changed.
+
 ## Considerations for Multi-Instance Nodes
 
 * To use the debugger, you need to scale down to one instance.
diff --git a/content/en/docs/deployment/mendix-cloud-deploy/environments-details.md b/content/en/docs/deployment/mendix-cloud-deploy/environments-details.md
@@ -180,6 +180,10 @@ On this tab, you can edit the model options for constants and scheduled events.
 
 In this section, you can view the configured constants. Constants are used to define configuration values that can differ per environment.
 
+{{% alert color="warning" %}}
+The combined length of all constant keys and values is limited to 128 KB (approximately 32,000 characters). For more information, refer to [Behavior of Your App in Mendix Cloud](/developerportal/deploy/behavior-of-app/#constants-size-limit).
+{{% /alert %}}
+
 To fill in a new value, select the constant and click **Edit** to bring up the **Edit Constant** dialog box.
 
 {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/edit-constant.png" >}}
diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/datadog-metrics.md b/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/datadog-metrics.md
@@ -208,7 +208,7 @@ If the app has more than one instance, you will see lines on the graph for each
 
 ## Mendix Tracing{#mendix-tracing}
 
-[Mendix Tracing](/refguide/tracing-in-runtime/) sends Mendix Runtime traces to [Datadog APM](https://docs.datadoghq.com/tracing/), giving you distributed tracing visibility into your app's performance and microflow executions.
+Mendix uses [OpenTelemetry](/refguide/opentelemetry-in-runtime/) to send Mendix Runtime traces to [Datadog APM](https://docs.datadoghq.com/tracing/), giving you an insight into your app's microflow executions and performance.
 
 {{% alert color="info" %}}
 Mendix Tracing requires Mendix Runtime 10.24.12 or above, or 11.5 or above.
@@ -232,7 +232,7 @@ To enable Mendix Tracing, follow these steps:
 
 ### Filtering Traces{#filter-traces}
 
-To control which traces are sent to Datadog, set the `MX_TRACING_FILTER` custom environment variable. For available filter options and syntax, see [Tracing in Runtime](/refguide/tracing-in-runtime/#filtering).
+To control which traces are sent to Datadog, set the `MX_TRACING_FILTER` custom environment variable. For available filter options and syntax, see [OpenTelemetry](/refguide/opentelemetry-in-runtime/#filtering).
 
 ## Additional Information{#additional-info}
 
@@ -305,7 +305,7 @@ Previously, when Mendix Cloud ran on Cloud Foundry, hosts were incorrectly regis
 
 * [Monitor Your Mendix Apps with Datadog](https://www.mendix.com/blog/monitor-your-mendix-apps-with-datadog/) – a Mendix blog about the capabilities of Datadog and using Datadog with Mendix
 * [Metrics](/developerportal/operate/metrics/)
-* [Tracing in Runtime](/refguide/tracing-in-runtime/) – Mendix documentation
+* [OpenTelemetry](/refguide/opentelemetry-in-runtime/) – Mendix documentation
 * [Java Runtime Metrics](https://docs.datadoghq.com/tracing/runtime_metrics/java/) – Datadog documentation
 * [Postgres](https://docs.datadoghq.com/integrations/postgres/) – Datadog documentation
 * [System Check](https://docs.datadoghq.com/integrations/system/) – Datadog documentation
diff --git a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/configurations-tab.md b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/configurations-tab.md
@@ -33,7 +33,7 @@ A configuration contains the following:
 * [Constants](#constants)
 * [Custom](#custom)
 * [Headers](#headers)
-* [OpenTelemetry](/refguide/tracing-in-runtime/#min-configuration)
+* [OpenTelemetry](/refguide/opentelemetry-in-runtime/#min-configuration)
 
 ### Database {#database}
 
diff --git a/content/en/docs/refguide/runtime/monitoring-mendix-runtime.md b/content/en/docs/refguide/runtime/monitoring-mendix-runtime.md
@@ -674,7 +674,7 @@ This will write logs to standard output in simple text format.
 }
 ```
 
-This will send logs to the registered OpenTelemetry collector. See [Tracing](/refguide/tracing-in-runtime/) for a guide on how to enable OpenTelemetry.
+This will send logs to the registered OpenTelemetry collector. See [OpenTelemetry](/refguide/opentelemetry-in-runtime/) for a guide on how to enable OpenTelemetry.
 
 ## Set Log Levels{#log-levels}
 
diff --git a/content/en/docs/refguide/runtime/tracing-in-runtime.md b/content/en/docs/refguide/runtime/tracing-in-runtime.md
@@ -1,7 +1,9 @@
 ---
-title: "Tracing"
-url: /refguide/tracing-in-runtime/
-description: "Describes how to setup and use tracing in the Mendix Runtime."
+title: "OpenTelemetry"
+url: /refguide/opentelemetry-in-runtime/
+description: "Describes how to setup and use OpenTelemetry in the Mendix Runtime."
+aliases:
+   - /refguide/tracing-in-runtime/
 ---
 
 ## Introduction
diff --git a/content/en/docs/refguide/testing/_index.md b/content/en/docs/refguide/testing/_index.md
@@ -80,4 +80,4 @@ Performance testing involves unit-level performance checks for critical microflo
 
 You can use the following offerings to help with this test type:
 
-* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).
+* [OpenTelemetry](/refguide/opentelemetry-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).
diff --git a/content/en/docs/refguide10/testing/_index.md b/content/en/docs/refguide10/testing/_index.md
@@ -80,4 +80,4 @@ Performance testing involves unit-level performance checks for critical microflo
 
 You can use the following offerings to help with this test type:
 
-* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).
+* [Tracing](/refguide10/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).
diff --git a/content/en/docs/releasenotes/studio-pro/10/10.24.md b/content/en/docs/releasenotes/studio-pro/10/10.24.md
@@ -427,7 +427,7 @@ We fixed an issue where long-running after-startup microflows caused other nodes
 
 ### Improvements
 
-* We implemented a feature that allows filtering out spans by their name. For more information, see the [Testing](/refguide/tracing-in-runtime/#testing) section of *Tracing*. 
+* We implemented a feature that allows filtering out spans by their name. For more information, see the [Testing](/refguide10/tracing-in-runtime/#testing) section of *Tracing*. 
 * The logout API in the new client `mx-api` now supports an optional params object with `reloadOnSuccess` flag. By default, `mx-api/logout` automatically reloads the page after a successful logout if you call it with no params object. If you pass a params object `{reloadOnSuccess: false}`, the automatic reload is disabled so you can implement your own custom logout flow and trigger reload yourself when needed.
 * We now log a warning when runtime operation parameters are missing during a database retrieval with an XPath constraint.
     This can happen, for example, when a nanoflow retrieve activity uses an XPath constraint that references an associated object that is not yet available in the nanoflow scope. In such cases, that would lead to unresolvable XPath. (Ticket 260339)
diff --git a/content/en/docs/releasenotes/studio-pro/11/11.0.md b/content/en/docs/releasenotes/studio-pro/11/11.0.md
@@ -66,9 +66,9 @@ For details on upgrading to Studio Pro 11, see [Upgrading from Mendix Studio Pro
 * We added support for Brazilian Portuguese to Studio Pro.
 * We improved the messages that Studio Pro shows when running an OQL query in view entities. There are now clearer messages when the app has not fully started yet and when the query refers to `[%CurrentUser%]` without specifying the user.
 * We relaxed the restriction that entities with an online synchronization mode could not refer to entities with an offline synchronization mode. It now only prevents XPath constraints in pages and nanoflows that mix entities with online and offline synchronization modes allowing more modeling possibilities.
-* When [tracing](/refguide/tracing-in-runtime/) is enabled, traces now include spans for all Microflow activities.
+* When [tracing](/refguide/opentelemetry-in-runtime/) is enabled, traces now include spans for all Microflow activities.
 * We bundled OpenTelemetry agent jar with Studio Pro. It can be found under `runtime/agents/opentelemetry-javaagent.jar`.
-* We provided the **Enable Tracing** option to enable runtime tracing in Studio Pro. It can be accessed through **App Settings**. For more information, see the [Minimal Configuration](/refguide/tracing-in-runtime/#min-configuration) section in *Tracing*.
+* We provided the **Enable Tracing** option to enable runtime tracing in Studio Pro. It can be accessed through **App Settings**. For more information, see the [Minimal Configuration](/refguide/opentelemetry-in-runtime/#min-configuration) section in *Tracing*.
 * We no longer close the response writer of custom request handlers, if an asynchronous request is started. With this change it is possible to implement asynchronous request handlers.
 * We implemented an OpenTelemetry agent extension that provides default settings. It can be found under `runtime/agents/mendix-opentelemetry-agent-extension.jar`.
 * We now add consistency warnings if there are multiple versions of the same Java dependency in your app.
diff --git a/content/en/docs/releasenotes/studio-pro/11/11.12.md b/content/en/docs/releasenotes/studio-pro/11/11.12.md
@@ -45,8 +45,11 @@ weight: 88
 - We fixed an issue in the modernized App Explorer where too many nodes could be selected at once.
 - We fixed an issue when calling `mx.ui.openForm` in the Dojo client.
 - We fixed an issue so that now, missing *progress message* on a blocking progress bar no longer causes a crash during deployment.
-- We fixed an issue where **Settings** were not be correctly loaded when upgrading a app to 11.12.
+- We fixed an issue where **Settings** were not correctly loaded when upgrading an app to 11.12.0.
 - We fixed an issue where the MCP Server settings intermittently caused an Oops dialog to appear.
+- We removed timeouts for Custom Blob Document consistency checks instead of showing a generic error in the **Errors** pane. We also added analytics to identify extensions that exceed the previous timeout.
+- We fixed a bug where the icon next to a tab title did not appear.
+- We fixed a bug where the Module Settings form incorrectly showed modules other than Add-on when packaging an extension into a module.
 
 ### Deprecations
     
diff --git a/content/en/docs/releasenotes/studio-pro/11/11.5.md b/content/en/docs/releasenotes/studio-pro/11/11.5.md
@@ -42,7 +42,7 @@ weight: 95
 * When an OQL UPDATE statement has a SET expression that returns multiple rows, Studio Pro now throw a `CardinalityViolationException` instead of a generic `ConnectionBusException`.
 * We improved the way Studio Pro updates attributes and associations based on the OQL query of a view entity. It now renames existing attributes and associations when the expression is the same but the alias is different.
 * We improved the Send REST Request activity in Studio Pro. It now indicates whether parameters are required or not.
-* We implemented a new [Tracing](/refguide/tracing-in-runtime/#testing) feature that allows filtering out spans by their name. 
+* We implemented a new [Tracing](/refguide/opentelemetry-in-runtime/#testing) feature that allows filtering out spans by their name. 
 * We have improved the UX of the managed dependencies and **userlib** *.JAR* exclusions dialogs. Now checking the rows will exclude the JAR files instead of including them.
 * The logout API in the new client `mx-api` now supports an optional params object with `reloadOnSuccess` flag. By default, `mx-api/logout` automatically reloads the page after a successful logout if you call it with no params object. If you pass a params object `{reloadOnSuccess: false}`, the automatic reload is disabled so you can implement your own custom logout flow and trigger reload yourself when needed.
 * Mendix 11 introduces a change in the versioning schema by dropping the fourth element, known as the build number. Versions will now follow a SemVer pattern (`major.minor.patch`) with the occasional pre-release suffix (for example, `beta.1` for planned pre-releases). This semantic version will also be the version that is returned by `Core.getRuntimeVersion()`. Apps built with a pre-release can be identified internally by their exact version.
diff --git a/content/en/docs/releasenotes/studio-pro/web-extensibility-api.md b/content/en/docs/releasenotes/studio-pro/web-extensibility-api.md
@@ -13,6 +13,11 @@ These release notes cover changes to the [Extensibility API for Web Developers](
 * We fixed a bug where the Extensions Overview Page would not open if the user was not signed in.
 * We fixed a bug where reloading a Dev extension would cause a crash if tabs previously opened via an extension were not closed before the reload.
 * We fixed an issue where the progress dialogs did not behave as the C# counterpart, where cancelling a step still waited for it to finish and return its result. If the user still wants to exit the step and return the result immediately, they can still do so by passing `resolveImmediatelyOnCancel` to the `IDialogApi.showProgressDialog` method.
+## Version 11.12.1
+
+* We removed timeouts for Custom Blob Document consistency checks instead of showing a generic error in the **Errors** pane. We also added analytics to identify extensions that exceed the previous timeout.
+* We fixed a bug where the icon next to a tab title did not appear.
+* We fixed a bug where the Module Settings form incorrectly showed modules other than Add-on when packaging an extension into a module.
 
 ## Version 11.12.0
 

Original file line number	Diff line number	Diff line change
`@@ -674,7 +674,7 @@ This will write logs to standard output in simple text format.`
`674`	`674`	`}`
`675`	`675`	```
`676`	`676`
`677`		`-This will send logs to the registered OpenTelemetry collector. See [Tracing](/refguide/tracing-in-runtime/) for a guide on how to enable OpenTelemetry.`
	`677`	`+This will send logs to the registered OpenTelemetry collector. See [OpenTelemetry](/refguide/opentelemetry-in-runtime/) for a guide on how to enable OpenTelemetry.`
`678`	`678`
`679`	`679`	`## Set Log Levels{#log-levels}`
`680`	`680`
Original file line number	Diff line number	Diff line change
`@@ -80,4 +80,4 @@ Performance testing involves unit-level performance checks for critical microflo`
`80`	`80`
`81`	`81`	`You can use the following offerings to help with this test type:`
`82`	`82`
`83`		`-* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).`
	`83`	`+* [OpenTelemetry](/refguide/opentelemetry-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).`