Merge remote-tracking branch 'upstream/development' into development

Author: github-actions[bot]

assets/scss/_styles_project.scss

@@ -464,6 +464,28 @@ img {
     }
   }
 
+    /* Olu - Position the mobile close button and remove extra top spacing so content aligns */
+    #td-sidebar-menu > .d-flex.d-md-none {
+        position: absolute;
+        top: 0.5rem;
+        right: 0.5rem;
+        z-index: 1060;
+    }
+
+    #td-sidebar-menu {
+        padding-top: 0;
+    }
+
+    #td-sidebar-menu .td-sidebar__search {
+        margin-top: 0; /* ensure search sits at top level */
+        padding-top: 0;
+    }
+
+    #td-sidebar-menu nav.td-sidebar-nav {
+        margin-top: 0;
+        padding-top: 0.25rem;
+    }
+
   // Responsive tables
   //
   // Generate series of `.table-responsive-*` classes for configuring the screen
@@ -607,4 +629,54 @@ img.ToC-icon{
     &:hover {
         background-color: $gray-light;
     };
+}
+
+// Olu - Mobile sidebar open/close behaviour (apply to small and medium screens)
+@include media-breakpoint-down(md) {
+    body.td-sidebar-open {
+        overflow: hidden;
+    }
+
+    .td-sidebar {
+        display: block !important;
+        position: fixed;
+        top: 0;
+        left: 0;
+        height: 100vh;
+        width: 80%;
+        max-width: 340px;
+        z-index: 1055;
+        background-color: $td-sidebar-bg-color;
+        transform: translateX(-100%);
+        transition: transform .25s ease-in-out;
+        box-shadow: 0 0 0.5rem rgba(0,0,0,0.2);
+    }
+
+    body.td-sidebar-open .td-sidebar {
+        transform: translateX(0);
+    }
+
+    .td-sidebar-overlay {
+        display: none;
+        position: fixed;
+        inset: 0;
+        z-index: 1050;
+        background: rgba(0,0,0,0.45);
+    }
+
+    body.td-sidebar-open .td-sidebar-overlay {
+        display: block;
+    }
+
+    /* adjustment for the close button in the sidebar */
+    #td-mobile-sidebar-close {
+        font-size: 1.1rem;
+    }
+
+    // Ensure the scrolling container inside the off-canvas sidebar fills more of the viewport
+    .td-sidebar__inner {
+        height: calc(100vh - 1.5rem) !important;
+        overflow-y: auto;
+        padding-top: 1.25rem;
+    }
 }

config/_default/hugo.toml

@@ -84,7 +84,7 @@ replacements = "github.com/FortAwesome/Font-Awesome -> ., github.com/twbs/bootst
 
 # Olu - Minification configuration
 [minify]
-    minifyOutput = true
+    minifyOutput = false
 
 # Everything below this are Site Params
 # ======================================

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/debug-microflows-and-nanoflows/_index.md

@@ -1,6 +1,6 @@
 ---
 title: "Debugging Microflows and Nanoflows"
-url: /refguide/debug-microflows-and-nanoflows//
+url: /refguide/debug-microflows-and-nanoflows/
 weight: 120
 ---
 
@@ -20,6 +20,10 @@ Before starting this how-to, make sure you have completed the following prerequi
 * Read [Configuring a Domain Model](/refguide/configuring-a-domain-model/)
 * Read [How to Create Your First Two Overview and Detail Pages](/howto/front-end/create-your-first-two-overview-and-detail-pages/)
 
