Merge branch 'development' into kk-azure-blob

Author: katarzyna-koltun-mx

.github/workflows/lint-action.yml

@@ -54,8 +54,8 @@ jobs:
             ${{ env.VER }}
           branch: lint-docs
           committer: MarkvanMents <[email protected]>
-          assignees: MarkvanMents
-          reviewers: MarkvanMents
+          assignees: MarkvanMents,OlufunkeMoronfolu
+          reviewers: MarkvanMents,OlufunkeMoronfolu
           labels: Internal WIP
           add-paths: |
             content/en/docs/**/*.md

.github/workflows/remunusedattachments.yml

@@ -37,8 +37,8 @@ jobs:
             Check the htmltest output from the CI/CD pipeline to ensure that nothing has been removed accidentally.
           branch: rem-unused-attachments
           committer: MarkvanMents <[email protected]>
-          assignees: MarkvanMents
-          reviewers: MarkvanMents
+          assignees: MarkvanMents,OlufunkeMoronfolu
+          reviewers: MarkvanMents,OlufunkeMoronfolu
           labels: Internal WIP
           add-paths: |
             static/attachments/**

config/_default/hugo.toml

@@ -47,6 +47,10 @@ disableKinds = ["taxonomy", "term"]
     [markup.goldmark]
         [markup.goldmark.renderer]
             unsafe = true
+        [markup.goldmark.extensions.typographer]
+            # Disable typographic replacements, such as smart quotes. MvM - Changed to disable=true to avoid issues with quotes being mismatched.
+            # See https://gohugo.io/configuration/markup/
+            disable = true
     [markup.highlight]
         # See a complete list of available styles at https://xyproto.github.io/splash/docs/all.html
         # See config options at https://gohugo.io/getting-started/configuration-markup/#highlight

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/get-started.md

@@ -16,7 +16,6 @@ For more information, see the [Mendix Studio Pro Web Extensibility API](http://a
 You will need the following prerequisites:
 
 * Mendix Studio Pro version 10.21.0 or higher [Mendix Studio Pro](https://marketplace.mendix.com/link/studiopro). 
-* Install the latest Studio Pro version from the Mendix [Marketplace](https://marketplace.mendix.com/link/studiopro/).
 * A development IDE to develop your extensions. We recommend using [Visual Studio Code](https://code.visualstudio.com/).
 * Install the latest version 22.x.x of Node: https://nodejs.org/en/download.
 

content/en/docs/control-center/entitlements/cloud-tokens.md

@@ -20,7 +20,7 @@ These are the details available for each transaction that uses Mendix Cloud Toke
 * **App** – The app that triggered the transaction.
 * **Transaction** – The type of transaction.
 * **Cloud Resource Pack** – The Cloud Resource Pack that corresponds to the transaction. For more information, refer to [Cloud Resource Packs](#crps).
-* **Cloud Credits** – The number of Mendix Cloud Tokens consumed by the transaction.
+* **Cloud Tokens** – The number of Mendix Cloud Tokens consumed by the transaction.
 * **Tokens Remaining** – The number of Mendix Cloud Tokens remaining after the transaction was completed.
 
 ## Mendix Cloud Tokens {#cloud-tokens}

content/en/docs/deployment/cloud-foundry-deploy.md

@@ -20,6 +20,8 @@ aliases:
 
 ## Introduction
 
+{{% alert color="warning" %}} Cloud Foundry deployment from Studio Pro is deprecated in version 10 and removed in version 11. {{% /alert %}}
+
 Mendix apps can be deployed to a variety of different environments, for example Mendix Cloud, on-premises, or Kubernetes.
 
 Mendix apps can also be deployed to any cloud platform which supports a version of Cloud Foundry, database, and cloud storage at or above the minimum required version which supports Mendix. For specific version numbers see [Mendix System Requirements](/refguide/system-requirements/). 
@@ -162,15 +164,15 @@ You may need to configure your file store by using environment variables. See th
 
 ## ⚠ Deploy Your App to Cloud Foundry (Deprecated)
 
-1. Open Studio Pro
+1. Open Studio Pro.
 2. Open the app you want to deploy to Cloud Foundry.
 3. Choose the menu option **Run > Run on Cloud Foundry**:
 
     {{< figure src="/attachments/deployment/cloud-foundry-deploy/run-on-cf.png" class="no-border" >}} 
 
 The Mendix app will now be deployed to the configured Cloud Foundry app and started automatically
 
-{{% alert color="warning" %}}Deploying directly to Cloud Foundry from Studio Pro is deprecated. This functionality will be removed in Mendix 11.{{% /alert %}}
+{{% alert color="warning" %}} Cloud Foundry deployment from Studio Pro is deprecated in version 10 and removed in version 11. {{% /alert %}}
 
 ## Cloud Foundry Environment Variables
 

content/en/docs/deployment/general/running-in-iframe.md

@@ -8,21 +8,33 @@ description: "Issues to take into consideration when running apps in an iframe"
 
 ## Introduction
 
-By default, a Mendix app is blocked from running inside an iframe. This is to protect the end-user from attacks using *clickjacking*. There is more information on this in the [Adding HTTP Headers](/howto/security/best-practices-security/#adding-http-header) section of *How To Implement Best Practices for App Security*.
+By default, a Mendix application is blocked from running inside an iframe. This is to protect the end-user from attacks using *clickjacking*. There is more information on this in the [Adding HTTP Headers](/howto/security/best-practices-security/#adding-http-header) section of *How To Implement Best Practices for App Security*.
 
-You can enable your app to run inside an iframe by setting the `frame-ancestors` directive of the `Content-Security-Policy` HTTP header for your node’s environment. For Mendix Cloud, this can be done within the Mendix Portal, as described in the [HTTP Headers](/developerportal/deploy/environments-details/#http-headers) section of *Environment Details*.
+You can enable your application to run inside an iframe by setting a [Content Security Policy](#running-mendix-app) directive.
 
 There is more information about iframes on Mendix Cloud in the [Running Your App in an Iframe](/developerportal/deploy/environments-details/#iframe) section of *Environment Details*.
 
 You can also set the obsolete `X-Frame-Options` HTTP header if you need backward compatibility. 
 
+## Content Security Policy {#csp}
+
+When Content Security Policy (CSP) is enforced additional directives are needed for running a Mendix application in an iframe for both the host application and the Mendix application.
+
+### Host Application
+
+If the host application enforces CSP, it must be configured to explicitly allow loading frames and scripts from the Mendix application’s URL.
+
+### Mendix Application {#running-mendix-app}
+
+To allow a Mendix application to run in an iframe, the `frame-ancestors` directive of the `Content-Security-Policy` HTTP header for your node’s environment needs to be set. For Mendix Cloud, this can be done within the Mendix Portal, as described in the [HTTP Headers](/developerportal/deploy/environments-details/#http-headers) section of *Environment Details*.
+
 ## Resolving Browser Issues
 
-Most browsers have additional security to ensure that iframes are only allowed when they are from the same domain as the main page. If your app does not have the same domain as the main page containing the iframe, it will only run if the *SameSite* cookie is set to allow this. You can find a good explanation of SameSite cookies in [SameSite cookies explained](https://web.dev/samesite-cookies-explained/) on the *web.dev* website.
+Most browsers have additional security to ensure that iframes are only allowed when they are from the same domain as the main page. If your application does not have the same domain as the main page containing the iframe, it will only run if the *SameSite* cookie is set to allow this. You can find a good explanation of SameSite cookies in [SameSite cookies explained](https://web.dev/samesite-cookies-explained/) on the *web.dev* website.
 
-When running your app in Mendix Cloud, you can set the SameSite cookie through a custom runtime setting as explained in the [Running Your App in an Iframe](/developerportal/deploy/environments-details/#iframe) section of *Environment Details*.
+When running your application in Mendix Cloud, you can set the SameSite cookie through a custom runtime setting as explained in the [Running Your App in an Iframe](/developerportal/deploy/environments-details/#iframe) section of *Environment Details*.
 
-If your app is deployed outside Mendix Cloud (on premises, for example), then you will need to configure your webserver to set the SameSite cookie to the correct value.
+If your application is deployed outside Mendix Cloud (on premises, for example), then you will need to configure your webserver to set the SameSite cookie to the correct value.
 
 ## Limitations
 
@@ -38,6 +50,12 @@ Mendix does not support native messaging between the embedded application and th
 
 Mendix applications embedded in iframes do not inherit the session or user credentials from the host application. To enable shared authentication, a secure custom mechanism, such as JWT-based authentication, must be implemented.
 
-### Content Security Policy (CSP) Requirements
+### Responsiveness
+
+Iframes are not natively responsive. This means that by default an `<iframe>` does not automatically resize itself to fit different screen sizes or maintain an aspect ratio as the viewport changes. Custom CSS or JavaScript libraries are needed to accomplish this.
+
+### Focus Management and Accessibility
+
+Focus management for iframes presents unique accessibility challenges because iframes create a separate document context, and the parent page loses direct control over focus once it enters the iframe.
 
-If the host application enforces a Content Security Policy, it must be configured to explicitly allow loading frames and scripts from the Mendix application’s URL.
+Iframes need careful handling and thorough testing to ensure accessibility, especially for keyboard and screen reader users.

content/en/docs/deployment/mendix-cloud-deploy/access-restrictions.md

@@ -30,7 +30,7 @@ To view or manage access restriction profiles, follow these steps:
 
 When configuring an access restriction profile, keep the following considerations in mind:
 
-* Access restriction profiles are configured at the application level. They can be reused in all the environments (test, acceptance, production) of an app.
+* Access restriction profiles are configured at the application level. They can be reused in all the environments (for example test, acceptance, production) of an app.
 * Access restriction profiles can contain any number of IPv4 address ranges, client CAs, or both.
 * If an access restriction profile contains both IP address ranges and client CAs, then any match on either the IP range or the client certificate will grant access.
 

content/en/docs/deployment/sap-btp/_index.md

@@ -739,6 +739,7 @@ Since SAP Application Logging will soon be deprecated, you need to migrate your
 3. Click **Connect Services** and restart your application to bind the new SAP Cloud logging service.
 4. At this point, both **application-logs** and **cloud-logging** services will be active for your application.
 5. Retain the **application-logs** service until its log retention period ends, to ensure access to existing log entries. Then, delete it following the instructions provided in the [Unbinding and Removing Services](/developerportal/deploy/sap-cloud-platform/#unbinding-and-removing-services) section above. After this, only the new SAP Cloud Logging service will remain active.
+6. When using the **cloud-logging** service, upgrade **SapApplicationLogs** to the latest version. If you are using an older version, update the **Default Value** of the **LoggingService** constant to *cloud-logging* in the [SAP Logging Connector](https://marketplace.mendix.com/link/component/110219). For more information, refer to the [Using the Connector](/appstore/modules/sap/sap-logger/#using-the-connector) section of the *SAP Logging Connector* document.
 
 ## Troubleshooting
 

content/en/docs/marketplace/genai/_index.md

@@ -81,7 +81,7 @@ Mendix connectors offer direct support for the following models:
 | | Amazon Titan Image Generator G1 | Image generation | text | image | |
 | | Amazon Titan Embeddings Text v2 | Embeddings | text | embeddings| |
 | | Anthropic Claude 2.0, Anthropic Claude 2.1| Chat Completions | text, document | text | |
-| | Anthropic Claude 3 Sonnet, Anthropic Claude 3.5 Sonnet, Anthropic Claude 3.5 Sonnet v2, Anthropic Claude 3 Haiku, Anthropic Claude 3 Opus, Anthropic Claude 3.5 Haiku, Anthropic Claude 3.7 Sonnet  | Chat Completions | text, image, document | text | Function calling |
+| | Anthropic Claude 3 Sonnet, Anthropic Claude 3.5 Sonnet, Anthropic Claude 3.5 Sonnet v2, Anthropic Claude 3 Haiku, Anthropic Claude 3 Opus, Anthropic Claude 3.5 Haiku, Anthropic Claude 3.7 Sonnet, Anthropic Claude 4 Sonnet  | Chat Completions | text, image, document | text | Function calling |
 | | Cohere Command | Chat Completions | text, document | text | |
 | | Cohere Command Light | Chat Completions | text | text | |
 | | Cohere Command R, Cohere Command R+ | Chat Completions | text, document | text | Function calling |