+{{% alert color="info" %}}
+Debugging with breakpoints is not supported for microflows executed during application startup (for example, the [After startup](/refguide/runtime-tab/#after-startup) microflow and any microflows it calls).
+{{% /alert %}}
+
 ## Debugging Overview
 
 There are three debugging panes: **Breakpoints**, **Debugger**, and **Variables**:

content/en/docs/refguide/runtime/custom-settings/_index.md

@@ -7,7 +7,20 @@ description: "Describes how to setup and use tracing in the Mendix Runtime."
 ## Introduction
 
 Mendix supports tracing via OpenTelemetry. When tracing is enabled, the runtime generates traces that help you analyze errors and performance.
-These traces can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).
+
+Tracing provides a deep insight into applications' performance and stability by collecting and analyzing runtime data during operation. It offers these key benefits:
+
+* End‑to‑end request visibility – tracing can follow a single request across all involved services.
+* Clear causality and root‑cause analysis – traces show exactly where an issue occurred and how it propagated.
+* Precise latency attribution – tracing pinpoints which operation or dependency affected response times the most.
+* Correlation across telemetry signals – traces can be correlated with logs and metrics for holistic performance and error analysis.
+* Vendor‑neutral, future‑proof instrumentation – OpenTelemetry is an open industry standard and best practice.
+
+Tracing is an important tool for maintaining critical applications, ensuring application performance, and troubleshooting issues with applications in production.
+
+## Prerequisites
+
+To view these traces, you will need an observability tool such as [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).
 
 {{% alert color="warning" %}}
 Tracing is currently supported only via [Datadog integration](/developerportal/operate/datadog-metrics/) on Mendix Cloud.

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

@@ -1,6 +1,6 @@
 ---
 title: "Debugging Microflows and Nanoflows"
-url: /refguide10/debug-microflows-and-nanoflows//
+url: /refguide10/debug-microflows-and-nanoflows/
 weight: 120
 ---
 
@@ -20,6 +20,10 @@ Before starting this how-to, make sure you have completed the following prerequi
 * Read [Configuring a Domain Model](/refguide10/configuring-a-domain-model/)
 * Read [How to Create Your First Two Overview and Detail Pages](/howto10/front-end/create-your-first-two-overview-and-detail-pages/)
 
+{{% alert color="info" %}}
+Debugging with breakpoints is not supported for microflows executed during application startup (for example, the [After startup](/refguide10/app-settings/#after-startup) microflow and any microflows it calls).
+{{% /alert %}}
+
 ## Debugging Overview
 
 There are three debugging panes: **Breakpoints**, **Debugger**, and **Variables**:

content/en/docs/refguide10/modeling/application-logic/microflows-and-nanoflows/debug-microflows-and-nanoflows/_index.md

@@ -296,21 +296,44 @@ The settings below configure metrics through [micrometer](https://micrometer.io/
 
 ## Proxy Settings {#proxy-settings}
 
-The settings below allow you to use a proxy. 
+### Http(s) Connections
 
-{{% alert color="warning" %}}
-These settings have to be set as JVM properties, not as custom Runtime settings.
-{{% /alert %}}
+The settings below configure the app to use a proxy for all connections, whether they are using the HTTP or HTTPS protocol. They are used in the following circumstances:
+
+  1. In the integration microflow activities [call web service](/refguide10/call-web-service-action/), [call REST service](/refguide10/call-rest-action/), [send REST request](/refguide10/send-rest-request/), and  [call external action](/refguide10/call-external-action/).
+  2. In the external object microflow activities [send external object](/refguide10/send-external-object/) and [delete external object](/refguide10/delete-external-object/).
+  3. When retrieving an external entity data using a [consumed OData service](/refguide10/consumed-odata-service/).
+  4. When calling the Mendix runtime API [Core.Http().executeHttpRequest](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/http/Http.html) and [HttpConfiguration.getInstance().getProxyConfiguration()](https://apidocs.rnd.mendix.com/10/runtime/com/mendix/http/IHttpConfiguration.html).
+
+These settings can be set either as JVM properties or as custom Runtime settings. When both the JVM property and custom runtime setting are set, the app uses the custom runtime setting.
 
 | Name | Description | Default Value |
 | --- | --- | --- |
 | <a id="httpproxyHost" href="#httpproxyHost">http.proxyHost</a> | Defines the hostname of the HTTP proxy server. | |
 | <a id="httpproxyPort" href="#httpproxyPort">http.proxyPort</a> | Defines the port number of the HTTP proxy server. | |
 | <a id="httpproxyUser" href="#httpproxyUser">http.proxyUser</a> | Defines the user of the HTTP proxy server. | | 
 | <a id="httpproxyPassword" href="#httpproxyPassword">http.proxyPassword</a> | Defines the password of the HTTP proxy server. | | 
+
+{{% alert color="info" %}}
+The `http.` part of the names of these settings does not imply anything about whether the `HTTP` or `HTTPS` protocol is used - it is just the name of the setting.
+{{% /alert %}}
+
+### License Server
+
+The settings below configure the app to use a proxy to reach the Mendix license server.
+
+{{% alert color="info" %}}
+These settings have to be set as JVM properties, not as custom runtime settings.
+{{% /alert %}}
+
+| Name | Description | Default Value |
+| --- | --- | --- |
 | <a id="httpsproxyHost" href="#httpsproxyHost">https.proxyHost</a> | Defines the hostname of the HTTPS proxy server. | |
 | <a id="httpsproxyPort" href="#httpsproxyPort">https.proxyPort</a> | Defines the port number of the HTTPS proxy server. | |
 | <a id="httpsproxyUser" href="#httpsproxyUser">https.proxyUser</a> | Defines the user of the HTTPS proxy server. | | 
 | <a id="httpsproxyPassword" href="#httpsproxyPassword">https.proxyPassword</a> | Defines the password of the HTTPS proxy server. | | 
+| <a id="httpsnonProxyHosts" href="#httpsnonProxyHosts">https.nonProxyHosts</a> | Defines a list of hosts that should be reached directly, bypassing the proxy. This is a list of patterns separated by '&#x007C;'. The patterns may start or end with a '*' for wildcards. | | 
 
-{{% alert color="info" %}} `http.nonProxyHosts` only affects the license server. {{% /alert %}}
+{{% alert color="info" %}}
+The `https.` part of the names of these settings does not imply anything about whether the `HTTP` or `HTTPS` protocol is used - it is just the name of the setting.
+{{% /alert %}}

content/en/docs/refguide10/runtime/custom-settings/_index.md

@@ -1,6 +1,6 @@
 ---
 title: "Debugging Microflows and Nanoflows"
-url: /refguide9/debug-microflows-and-nanoflows//
+url: /refguide9/debug-microflows-and-nanoflows/
 weight: 120
 ---
 
@@ -20,6 +20,10 @@ Before starting this how-to, make sure you have completed the following prerequi
 * Read [Creating a Basic Data Layer](/refguide9/create-a-basic-data-layer/)
 * Read [How to Create Your First Two Overview and Detail Pages](/howto9/front-end/create-your-first-two-overview-and-detail-pages/)
 
+{{% alert color="info" %}}
+Debugging with breakpoints is not supported for microflows executed during application startup (for example, the [After startup](/refguide9/app-settings/#after-startup) microflow and any microflows it calls).
+{{% /alert %}}
+
 ## Debugging Overview
 
 There are three debugging panes: **Breakpoints**, **Debugger**, and **Variables**: