diff --git a/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/pipeline-api-v2.md b/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/pipeline-api-v2.md index f8284c8e5f6..d257f7742ea 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/pipeline-api-v2.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/pipeline-api-v2.md @@ -26,4 +26,4 @@ For information about Pipeline API version 1, see [Pipeline API - Version 1](/ap ## API Reference -{{< swaggerui src="/openapi-spec/openapi-pipeline-v2.yaml" >}} \ No newline at end of file +{{< swaggerui src="/openapi-spec/openapi-pipeline-v2.yaml" >}} diff --git a/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api-v2.md b/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api-v2.md index 546a29a0135..7f31094aa86 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api-v2.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api-v2.md @@ -32,4 +32,4 @@ For information about Project API version 1, see [Project API - Version 1](/apid ## API Reference -{{< swaggerui src="/openapi-spec/openapi-project-v2.yaml" >}} \ No newline at end of file +{{< swaggerui src="/openapi-spec/openapi-project-v2.yaml" >}} diff --git a/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api.md b/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api.md index fd4fc4db559..255c5c4e888 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api.md @@ -31,4 +31,4 @@ For information about Project API version 2, see [Project API - Version 2](/apid ## API Reference -{{< swaggerui src="/openapi-spec/openapi-project-v1.yaml" >}} \ No newline at end of file +{{< swaggerui src="/openapi-spec/openapi-project-v1.yaml" >}} diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/consistency-checks.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/consistency-checks.md index 635866d3799..d216d63c0e6 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/consistency-checks.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/consistency-checks.md @@ -279,7 +279,6 @@ export const component: IComponent = { }; ``` - Replace your `src/model/PersonInfo.ts` file with the following: ```typescript {hl_lines=["6-10"]} @@ -416,7 +415,6 @@ export const component: IComponent = { }; ``` - Return `dependentElementIds` to tell Studio Pro which elements your document depends on. When those elements change, your checks rerun automatically. {{% alert color="info" %}} @@ -487,7 +485,6 @@ async function checkDependencyWasChanged(dependencies: Dependency[], documents: By checking whether any of the changed documents from the event payload are included in your dependencies, you can trigger the consistency checks to run again by updating the content of your blob document using `studioPro.app.model.customBlobDocuments.updateDocumentContent`. This ensures your checks run again whenever one of your dependencies is modified in Studio Pro. - ### Renamed Elements If one of your dependencies gets renamed, you may need to update the dependency names in your document. Studio Pro cannot automatically rename your dependencies; it can only notify you that the document matching the ID now has a new name. It is up to you to update your dependency's name. diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/permissions.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/permissions.md index 04229a24bb1..7ae30214b2a 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/permissions.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/permissions.md @@ -90,6 +90,7 @@ export const component: IComponent = { } }; ``` + The `permissionsChanged` event fires for all extensions whenever any permission is granted or revoked anywhere in the system, not just for your extension. This means multiple extensions may respond to the same event simultaneously. To check if a change affects your extension, compare the old granted state against the new one for each permission name your extension declared. Without this check, your extension fires a notification every time any permission changes, including changes unrelated to your extension. diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md index 1296b4dbd65..ba898727cf3 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md @@ -485,7 +485,7 @@ if (selection.type === "Single") { ## Exposed Modules - ### Session {#session} +### Session {#session} The Mendix Platform exposes a `mendix/session` module for inspecting the current user session. It is available in both web and native. diff --git a/content/en/docs/catalog/_index.md b/content/en/docs/catalog/_index.md index a0c29eed824..676abf800b7 100644 --- a/content/en/docs/catalog/_index.md +++ b/content/en/docs/catalog/_index.md @@ -54,7 +54,6 @@ From the **Home** screen, you can do the following: The Catalog is also integrated in Mendix Studio Pro to find and connect to shared services in your apps. For further details on using Catalog in Studio Pro, see [Integration Pane](/refguide/integration-pane/) in the *Studio Pro Guide*. - ## Information Available in the Catalog {#available-info} In the Catalog, all the information for registered assets is displayed in the [Catalog search details](/catalog/manage/search/#search-details) screen. This information comes from the metadata in the OData service contract, and also from additional metadata that is added when registered assets are curated. Registered assets can be curated by owners, [Curators](/catalog/manage/user-roles/#curator), and [Mendix Admins](/catalog/manage/user-roles/#admin). diff --git a/content/en/docs/control-center/maia/_index.md b/content/en/docs/control-center/maia/_index.md index 34d48b4c7ef..7c4369605a4 100644 --- a/content/en/docs/control-center/maia/_index.md +++ b/content/en/docs/control-center/maia/_index.md @@ -10,4 +10,4 @@ no_list: false The **Maia** section allows you to manage, control, and monitor Maia resources and behavior on Mendix Portal. -## Documents in This Category \ No newline at end of file +## Documents in This Category diff --git a/content/en/docs/control-center/security/policies.md b/content/en/docs/control-center/security/policies.md index 770a2df0c88..1a3479bbea8 100644 --- a/content/en/docs/control-center/security/policies.md +++ b/content/en/docs/control-center/security/policies.md @@ -43,41 +43,41 @@ You can create a policy by defining your own details. 2. On the **Policy Definition** tab, fill in the following details: -* **Policy Name** – A relevant name for your policy, such as one indicating what the policy checks. -* **Description** – A description of the goal of the policy, which covers why it needs to be adhered to, and how to fix its violations. -* **Policy Conditions** – Define the conditions under which the policy is considered violated. These are the available conditions and their values: + * **Policy Name** – A relevant name for your policy, such as one indicating what the policy checks. + * **Description** – A description of the goal of the policy, which covers why it needs to be adhered to, and how to fix its violations. + * **Policy Conditions** – Define the conditions under which the policy is considered violated. These are the available conditions and their values: - * **Any finding severity is** – Choose which severity level violates the policy. You can select one or more of the following values: + * **Any finding severity is** – Choose which severity level violates the policy. You can select one or more of the following values: - * **LOW** - * **MEDIUM** - * **HIGH** - * **CRITICAL** + * **LOW** + * **MEDIUM** + * **HIGH** + * **CRITICAL** - For example, if you select **CRITICAL**, apps with critical findings violate this policy. + For example, if you select **CRITICAL**, apps with critical findings violate this policy. - * **Mendix runtime version is lower than** – Indicate which Mendix version is the minimum that your apps must use. + * **Mendix runtime version is lower than** – Indicate which Mendix version is the minimum that your apps must use. - * **Marketplace component license is not** – Select the licenses that are acceptable. If a Marketplace component has a license which is not one of the ones you select here, the policy is violated. These are the possible values: + * **Marketplace component license is not** – Select the licenses that are acceptable. If a Marketplace component has a license which is not one of the ones you select here, the policy is violated. These are the possible values: - * MIT - * BSD_2_0 - * APACHE_V2 - * APACHE_1_0 - * MENDIX_EULA - * PARTNER_LICENSES - * CREATIVE_COMMONS_CC0 - * GNU_GENERAL_PUBLIC_LICENSE_V3 - * MENDIX_MARKETPLACE_CONTENT_TERMS + * MIT + * BSD_2_0 + * APACHE_V2 + * APACHE_1_0 + * MENDIX_EULA + * PARTNER_LICENSES + * CREATIVE_COMMONS_CC0 + * GNU_GENERAL_PUBLIC_LICENSE_V3 + * MENDIX_MARKETPLACE_CONTENT_TERMS - * **Marketplace component support is not** – Select the support types that are acceptable. If a Marketplace component has a support type which is not one of the ones you select here, the policy is violated. These are the possible values: + * **Marketplace component support is not** – Select the support types that are acceptable. If a Marketplace component has a support type which is not one of the ones you select here, the policy is violated. These are the possible values: - * PARTNER - * SIEMENS - * PLATFORM - * COMMUNITY + * PARTNER + * SIEMENS + * PLATFORM + * COMMUNITY -* **Checkpoints & Action(s)** – Select the trigger which causes the policy to be checked, and the action that is taken if the policy is violated. Currently, policy violations are checked at the time of package creation, and violations generate warnings. + * **Checkpoints & Action(s)** – Select the trigger which causes the policy to be checked, and the action that is taken if the policy is violated. Currently, policy violations are checked at the time of package creation, and violations generate warnings. 3. On the **Policy Scope** tab, select whether you want the policy to apply to all licensed apps, or only to specific apps in your environment. diff --git a/content/en/docs/deployment/general/subscription-management/user-metering/implementing-user-metering.md b/content/en/docs/deployment/general/subscription-management/user-metering/implementing-user-metering.md index e34f3187f1b..0e28a78a727 100644 --- a/content/en/docs/deployment/general/subscription-management/user-metering/implementing-user-metering.md +++ b/content/en/docs/deployment/general/subscription-management/user-metering/implementing-user-metering.md @@ -119,7 +119,6 @@ The improved user metering capabilities are introduced in Mendix 11. These capab | Multi-app user identification | `system.user.name` | `system.user.name` or `NamedUserIdentifier` in User Commons v2.2.0 and above | | SCIM-based user deactivation | SCIM v3.0.0 and above | SCIM v4.0.0 and above | - ## Domain Model Entities {#domain-model-entities} This section explains the entities and their attributes in your application domain model that are relevant for user metering. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/deploy-apis-with-ai-agents.md b/content/en/docs/deployment/mendix-cloud-deploy/deploy-apis-with-ai-agents.md index 6fd3aa1dc0b..7809ea52706 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/deploy-apis-with-ai-agents.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/deploy-apis-with-ai-agents.md @@ -45,7 +45,6 @@ Replace the following placeholders with your credentials: * `{Mendix-Username}` – the login name of the user making the request, with the required privileges in the Mendix Platform * `{Mendix-ApiKey}` – the API key associated with that user - To verify the connection, run the following command: ```bash @@ -161,7 +160,6 @@ Two authentication methods are used depending on the API: Include all three headers in your connection configuration to ensure all tools work correctly. {{% /alert %}} - ## Client Compatibility {#compatibility} The Mendix MCP integration works with any MCP-compatible client that supports HTTP transport (streamable HTTP) and custom headers for authentication. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/opentelemetry.md b/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/opentelemetry.md index 11cb4959310..4fcb947dda1 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/opentelemetry.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/opentelemetry.md @@ -150,7 +150,7 @@ These variables control the resource attributes attached to all telemetry. They | `MX_OTEL_SERVICE_NAME` | App subdomain | Service name (`service.name` attribute). Defaults to the subdomain of the app's first route (for example, `my-app` from `my-app.mendixcloud.com`). Set this variable to override it. | | `MX_OTEL_SERVICE_VERSION` | Model version | Service version (`service.version` attribute). Defaults to the Mendix model version. Falls back to the `version` application tag if set, otherwise `unversioned`. | | `MX_OTEL_DEPLOYMENT_ENV` | `env` tag or `none` | Deployment environment (`deployment.environment.name` attribute). Defaults to the `env` application tag if set, otherwise `none`. | -| `MX_OTEL_RESOURCE_ATTRIBUTES` | _(from app tags)_ | Additional resource attributes as comma-separated `key=value` pairs. Automatically populated from the application tags set in the Developer Portal. Can be set directly to override the tag-derived value. | +| `MX_OTEL_RESOURCE_ATTRIBUTES` | *(from app tags)* | Additional resource attributes as comma-separated `key=value` pairs. Automatically populated from the application tags set in the Developer Portal. Can be set directly to override the tag-derived value. | ### OpenTelemetry Issues diff --git a/content/en/docs/deployment/on-premises-design/linux/linux.md b/content/en/docs/deployment/on-premises-design/linux/linux.md index 8b181f02991..c03ccb5567a 100644 --- a/content/en/docs/deployment/on-premises-design/linux/linux.md +++ b/content/en/docs/deployment/on-premises-design/linux/linux.md @@ -14,7 +14,6 @@ With the release of [Mendix Portable Runtime](https://docs.mendix.com/developerp For more information, see [Mendix Portable Runtime: Deployment, Simplified](https://www.mendix.com/blog/mendix-portable-runtime/). {{% /alert %}} - ## Introduction Mendix can be installed on premises on systems running Linux. The installation consists of the following: diff --git a/content/en/docs/deployment/pad/docker-monitoring.md b/content/en/docs/deployment/pad/docker-monitoring.md index ae53a6d97c8..f9ff00e14ca 100644 --- a/content/en/docs/deployment/pad/docker-monitoring.md +++ b/content/en/docs/deployment/pad/docker-monitoring.md @@ -71,4 +71,4 @@ Dynatrace offers the following features: ### Installing and Monitoring Docker Containers with Dynatrace -To integrate Dynatrace with your Docker environment for comprehensive monitoring, see [Set up Dynatrace on Docker](https://docs.dynatrace.com/docs/ingest-from/setup-on-container-platforms/docker) in Dynatrace documentation. \ No newline at end of file +To integrate Dynatrace with your Docker environment for comprehensive monitoring, see [Set up Dynatrace on Docker](https://docs.dynatrace.com/docs/ingest-from/setup-on-container-platforms/docker) in Dynatrace documentation. diff --git a/content/en/docs/deployment/pad/pad-troubleshooting.md b/content/en/docs/deployment/pad/pad-troubleshooting.md index feadae7a71c..0ba2ce37270 100644 --- a/content/en/docs/deployment/pad/pad-troubleshooting.md +++ b/content/en/docs/deployment/pad/pad-troubleshooting.md @@ -94,4 +94,4 @@ The value of `M2EE_ADMIN_PASS` is not set. ### Solution -Set the value of `M2EE_ADMIN _PASS`. For more information, see [Mendix Portable Runtime: Deploying Locally](/developerportal/deploy/portable-app-distribution-deploy/#deploy-local). \ No newline at end of file +Set the value of `M2EE_ADMIN _PASS`. For more information, see [Mendix Portable Runtime: Deploying Locally](/developerportal/deploy/portable-app-distribution-deploy/#deploy-local). diff --git a/content/en/docs/deployment/private-cloud/private-cloud-operator.md b/content/en/docs/deployment/private-cloud/private-cloud-operator.md index 64509e0f06c..80cfc4750ff 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-operator.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-operator.md @@ -240,8 +240,8 @@ You must make the following changes: * **environmentVariables** - Set the environment variables for the Mendix app container, and JVM arguments through the `JAVA_TOOL_OPTIONS` environment variable. * **clientCertificates** - Specify client certificates to be used for TLS calls to Web Services and REST services. - * When **key** and **password** are specified, will use the client TLS certificate specified directly in the **MendixApp** CR. - * When **certificateSecret** is specified without a **key** and **password**, will load a client TLS certificate from the specified Kubernetes Secret. This feature requires Mendix Operator 2.27 or newer. + * When **key** and **password** are specified, will use the client TLS certificate specified directly in the **MendixApp** CR. + * When **certificateSecret** is specified without a **key** and **password**, will load a client TLS certificate from the specified Kubernetes Secret. This feature requires Mendix Operator 2.27 or newer. * **runtimeMetricsConfiguration** - Specify how metrics should be collected. Any non-empty values override the [default values](/developerportal/deploy/private-cloud-cluster/#customize-runtime-metrics) from `OperatorConfiguration`. Refer to [Monitoring Environments in Mendix on Kubernetes](/developerportal/deploy/private-cloud-monitor/) for details on how to monitor your environment. * **runtimeLeaderSelection** - Specify how the leader replica should be selected. The following options are available: @@ -343,7 +343,6 @@ If you read the secret and see `data` instead of `stringData`, the values of the This ensures that a binary PKCS12 file can be safely stored and edited as a plaintext string. {{% /alert %}} - ```yaml apiVersion: privatecloud.mendix.com/v1alpha1 kind: MendixApp diff --git a/content/en/docs/developerportal/maia-plan/maia-plan-mcp/_index.md b/content/en/docs/developerportal/maia-plan/maia-plan-mcp/_index.md index 28083b5f56b..11f6f74f88e 100644 --- a/content/en/docs/developerportal/maia-plan/maia-plan-mcp/_index.md +++ b/content/en/docs/developerportal/maia-plan/maia-plan-mcp/_index.md @@ -128,6 +128,7 @@ To configure Visual Studio Code Copilot to connect to the Maia Plan MCP server, } } ``` + 3. In Visual Studio Code, follow these steps: 1. Open **Command Palette**. diff --git a/content/en/docs/genai/_index.md b/content/en/docs/genai/_index.md index 53ffd7fd45d..21f077d34b3 100644 --- a/content/en/docs/genai/_index.md +++ b/content/en/docs/genai/_index.md @@ -106,4 +106,4 @@ In addition to the models listed above, you can also connect to other models by If you have any questions, encounter errors, or want to share feedback, reach out in the [#genai-connectors](https://mendixcommunity.slack.com/archives/C07P8NRBLN9) channel in the Mendix Community Slack workspace. To sign up for this workspace, use [this invitation link](https://mendixcommunity.slack.com/join/shared_invite/zt-270ys3pwi-kgWhJUwWrKMEMuQln4bqrQ#/shared-invite/email). -## Documents in This Category \ No newline at end of file +## Documents in This Category diff --git a/content/en/docs/genai/v1/_index.md b/content/en/docs/genai/v1/_index.md index e1e9d9e6122..c2e808d73ef 100644 --- a/content/en/docs/genai/v1/_index.md +++ b/content/en/docs/genai/v1/_index.md @@ -82,4 +82,4 @@ Older versions of some modules and the GenAI Showcase App are available in Studi * [Release and Migration Guide for GenAI Modules](/agents/agents-kit-1/reference-guide/migration-guide/) - Describes the combined releases of various GenAI-related modules and their inter-module dependencies. Also includes migration steps and notices about deprecations and removals. \ No newline at end of file + Describes the combined releases of various GenAI-related modules and their inter-module dependencies. Also includes migration steps and notices about deprecations and removals. diff --git a/content/en/docs/genai/v1/how-to/creating-agents/shared-setup.md b/content/en/docs/genai/v1/how-to/creating-agents/shared-setup.md index 525bcdb90ab..fa5a6e16943 100644 --- a/content/en/docs/genai/v1/how-to/creating-agents/shared-setup.md +++ b/content/en/docs/genai/v1/how-to/creating-agents/shared-setup.md @@ -73,6 +73,7 @@ The agent interacts with data from a knowledge base and the Mendix app. To make Each of these steps is described in the following sections. To define the agent and generate responses, the steps differ based on your chosen approach and are covered in separate documents. + ### Ingesting Data Into Knowledge Base {#ingest-knowledge-base} Ingest Mendix ticket data into the knowledge base. For a detailed guide, see [Grounding Your LLM in Data](/agents/agents-kit-1/how-to/howto-groundllm/#demodata). The following steps explain the process at a higher level by modifying logic imported from the [GenAI Showcase App](https://marketplace.mendix.com/link/component/220475). You can find the sample data used in this document in the GenAI Showcase App or use your own data. diff --git a/content/en/docs/genai/v1/reference-guide/mcp-modules/mcp-client.md b/content/en/docs/genai/v1/reference-guide/mcp-modules/mcp-client.md index 848671a9633..f76e42b92b9 100644 --- a/content/en/docs/genai/v1/reference-guide/mcp-modules/mcp-client.md +++ b/content/en/docs/genai/v1/reference-guide/mcp-modules/mcp-client.md @@ -100,4 +100,3 @@ There are several possible reasons why the client cannot connect to your server. * The [GenAI Showcase App](https://marketplace.mendix.com/link/component/220475) provides an example on how to expose microflows as tools via the MCP Server module. * The official [MCP docs](https://modelcontextprotocol.io/introduction) * The [MCP Java SDK GitHub Repository](https://github.com/modelcontextprotocol/java-sdk) - diff --git a/content/en/docs/genai/v2/how-to/creating-agents/shared-setup.md b/content/en/docs/genai/v2/how-to/creating-agents/shared-setup.md index 50996730d3f..3dbdc5f6d36 100644 --- a/content/en/docs/genai/v2/how-to/creating-agents/shared-setup.md +++ b/content/en/docs/genai/v2/how-to/creating-agents/shared-setup.md @@ -70,6 +70,7 @@ The agent interacts with data from a knowledge base and the Mendix app. To make Each of these steps is described in the following sections. To define the agent and generate responses, the steps differ based on your chosen approach and are covered in separate documents. + ### Ingesting Data Into Knowledge Base {#ingest-knowledge-base} Ingest Mendix ticket data into the knowledge base. For a detailed guide, see [Grounding Your LLM in Data](/agents/agents-kit-2/how-to/howto-groundllm/#demodata). The following steps explain the process at a higher level by modifying logic imported from the [GenAI Showcase App](https://marketplace.mendix.com/link/component/220475). You can find the sample data used in this document in the GenAI Showcase App or use your own data. diff --git a/content/en/docs/genai/v2/reference-guide/mcp-modules/mcp-client.md b/content/en/docs/genai/v2/reference-guide/mcp-modules/mcp-client.md index 1361e730cea..afd227fea47 100644 --- a/content/en/docs/genai/v2/reference-guide/mcp-modules/mcp-client.md +++ b/content/en/docs/genai/v2/reference-guide/mcp-modules/mcp-client.md @@ -98,4 +98,3 @@ There are several possible reasons why the client cannot connect to your server. * The [GenAI Showcase App](https://marketplace.mendix.com/link/component/220475) provides an example on how to expose microflows as tools via the MCP Server module. * The official [MCP docs](https://modelcontextprotocol.io/introduction) * The [MCP Java SDK GitHub Repository](https://github.com/modelcontextprotocol/java-sdk) - diff --git a/content/en/docs/genai/v2/release-guide.md b/content/en/docs/genai/v2/release-guide.md index eaeddfa388e..b79c28fd55b 100644 --- a/content/en/docs/genai/v2/release-guide.md +++ b/content/en/docs/genai/v2/release-guide.md @@ -63,4 +63,4 @@ Agents Kit 2 modules are compatible with [Atlas UI 4](/refguide/frontend/atlas4- * Feature parity between Agent Builder in Runtime and Agent Editor in Studio Pro is still in progress, particularly for external provider support and human-in-the-loop capabilities. * The [RFP Assistant Starter App](https://marketplace.mendix.com/link/component/235917) now supports Studio Pro agents and requires [Mendix Cloud GenAI](/agents/mx-cloud-genai/). -* The latest version of the [AI Bot Starter App](https://marketplace.mendix.com/link/component/227926) remains available in Studio Pro 10.24 and has not been upgraded for Agents Kit 2, as its use case does not rely on agents. \ No newline at end of file +* The latest version of the [AI Bot Starter App](https://marketplace.mendix.com/link/component/227926) remains available in Studio Pro 10.24 and has not been upgraded for Agents Kit 2, as its use case does not rely on agents. diff --git a/content/en/docs/marketplace/manage-content/_index.md b/content/en/docs/marketplace/manage-content/_index.md index 03f1b0b3c7e..283aef8a02f 100644 --- a/content/en/docs/marketplace/manage-content/_index.md +++ b/content/en/docs/marketplace/manage-content/_index.md @@ -11,4 +11,4 @@ description_list: true This section provides information about creating content, uploading it to Mendix Marketplace, and deprecating it if necessary. -## Documents in This Category \ No newline at end of file +## Documents in This Category diff --git a/content/en/docs/marketplace/platform-supported-content/widgets/fieldset.md b/content/en/docs/marketplace/platform-supported-content/widgets/fieldset.md index 0b929aeffd3..c7b659fed80 100644 --- a/content/en/docs/marketplace/platform-supported-content/widgets/fieldset.md +++ b/content/en/docs/marketplace/platform-supported-content/widgets/fieldset.md @@ -17,4 +17,3 @@ The [Fieldset](https://marketplace.mendix.com/link/component/113922/Mendix/Field ## Limitations * This widget should only be used to group widgets belonging to a form - diff --git a/content/en/docs/marketplace/platform-supported-content/widgets/image-cropper.md b/content/en/docs/marketplace/platform-supported-content/widgets/image-cropper.md index 8583ba507e2..fc06cb8b61b 100644 --- a/content/en/docs/marketplace/platform-supported-content/widgets/image-cropper.md +++ b/content/en/docs/marketplace/platform-supported-content/widgets/image-cropper.md @@ -19,20 +19,20 @@ This widget replaces the legacy [Image Crop](/appstore/modules/image-crop/) modu ### Features -- Crop with a rectangular or circular crop shape -- Constrain the crop to a fixed aspect ratio (1:1, 16:9, 4:3, 3:4), a custom ratio, or a free selection -- Zoom with a slider and/or the mouse wheel -- Rotate the image in 90-degree increments -- Convert the image to grayscale -- Reset the image back to its original state -- Save the result as PNG or JPEG at the source or on-screen resolution -- Trigger a Mendix action each time the crop is applied +* Crop with a rectangular or circular crop shape +* Constrain the crop to a fixed aspect ratio (1:1, 16:9, 4:3, 3:4), a custom ratio, or a free selection +* Zoom with a slider and/or the mouse wheel +* Rotate the image in 90-degree increments +* Convert the image to grayscale +* Reset the image back to its original state +* Save the result as PNG or JPEG at the source or on-screen resolution +* Trigger a Mendix action each time the crop is applied ### Limitations -- The widget requires an editable image attribute and both reads from and writes to that same attribute. There is no separate output attribute. -- Editing operations do not save back to a read-only image attribute. -- The widget is available on the web platform only and is not offline capable. +* The widget requires an editable image attribute and both reads from and writes to that same attribute. There is no separate output attribute. +* Editing operations do not save back to a read-only image attribute. +* The widget is available on the web platform only and is not offline capable. ## Configuration @@ -44,27 +44,27 @@ The following sections will describe the different available widget properties a The **Source** section (required) is used to configure the image the widget edits. It has the following property: -- **Image attribute** – Specifies the image the end-user wants to crop. - - The cropped result is saved back to this same attribute. - - The attribute is both the source and the destination for the widget. +* **Image attribute** – Specifies the image the end-user wants to crop. + * The cropped result is saved back to this same attribute. + * The attribute is both the source and the destination for the widget. #### Crop Area Section The **Crop area** section is used to configure the shape and proportions of the crop selection. It includes the following properties: * **Crop shape** – Defines the shape of the crop. - * **Rectangle** (default) – When enabled, the full crop rectangle is saved. - * **Circle** – When enabled, the corners are masked and the saved image is clipped to an ellipse inscribed in the crop rectangle. -- **Aspect ratio** – Locks the crop proportions. - * **Free** (default) – The end-user can resize the selection to any proportion. - * **1:1**, **16:9**, **4:3**, or **3:4** – When set to one of these predetermined ratios, the selection is locked to that ratio during resize. - * **Custom** – When enabled, the selection is locked to the ratio defined by **Custom aspect width** and **Custom aspect height**. -- **Custom aspect width** (default **1**) – The width side of the ratio (for example, _3_ in 3:2). - - Configurable when **Aspect ratio** is set to **Custom**. - - When either the custom width or custom height is not greater than _0_, the selection falls back to a free-form shape. -- **Custom aspect height** (default **1**) – The height side of the ratio (for example, _2_ in 3:2). - - Configurable when **Aspect ratio** is set to **Custom**. - - When either the custom width or custom height is not greater than _0_, the selection falls back to a free-form shape. + * **Rectangle** (default) – When enabled, the full crop rectangle is saved. + * **Circle** – When enabled, the corners are masked and the saved image is clipped to an ellipse inscribed in the crop rectangle. +* **Aspect ratio** – Locks the crop proportions. + * **Free** (default) – The end-user can resize the selection to any proportion. + * **1:1**, **16:9**, **4:3**, or **3:4** – When set to one of these predetermined ratios, the selection is locked to that ratio during resize. + * **Custom** – When enabled, the selection is locked to the ratio defined by **Custom aspect width** and **Custom aspect height**. +* **Custom aspect width** (default **1**) – The width side of the ratio (for example, *3* in 3:2). + * Configurable when **Aspect ratio** is set to **Custom**. + * When either the custom width or custom height is not greater than *0*, the selection falls back to a free-form shape. +* **Custom aspect height** (default **1**) – The height side of the ratio (for example, *2* in 3:2). + * Configurable when **Aspect ratio** is set to **Custom**. + * When either the custom width or custom height is not greater than *0*, the selection falls back to a free-form shape. {{< figure src="/attachments/appstore/platform-supported-content/widgets/image-cropper/image-cropper-circle-demo.gif" alt="Cropping an image with a circular crop shape" class="no-border" >}} @@ -72,8 +72,8 @@ The **Crop area** section is used to configure the shape and proportions of the The **Events** section allows you to configure what happens each time the crop is applied. It includes the following property: -- **On crop** (optional) – A Mendix action that runs each time the crop is auto-applied to the image attribute. - - The action runs after a crop is saved back, but not after a rotation or a reset. +* **On crop** (optional) – A Mendix action that runs each time the crop is auto-applied to the image attribute. + * The action runs after a crop is saved back, but not after a rotation or a reset. ### Dimensions Tab {#dimensions} @@ -81,12 +81,12 @@ The **Events** section allows you to configure what happens each time the crop i The **Canvas** section is used to configure the on-screen size of the crop area. It includes the following properties: -- **Canvas max width (px)** (default **800**) – Sets the maximum on-screen width of the crop area. - - The image scales down to fit, and the canvas wraps the rendered image so that smaller crops produce a smaller canvas with no blank gaps. - - This property does not change the saved image size. -- **Canvas max height (px)** (default **800**) – the maximum on-screen height of the crop area. - - The image scales down to fit, and the canvas wraps the rendered image so that smaller crops produce a smaller canvas with no blank gaps. - - This property does not change the saved image size. +* **Canvas max width (px)** (default **800**) – Sets the maximum on-screen width of the crop area. + * The image scales down to fit, and the canvas wraps the rendered image so that smaller crops produce a smaller canvas with no blank gaps. + * This property does not change the saved image size. +* **Canvas max height (px)** (default **800**) – the maximum on-screen height of the crop area. + * The image scales down to fit, and the canvas wraps the rendered image so that smaller crops produce a smaller canvas with no blank gaps. + * This property does not change the saved image size. ### Behavior Tab {#behavior} @@ -94,41 +94,41 @@ The **Canvas** section is used to configure the on-screen size of the crop area. The **Interaction** section is used to configure how the end-user interacts with the crop selection. It includes the following property: -- **Resizable handles** (default **Yes**) – Allows the end-user to resize the selection by dragging its corners. - - When set to **No**, the selection cannot be resized by dragging its corners. +* **Resizable handles** (default **Yes**) – Allows the end-user to resize the selection by dragging its corners. + * When set to **No**, the selection cannot be resized by dragging its corners. #### Buttons Section The **Buttons** section is used to configure the editing buttons shown in the toolbar. It includes the following properties: -- **Enable rotation** (default **Yes**) – Shows rotate-left and rotate-right buttons that rotate the image in 90-degree increments. - - The rotation is baked into the saved image. -- **Enable grayscale** (default **No**) – Shows a grayscale toggle. - - When the toggle is on, the saved image is converted to grayscale (black and white). -- **Enable reset** (default **Yes**) – Shows a **Reset** button that restores the original image and clears zoom, rotation, and grayscale. - - The button is available only when the original image could be captured. +* **Enable rotation** (default **Yes**) – Shows rotate-left and rotate-right buttons that rotate the image in 90-degree increments. + * The rotation is baked into the saved image. +* **Enable grayscale** (default **No**) – Shows a grayscale toggle. + * When the toggle is on, the saved image is converted to grayscale (black and white). +* **Enable reset** (default **Yes**) – Shows a **Reset** button that restores the original image and clears zoom, rotation, and grayscale. + * The button is available only when the original image could be captured. #### Zoom Section The **Zoom** section is used to configure how the end-user zooms the image. It includes the following properties: -- **Enable zoom** (default **Yes**) – The primary switch for zooming. - - When set to **No**, the slider and mouse-wheel zoom are disabled and the image stays at **1x**. -- **Show zoom slider** (default **Yes**) – shows the zoom slider below the crop area. - - Configurable when **Enable zoom** is set to **Yes**. - - Turn this off to keep mouse-wheel zoom while hiding the slider. -- **Mouse wheel zoom** (default **On (hold Ctrl)**) – Determines whether the mouse wheel zooms the image. - - Configurable when **Enable zoom** is set to **Yes**. - - When set to **On (hold Ctrl)**, the wheel zooms only while Ctrl is held, so page scroll keeps working. - - When set to **On**, the wheel always zooms. - - When set to **Off**, the wheel never zooms. -- **Minimum zoom** (default **1**) – Sets the smallest zoom level. - - Configurable when **Enable zoom** is set to **Yes**. - - A value of _1_ means the image fits the canvas; a value below _1_ lets the end-user zoom out further. -- **Maximum zoom** (default **4**) – Sets the largest zoom level. - - Configurable when **Enable zoom** is set to **Yes**. - - A value of _4_ means the image can be zoomed up to four times the canvas size. - - This value must be greater than **Minimum zoom**. +* **Enable zoom** (default **Yes**) – The primary switch for zooming. + * When set to **No**, the slider and mouse-wheel zoom are disabled and the image stays at **1x**. +* **Show zoom slider** (default **Yes**) – shows the zoom slider below the crop area. + * Configurable when **Enable zoom** is set to **Yes**. + * Turn this off to keep mouse-wheel zoom while hiding the slider. +* **Mouse wheel zoom** (default **On (hold Ctrl)**) – Determines whether the mouse wheel zooms the image. + * Configurable when **Enable zoom** is set to **Yes**. + * When set to **On (hold Ctrl)**, the wheel zooms only while Ctrl is held, so page scroll keeps working. + * When set to **On**, the wheel always zooms. + * When set to **Off**, the wheel never zooms. +* **Minimum zoom** (default **1**) – Sets the smallest zoom level. + * Configurable when **Enable zoom** is set to **Yes**. + * A value of *1* means the image fits the canvas; a value below *1* lets the end-user zoom out further. +* **Maximum zoom** (default **4**) – Sets the largest zoom level. + * Configurable when **Enable zoom** is set to **Yes**. + * A value of *4* means the image can be zoomed up to four times the canvas size. + * This value must be greater than **Minimum zoom**. ### Output Tab {#output} @@ -136,15 +136,15 @@ The **Zoom** section is used to configure how the end-user zooms the image. It i The **Output** section is used to configure the format and resolution of the saved image. It includes the following properties: -- **Output format** (default **PNG**) – Sets the file format of the saved image. - - When set to **PNG**, transparency is preserved and **JPEG quality** is ignored. - - When set to **JPEG**, a white background is filled behind the image and smaller files are produced. -- **JPEG quality (0.0 - 1.0)** (default **0.92**) – Sets the JPEG compression level. - - Configurable when **Output format** is set to **JPEG**. - - A higher value produces a sharper and larger file. -- **Output size** (default **Original (source resolution)**) – Sets the resolution of the saved crop. - - When set to **Original (source resolution)**, the crop is saved at the source resolution of the cropped region, which is the sharpest option. - - When set to **Viewport (canvas dimensions)**, the crop is saved at the on-screen canvas size. +* **Output format** (default **PNG**) – Sets the file format of the saved image. + * When set to **PNG**, transparency is preserved and **JPEG quality** is ignored. + * When set to **JPEG**, a white background is filled behind the image and smaller files are produced. +* **JPEG quality (0.0 - 1.0)** (default **0.92**) – Sets the JPEG compression level. + * Configurable when **Output format** is set to **JPEG**. + * A higher value produces a sharper and larger file. +* **Output size** (default **Original (source resolution)**) – Sets the resolution of the saved crop. + * When set to **Original (source resolution)**, the crop is saved at the source resolution of the cropped region, which is the sharpest option. + * When set to **Viewport (canvas dimensions)**, the crop is saved at the on-screen canvas size. ## Usage @@ -152,10 +152,10 @@ When the widget loads, it shows the image bound to the **Image attribute** with The end-user edits the image as follows: -- **Move or resize the crop box** – The crop is saved immediately when the end-user finishes the drag. -- **Zoom or toggle grayscale** – The change is saved a short moment after the last adjustment. -- **Rotate** – A live preview is shown immediately, and the rotation is then saved back to the image attribute. -- **Reset** – The original image is restored and zoom, rotation, and grayscale are cleared. A reset is not saved as a crop and does not trigger the **On crop** action. +* **Move or resize the crop box** – The crop is saved immediately when the end-user finishes the drag. +* **Zoom or toggle grayscale** – The change is saved a short moment after the last adjustment. +* **Rotate** – A live preview is shown immediately, and the rotation is then saved back to the image attribute. +* **Reset** – The original image is restored and zoom, rotation, and grayscale are cleared. A reset is not saved as a crop and does not trigger the **On crop** action. ## Styling @@ -163,4 +163,4 @@ The widget is shipped with default styles and works out of the box without Atlas ## Read More -- [Image](/appstore/widgets/image/) +* [Image](/appstore/widgets/image/) diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0207.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0207.md index a82fee1b458..15b0e9a8d64 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0207.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0207.md @@ -68,4 +68,4 @@ For more information on how Private Mendix Platform manages dynamic roles and gr {{< figure src="/attachments/private-platform/nist-ac/nist-ac-0207-3.png" class="no-border" >}} -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0207-4.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0207-4.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac06.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac06.md index 223c425e271..c27fabdad29 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac06.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac06.md @@ -179,4 +179,4 @@ Kubernetes privilege credentials are removed from the build configuration. ### Private Mendix Plaform Roles -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-06-5.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-06-5.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1101.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1101.md index a957a66b5de..e0d23769344 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1101.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1101.md @@ -51,4 +51,4 @@ After the time specified in the **Maximum duration before session lock time** se For information about implementing the function in your Mendix apps by building a widget which runs a JavaScript snippet with idle detection API, refer to the following topics: * [Idle Detection API](https://developer.mozilla.org/en-US/docs/Web/API/Idle_Detection_API) -* [Pluggable Widgets API](/apidocs-mxsdk/apidocs/pluggable-widgets-10/) \ No newline at end of file +* [Pluggable Widgets API](/apidocs-mxsdk/apidocs/pluggable-widgets-10/) diff --git a/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca05.md b/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca05.md index 70837ba7ec1..22d7e28ee66 100644 --- a/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca05.md +++ b/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca05.md @@ -107,4 +107,4 @@ The customer is responsible for developing, maintaining, and executing the overa Mendix is responsible for publishing timely security advisories and providing patched releases for Mendix platform components. -Infrastructure and Application Implementers and Operators are responsible for implementing specific remedial actions within their respective domains as directed by the customer's POAM. \ No newline at end of file +Infrastructure and Application Implementers and Operators are responsible for implementing specific remedial actions within their respective domains as directed by the customer's POAM. diff --git a/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca07.md b/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca07.md index 192e45c9107..80bf7624a16 100644 --- a/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca07.md +++ b/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca07.md @@ -84,4 +84,4 @@ To meet these requirements, the customer must carry out the following actions: 3. Maintain ongoing monitoring and reporting. - The Infra Operator and App Operator must ensure that the infrastructure and Mendix App remain in compliance with the customer's continuous monitoring program as it evolves. This includes performing regular security control assessments, correlating and analyzing security-related information, generating compliance reports, and executing response actions to address identified risks per OMB Memorandum 11-33. \ No newline at end of file + The Infra Operator and App Operator must ensure that the infrastructure and Mendix App remain in compliance with the customer's continuous monitoring program as it evolves. This includes performing regular security control assessments, correlating and analyzing security-related information, generating compliance reports, and executing response actions to address identified risks per OMB Memorandum 11-33. diff --git a/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca09.md b/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca09.md index 23d1976dd47..e498ae579aa 100644 --- a/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca09.md +++ b/content/en/docs/private-platform/nist-controls/ca/pmp-nist-ca09.md @@ -67,4 +67,4 @@ To meet these requirements, the customer must carry out the following actions: 3. Maintain connection documentation over lifecycle. - The Infra Operator and App Operator must ensure that these internal connections and the associated documentation stay current over the lifecycle of the solution. This includes performing periodic reviews of authorized connections, updating documentation when connections change, and removing or re-authorizing connections as the system evolves. \ No newline at end of file + The Infra Operator and App Operator must ensure that these internal connections and the associated documentation stay current over the lifecycle of the solution. This includes performing periodic reviews of authorized connections, updating documentation when connections change, and removing or re-authorizing connections as the system evolves. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm04.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm04.md index fe427d43b65..4c1fe07988f 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm04.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm04.md @@ -119,4 +119,4 @@ The App Operator must perform the following tasks: * Before applying Mendix application updates, analyze the potential security impacts by reviewing change documentation, dependency updates, and Mendix release notes against the current application security configuration. * Document the results of security impact assessments and report findings to the customer for review and approval before implementing application changes. -* Test application changes in separate environments to validate that security controls remain effective and that no new vulnerabilities are introduced before promoting to production. \ No newline at end of file +* Test application changes in separate environments to validate that security controls remain effective and that no new vulnerabilities are introduced before promoting to production. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm05.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm05.md index f06ba810deb..be580621e66 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm05.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm05.md @@ -27,6 +27,7 @@ Any changes to the hardware, software, or firmware components of information sys Organizations maintain records of access to ensure that configuration change control is implemented and to support after-the-fact actions should organizations discover any unauthorized changes. Access restrictions for change also include software libraries. Examples of access restrictions include the following: + * Physical and logical access controls (for example, AC-03 and PE-03) * Workflow automation * Media libraries @@ -63,4 +64,4 @@ To meet these requirements, the customer must carry out the following actions: 3. Maintain change access records and audit trails. - The customer must maintain records of all access granted for change purposes and periodically review these records to detect unauthorized changes. This includes implementing audit logging for all configuration change activities, conducting regular reviews of change access permissions, and enforcing separation of duties as required by PE-03 physical protection requirements. \ No newline at end of file + The customer must maintain records of all access granted for change purposes and periodically review these records to detect unauthorized changes. This includes implementing audit logging for all configuration change activities, conducting regular reviews of change access permissions, and enforcing separation of duties as required by PE-03 physical protection requirements. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0505.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0505.md index 80f1897c864..e2e6da002d9 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0505.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0505.md @@ -19,6 +19,7 @@ This document describes how Private Mendix Platform fulfills the CM-05 (05) cont ## Control The organization: + * Limits privileges to change information system components and system-related information within a production or operational environment. * Reviews and reevaluates privileges at an organization-defined frequency. @@ -132,4 +133,4 @@ Users with the Contributor role can only contribute to the app, but they cannot {{< figure src="/attachments/private-platform/nist-cm/nist-cm-0505-3.png" class="no-border" >}} -For more information, see [Dynamic Role Management in Private Mendix Platform](/private-mendix-platform/dynamic-role-management/). \ No newline at end of file +For more information, see [Dynamic Role Management in Private Mendix Platform](/private-mendix-platform/dynamic-role-management/). diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0506.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0506.md index a6807a56b23..78ab395fa9b 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0506.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0506.md @@ -52,4 +52,4 @@ To meet these requirements, the customer must carry out the following actions: 3. Review and audit library access privileges. - The customer must periodically review and audit access privileges to software libraries to ensure compliance with the defined policies. This includes maintaining records of who has write access to software libraries, reviewing privilege assignments at organization-defined frequencies, and revoking unnecessary access in alignment with least privilege principles, as described in NIST SP 800-53 AC-06. \ No newline at end of file + The customer must periodically review and audit access privileges to software libraries to ensure compliance with the defined policies. This includes maintaining records of who has write access to software libraries, reviewing privilege assignments at organization-defined frequencies, and revoking unnecessary access in alignment with least privilege principles, as described in NIST SP 800-53 AC-06. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm06.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm06.md index 12c75e3b0ba..dc017a5eac2 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm06.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm06.md @@ -146,4 +146,4 @@ The App Operator must perform the following tasks: * Implement monitoring to detect deviations from established application security configuration settings and alert on unauthorized changes. * Ensure all changes to application configuration settings follow the organization's change control process and are approved before implementation. -* Provide regular application configuration compliance reports to the customer, including any deviations detected and remediation actions taken. \ No newline at end of file +* Provide regular application configuration compliance reports to the customer, including any deviations detected and remediation actions taken. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0801.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0801.md index a84cd8a0870..401e45b627e 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0801.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0801.md @@ -90,4 +90,4 @@ For more information, refer to the following: * [Mendix on Kubernetes Release Notes](/releasenotes/developer-portal/mendix-for-private-cloud/) * [LTS, MTS, and Monthly Releases](/releasenotes/studio-pro/lts-mts/) * [Private Mendix Platform Release Notes](/releasenotes/private-platform/) -* [SBOM Generation](/refguide/sbom-generation/) \ No newline at end of file +* [SBOM Generation](/refguide/sbom-generation/) diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0507.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0507.md index e7d432fde72..0c8cb1ea48f 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0507.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0507.md @@ -59,4 +59,4 @@ Selecting Azure Key Vault as the secret provider: Selecting HashiCorp Vault as the secret provider: -{{< figure src="/attachments/private-platform/nist-ia/nist-ia-0507-4.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ia/nist-ia-0507-4.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0511.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0511.md index f7c1a5430db..37fccc5245a 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0511.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0511.md @@ -64,4 +64,4 @@ IdP SAML configuration in Private Mendix Platform: {{< figure src="/attachments/private-platform/nist-ia/nist-ia-08-3.png" class="no-border" >}} -For more information about hardware token-based authentication IdP bonding, see [What is Microsoft Entra certificate-based authentication?](https://learn.microsoft.com/en-us/entra/identity/authentication/concept-certificate-based-authentication). \ No newline at end of file +For more information about hardware token-based authentication IdP bonding, see [What is Microsoft Entra certificate-based authentication?](https://learn.microsoft.com/en-us/entra/identity/authentication/concept-certificate-based-authentication). diff --git a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir06.md b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir06.md index 4204f520591..57aa78da26b 100644 --- a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir06.md +++ b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir06.md @@ -61,4 +61,4 @@ It is the responsibility of the Customer, Infra Implementer, App Implementer, In Mendix meets or exceeds US Federal Regulations around CVE remediation times. See our Vulnerability Management policy in [Conveyor](https://app.conveyor.com/profile/mendix) for more information. -{{< figure src="/attachments/private-platform/nist-ir/nist-ir-06-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ir/nist-ir-06-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0602.md b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0602.md index bac2d45bbed..561367aa7a9 100644 --- a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0602.md +++ b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0602.md @@ -44,4 +44,4 @@ It is the responsibility of the Infra Implementer, App Implementer, Infra Operat ## Proof and Remarks -Details about the Mendix security incident response are available in Section IV of the SOC-2 report in Conveyor. \ No newline at end of file +Details about the Mendix security incident response are available in Section IV of the SOC-2 report in Conveyor. diff --git a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma01.md b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma01.md index 78b354cf5de..86d84c104a9 100644 --- a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma01.md +++ b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma01.md @@ -56,4 +56,4 @@ This is not a Mendix responsibility. It is the responsibility of the customer to It is the responsibility of the Infra Implementer to ensure that the infrastructure and Private Mendix Platform is implemented in such a way that they comply with and support the customer's system maintenance policy and procedures. It is the responsibility of the App Implementer to ensure that the Mendix App is implemented in such a way that it complies with and supports the customer's system maintenance policy and procedures. -It is the responsibility of the Infra Operator and App Operator to perform maintenance and updates in such a way that they ensure ongoing compliance with the customer's system maintenance policy and procedures. \ No newline at end of file +It is the responsibility of the Infra Operator and App Operator to perform maintenance and updates in such a way that they ensure ongoing compliance with the customer's system maintenance policy and procedures. diff --git a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma02.md b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma02.md index 9d191c97de7..ba62fe95b6f 100644 --- a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma02.md +++ b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma02.md @@ -67,4 +67,4 @@ It is the customer's responsibility to provide maintenance policies and procedur It is the responsibility of the Infra Operator to perform maintenance on the infrastructure and Private Mendix Platform in compliance with the customer's maintenance policies. -It is the responsibility of the App Operator to perform maintenance on the Mendix app in compliance with the customer's maintenance policies. \ No newline at end of file +It is the responsibility of the App Operator to perform maintenance on the Mendix app in compliance with the customer's maintenance policies. diff --git a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0402.md b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0402.md index e0c9cbb4e1f..77274e066a7 100644 --- a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0402.md +++ b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0402.md @@ -32,4 +32,4 @@ The documentation of the security plan for the Mendix solution, including consid This is not a Mendix responsibility. It is the responsibility of the customer to document the security plan for the Mendix solution in collaboration with the Infra Implementer and the App Implementer, including considering how to perform local and non-local maintenance. -It is the responsibility of the Infra Operator and App Operator to perform their tasks in compliance with the customer's security plan for the Mendix solution. \ No newline at end of file +It is the responsibility of the Infra Operator and App Operator to perform their tasks in compliance with the customer's security plan for the Mendix solution. diff --git a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0403.md b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0403.md index 3a9b322ce84..d4293e6d106 100644 --- a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0403.md +++ b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0403.md @@ -48,4 +48,4 @@ Additionally, the customer's Infra and App Operators must ensure adherence with This is not a Mendix responsibility. It is the responsibility of the customer to defined the required external maintenance capabilities, as well as ensuring that non-local maintenance systems are compliant. -It is the responsibility of the Infra Operator and App Operator to respect the customer's requirements and only use approved tools and systems when completing non-local maintenance, and complying with customer dictated component removal policies and procedures before, during, and after any non-local service. \ No newline at end of file +It is the responsibility of the Infra Operator and App Operator to respect the customer's requirements and only use approved tools and systems when completing non-local maintenance, and complying with customer dictated component removal policies and procedures before, during, and after any non-local service. diff --git a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0501.md b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0501.md index 843246858e9..ac374205d9a 100644 --- a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0501.md +++ b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma0501.md @@ -60,4 +60,4 @@ This is not a Mendix responsibility, except in cases where direct product suppor ## Proof and Remarks -For more information, see [Dynamic Role Management in Private Mendix Platform](/private-mendix-platform/dynamic-role-management/). \ No newline at end of file +For more information, see [Dynamic Role Management in Private Mendix Platform](/private-mendix-platform/dynamic-role-management/). diff --git a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma06.md b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma06.md index cd62a7dd5c0..f8143135ae2 100644 --- a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma06.md +++ b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma06.md @@ -48,4 +48,4 @@ It is the responsibility of the customer to source maintenance and parts as well It is the responsibility of the Infra Operator and App Operator to perform maintenance and support of the Mendix solution in compliance with the Customer’s directives and according to applicable contracts and laws. -This is not a Mendix responsibility beyond providing support for the Mendix products sold as is outline in the license terms and other agreements. \ No newline at end of file +This is not a Mendix responsibility beyond providing support for the Mendix products sold as is outline in the license terms and other agreements. diff --git a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp01.md b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp01.md index 0d4940b7e94..760816c9a6c 100644 --- a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp01.md +++ b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp01.md @@ -62,4 +62,4 @@ It is the responsibility of the Infra Implementer to ensure the infrastructure a It is the responsibility of the App Implementer to ensure that the Mendix app is implemented in a way that is in compliance with, and supporting of, the customer's media protection policy. -It is the responsibility of the Infra Operator and App Operator to ensure ongoing compliance of the Mendix solution throughout its lifecycle. \ No newline at end of file +It is the responsibility of the Infra Operator and App Operator to ensure ongoing compliance of the Mendix solution throughout its lifecycle. diff --git a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp02.md b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp02.md index d28c5c8ce92..ef85535f9e6 100644 --- a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp02.md +++ b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp02.md @@ -53,4 +53,4 @@ It is the responsibility of the Infra Implementer to ensure that the infrastruct It is the responsibility of the App Implementer to ensure that the Mendix app properly implements media restrictions in compliance with the customer's directives. -It is the responsibility of the Infra Operator and App Operator to ensure ongoing compliance with the customer's media restriction directives throughout the lifecycle of the Mendix solution. \ No newline at end of file +It is the responsibility of the Infra Operator and App Operator to ensure ongoing compliance with the customer's media restriction directives throughout the lifecycle of the Mendix solution. diff --git a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp03.md b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp03.md index fddfd5a32b5..516520bb607 100644 --- a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp03.md +++ b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp03.md @@ -57,4 +57,4 @@ It is the responsibility of the Infra Implementer to ensure the infrastructure p It is the responsibility of the App Implementer to ensure the Mendix app marks media and provides media marking exemptions in compliance with the customer's directives. -it is the responsibility of the Infra Operator and the App Operator to ensure ongoing compliance with media marking and exemptions as directed by the customer over the lifecycle of the Mendix solution. \ No newline at end of file +it is the responsibility of the Infra Operator and the App Operator to ensure ongoing compliance with media marking and exemptions as directed by the customer over the lifecycle of the Mendix solution. diff --git a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp04.md b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp04.md index c035d81acae..a24b157409b 100644 --- a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp04.md +++ b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp04.md @@ -61,4 +61,4 @@ It is the responsibility of the Infra Implementer to ensure that the infrastruct It is the responsibility of the App Implementer to ensure that the media associated with the Mendix app complies with the customer's media security and lifecycle policies. -It is the responsibility of the Infra Operator and App Operator to ensure that the Mendix solution's media continues to comply with the customer's media security and lifecycle policies through the lifecycle of the Mendix solution. \ No newline at end of file +It is the responsibility of the Infra Operator and App Operator to ensure that the Mendix solution's media continues to comply with the customer's media security and lifecycle policies through the lifecycle of the Mendix solution. diff --git a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp05.md b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp05.md index f4140a1cac0..a796a1983b7 100644 --- a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp05.md +++ b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp05.md @@ -62,4 +62,4 @@ The responsibility for ensuring proper media controls and sanitization of data b ### Customer Responsibility -This is not a Mendix responsibility. It is the responsibility of the customer, Infra Implementer, App Implementer, Infra Operator, and App Operator to ensure proper media controls and scrubbing of data before transporting that data to Mendix for the purposes of providing product support. \ No newline at end of file +This is not a Mendix responsibility. It is the responsibility of the customer, Infra Implementer, App Implementer, Infra Operator, and App Operator to ensure proper media controls and scrubbing of data before transporting that data to Mendix for the purposes of providing product support. diff --git a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp0504.md b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp0504.md index 3762f2a1ce6..53734b8e6c5 100644 --- a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp0504.md +++ b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp0504.md @@ -55,4 +55,4 @@ While the Mendix Runtime provides the capability for encryption at rest, the ove Additionally, mobile device encryption at rest is supported (Apple and Android), as well as custom file-storage encryption. For more information, refer to the following topics: * [Offline Data Security: Local Data Safety](/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/local-data-security/#local-data-safety) -* [Updating Encryption Keys for S3 File Storage](/refguide/s3-encryption-key-update/) \ No newline at end of file +* [Updating Encryption Keys for S3 File Storage](/refguide/s3-encryption-key-update/) diff --git a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp07.md b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp07.md index 59f7666520d..99375a07dfc 100644 --- a/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp07.md +++ b/content/en/docs/private-platform/nist-controls/mp/pmp-nist-mp07.md @@ -59,4 +59,4 @@ It is the responsibility of the Infra Implementer to ensure the infrastructure c It is the responsibility of the App Implementer to ensure the Mendix app complies with the customer's media restrictions and safeguards. -It is the responsibility of the Infra Operator and App Operator to ensure the Mendix solution complies with the customer's media restrictions and safeguards throughout the system's lifecycle. \ No newline at end of file +It is the responsibility of the Infra Operator and App Operator to ensure the Mendix solution complies with the customer's media restrictions and safeguards throughout the system's lifecycle. diff --git a/content/en/docs/private-platform/nist-controls/pe/pmp-nist-pe0301.md b/content/en/docs/private-platform/nist-controls/pe/pmp-nist-pe0301.md index df9430efbc7..6baaffe87d1 100644 --- a/content/en/docs/private-platform/nist-controls/pe/pmp-nist-pe0301.md +++ b/content/en/docs/private-platform/nist-controls/pe/pmp-nist-pe0301.md @@ -54,4 +54,4 @@ Private Mendix Platform provides the integration points (OIDC, SAML) to connect Specific Mendix applications can be configured to connect to the customer's IdP by the App Implementer or Operator by using [OIDC SSO](/appstore/modules/oidc/) or [SAML](/appstore/modules/saml/), both of which allow for physical authentication mechanisms through the customer's IdP. -Additionally, it is possible to configure biometric authentication directly on native mobile applications (Apple and Android) using the [Native Mobile Resources](/appstore/modules/native-mobile-resources/#native-authentication-category) module. The module is platform-supported, that is, supported by Mendix. \ No newline at end of file +Additionally, it is possible to configure biometric authentication directly on native mobile applications (Apple and Android) using the [Native Mobile Resources](/appstore/modules/native-mobile-resources/#native-authentication-category) module. The module is platform-supported, that is, supported by Mendix. diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc28.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc28.md index 7346c693ec9..7d68d897dc9 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc28.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc28.md @@ -173,4 +173,4 @@ The Mendix Runtime provides the [EnableFileDocumentCaching](/refguide/custom-set ### SC-28 (01) - FIPS Mode: AES-256 and FIPS 140-2 Validated Cryptography -The sibling control SC-28 (01) documents the cryptographic protection mechanisms available in Private Mendix Platform, including support for FIPS 140-2 validated modules when deployed in FIPS mode. Private Mendix Platform supports FIPS-compliant deployments on supported Kubernetes distributions, ensuring that AES-256 is used for data at rest. \ No newline at end of file +The sibling control SC-28 (01) documents the cryptographic protection mechanisms available in Private Mendix Platform, including support for FIPS 140-2 validated modules when deployed in FIPS mode. Private Mendix Platform supports FIPS-compliant deployments on supported Kubernetes distributions, ensuring that AES-256 is used for data at rest. diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2801.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2801.md index ad7e31339c7..13f132805d0 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2801.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2801.md @@ -141,6 +141,7 @@ The Mendix Operator supports externalizing environment-level secrets (database c with each provider's native cryptographic mechanisms at rest. The following stores are supported: + * HashiCorp Vault * AWS Secrets Manager * Azure Key Vault @@ -205,4 +206,4 @@ For more information, see [Containerized Mendix App Architecture](/developerport As described in the [January 26, 2026 release note](/releasenotes/developer-portal/mendix-for-private-cloud/#0.10.7), License Manager CLI v0.10.7 and newer automatically disables API credential automounting for PCLM deployments, significantly limiting unnecessary access. -The Operator actively enforces that pods cannot acquire Kubernetes API credentials at runtime, closing the path by which a compromised pod could query the API server to discover and target other pods. \ No newline at end of file +The Operator actively enforces that pods cannot acquire Kubernetes API credentials at runtime, closing the path by which a compromised pod could query the API server to discover and target other pods. diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc39.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc39.md index d9eb785b63f..093123bd6dd 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc39.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc39.md @@ -121,4 +121,4 @@ For more information about port 8900 of the Mendix App Sidecar, see the followin * [Enable Metrics Scraping](/developerportal/deploy/private-cloud-monitor/#enable-metrics-scraping ) * [Customize Liveness Probe to Resolve Crash Loopback Scenarios](/developerportal/deploy/private-cloud-cluster/#customize-liveness) -For more information about port 8080 of the Mendix App Runtime container, see [Firewall Settings](/refguide/system-requirements/#firewall-settings). \ No newline at end of file +For more information about port 8080 of the Mendix App Runtime container, see [Firewall Settings](/refguide/system-requirements/#firewall-settings). diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si02.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si02.md index 6c42c125b4a..7b7efb7f7ce 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si02.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si02.md @@ -68,4 +68,4 @@ Mendix maintains a documented update and release cycle for its products (Runtime * [Studio Pro](/releasenotes/studio-pro/) * [Private Mendix Platform](/releasenotes/private-platform/) - * [Mendix Operator and Mendix on Kubernetes](/releasenotes/developer-portal/mendix-for-private-cloud/) \ No newline at end of file + * [Mendix Operator and Mendix on Kubernetes](/releasenotes/developer-portal/mendix-for-private-cloud/) diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0203.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0203.md index fe03d8510b2..0ff6775a1ea 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0203.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0203.md @@ -108,4 +108,4 @@ Long-Term Support (LTS) versions receive patch releases for bug and security fix Medium-Term Support (MTS) versions receive patch releases for bug and security fixes. Support ends three months after the next major version releases. For more information, see [Medium-Term Support Version (MTS)](/releasenotes/studio-pro/lts-mts/#mts). -For information about the current supported versions and dates, refer to the [version support table](/releasenotes/studio-pro/lts-mts/#types-of-support). \ No newline at end of file +For information about the current supported versions and dates, refer to the [version support table](/releasenotes/studio-pro/lts-mts/#types-of-support). diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0206.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0206.md index ce1526737f9..0a11d10a154 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0206.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0206.md @@ -67,4 +67,4 @@ Helm is the package manager for Kubernetes which handles the deployment and mana {{< figure src="/attachments/private-platform/nist-si/nist-si-0206-1.png" class="no-border" >}} -{{< figure src="/attachments/private-platform/nist-si/nist-si-0206-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-si/nist-si-0206-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0307.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0307.md index 37c0ffa0c6c..6c28c79225e 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0307.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0307.md @@ -101,7 +101,6 @@ For more information, see [Read-only RootFS](/developerportal/deploy/private-clo The Private Mendix Platform operator sets `automountServiceAccountToken: false` on Mendix app pods by default: - * *`runtimeAutomountServiceAccountToken` - Specify if Mendix app pods should get a Kubernetes Service Account token; defaults to false* Disabling token automounting prevents a compromised container from using the Kubernetes API to perform lateral movement - a common behavior-based attack vector. Any API calls from a Private Mendix Platform app pod are therefore anomalous and detectable without needing a signature for the specific malware. diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0310.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0310.md index c8cde3b5e6c..b6810e5b6a5 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0310.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0310.md @@ -57,4 +57,4 @@ The customer is responsible for establishing malicious code analysis capabilitie * Infra Implementer - Build malware analysis tools into the infrastructure as directed by the customer. * Infra Operator - Ensure ongoing compliance and support the Customer in using the selected tools. -* Security team - Analyze malware samples and incorporate findings into security processes. \ No newline at end of file +* Security team - Analyze malware samples and incorporate findings into security processes. diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0412.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0412.md index 4be7590d0a4..bdf58674f35 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0412.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0412.md @@ -42,4 +42,4 @@ Infrastructure and Application Implementers implement alert triggers in accordan #### Infrastructure and Application Operators -Infrastructure and Application Operators ensure that alerting mechanisms continue to function as expected and that security alerts generated by infrastructure components and Mendix applications are reliably delivered and actionable. \ No newline at end of file +Infrastructure and Application Operators ensure that alerting mechanisms continue to function as expected and that security alerts generated by infrastructure components and Mendix applications are reliably delivered and actionable. diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0416.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0416.md index 877930a7295..c7e350d1dfc 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0416.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0416.md @@ -36,4 +36,4 @@ This is not a Mendix responsibility. It is the customer's responsibility to ensu The customer is responsible for correlating monitoring information across multiple sources to enable effective detection and analysis of security‑relevant events. This includes logs and metrics from Mendix Operator components, the Private Mendix Platform, Mendix Runtime applications, Kubernetes cluster monitoring (such as pod metrics, events, and resource utilization), infrastructure monitoring systems, and security monitoring tools including IDS/IPS, firewall logs, and endpoint detection solutions. -Correlation of monitoring data is implemented through centralized logging and analysis capabilities, such as SIEM solutions or log aggregation platforms, to aggregate and analyze data from disparate sources. Correlation rules and dashboards are configured to identify attack patterns and provide consolidated visibility across monitoring domains, supporting timely detection, investigation, and response to potential security incidents. \ No newline at end of file +Correlation of monitoring data is implemented through centralized logging and analysis capabilities, such as SIEM solutions or log aggregation platforms, to aggregate and analyze data from disparate sources. Correlation rules and dashboards are configured to identify attack patterns and provide consolidated visibility across monitoring domains, supporting timely detection, investigation, and response to potential security incidents. diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0419.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0419.md index 1787c9aa077..ca6255ee567 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0419.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0419.md @@ -42,4 +42,4 @@ Infrastructure and Application Implementers ensure that additional monitoring ca #### Infrastructure and Application Operators -Infrastructure and Application Operators apply additional monitoring to identified individuals as directed by the customer. Centralized logging of Mendix component activities is used to support monitoring, review, and analysis of elevated‑risk user behavior. \ No newline at end of file +Infrastructure and Application Operators apply additional monitoring to identified individuals as directed by the customer. Centralized logging of Mendix component activities is used to support monitoring, review, and analysis of elevated‑risk user behavior. diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0420.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0420.md index b5d4afd1e8b..0117347959d 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0420.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0420.md @@ -38,4 +38,4 @@ The customer is responsible for defining additional monitoring requirements for #### Infrastructure and Application Implementers -Infrastructure and Application Implementers implement Customer‑defined privileged user monitoring controls at their respective layers, including infrastructure‑level logging for administrative actions and application‑level monitoring within Mendix applications. Mendix does not provide a dedicated audit logging system. Organizations rely on Kubernetes‑provided logging capabilities and integrations with external logging and monitoring solutions to support privileged user activity monitoring. \ No newline at end of file +Infrastructure and Application Implementers implement Customer‑defined privileged user monitoring controls at their respective layers, including infrastructure‑level logging for administrative actions and application‑level monitoring within Mendix applications. Mendix does not provide a dedicated audit logging system. Organizations rely on Kubernetes‑provided logging capabilities and integrations with external logging and monitoring solutions to support privileged user activity monitoring. diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si06.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si06.md index c8c458d0fb1..533f0c2c1bd 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si06.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si06.md @@ -55,4 +55,4 @@ This is not a Mendix responsibility. It is the responsibility of the customer to The customer is responsible for defining and maintaining procedures to verify the integrity and correct operation of security functions within the Mendix solution, ensuring that verification is performed at system startup, during security‑relevant events, and at defined periodic intervals in accordance with SI‑07 and SI‑07 (01). These procedures establish which security functions (such as authentication, authorization, encryption, logging, and intrusion detection) are subject to verification, who is authorized to perform verification activities, and how verification results are monitored. -The customer also defines notification and response actions for failed integrity or security function checks, including alerting, restart, or shutdown as appropriate, while Infrastructure and Application Implementers and Operators enable, execute, and respond to verification activities within their respective infrastructure and application responsibilities. \ No newline at end of file +The customer also defines notification and response actions for failed integrity or security function checks, including alerting, restart, or shutdown as appropriate, while Infrastructure and Application Implementers and Operators enable, execute, and respond to verification activities within their respective infrastructure and application responsibilities. diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0701.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0701.md index 4c02cef384c..b4ceb2352ec 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0701.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si0701.md @@ -44,4 +44,4 @@ The customer is responsible for defining the scope, frequency, and mechanisms fo The customer is responsible for defining the scope and execution of integrity verification activities in accordance with organizational security policies and risk management objectives. This includes identifying the software, firmware, and information subject to integrity checks; determining when such checks are performed (for example, at system startup, on demand, or at defined intervals); selecting appropriate integrity verification mechanisms such as cryptographic checksums or digital signatures; and establishing procedures for investigation, notification, and remediation when integrity violations are detected. -Infra Implementers and Operators support the customer-defined requirements by executing and maintaining the integrity verification mechanisms within the environment. The Infrastructure Implementer is responsible for implementing integrity checks for infrastructure components and container images, while the Application Implementer applies integrity controls to application code and dependencies as required. The Infrastructure Operator and Application Operator are responsible for monitoring integrity check results, responding to detected failures, and ensuring continued operation of integrity monitoring in alignment with customer-defined procedures. \ No newline at end of file +Infra Implementers and Operators support the customer-defined requirements by executing and maintaining the integrity verification mechanisms within the environment. The Infrastructure Implementer is responsible for implementing integrity checks for infrastructure components and container images, while the Application Implementer applies integrity controls to application code and dependencies as required. The Infrastructure Operator and Application Operator are responsible for monitoring integrity check results, responding to detected failures, and ensuring continued operation of integrity monitoring in alignment with customer-defined procedures. diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si10.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si10.md index 4d621e5fa80..fa0f03ba955 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si10.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si10.md @@ -58,4 +58,4 @@ Entity-level validation rules are editable in the domain model in Studio Pro. {{< figure src="/attachments/private-platform/nist-si/nist-si-10-1.png" class="no-border" >}} -For more information, see [Setting Up Data Validation: Data Validation on Entity Level](/refguide/setting-up-data-validation/#data-validation-on-entity-level). \ No newline at end of file +For more information, see [Setting Up Data Validation: Data Validation on Entity Level](/refguide/setting-up-data-validation/#data-validation-on-entity-level). diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si1003.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si1003.md index 16873da6fd3..64f2cefd436 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si1003.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si1003.md @@ -64,4 +64,4 @@ Example entity‑level input validation configured in Mendix Studio Pro, where v UI input validation on pages in Mendix Studio Pro using required fields and validation messages: -{{< figure src="/attachments/private-platform/nist-si/nist-si-1003-5.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-si/nist-si-1003-5.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si11.md b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si11.md index 6ea20973cbb..8ab7e2ed680 100644 --- a/content/en/docs/private-platform/nist-controls/si/pmp-nist-si11.md +++ b/content/en/docs/private-platform/nist-controls/si/pmp-nist-si11.md @@ -69,4 +69,4 @@ Evidence of compliance: * Detailed error information is available only in logs accessible to privileged users - {{< figure src="/attachments/private-platform/nist-si/nist-si-11-2.png" class="no-border" >}} \ No newline at end of file + {{< figure src="/attachments/private-platform/nist-si/nist-si-11-2.png" class="no-border" >}} diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/_index.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/_index.md index 801fb947fd2..661f77cb1e7 100644 --- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/_index.md +++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/_index.md @@ -56,7 +56,6 @@ The following table lists Maia Make Standalone Capabilities and the Studio Pro v | [Maia Agent Skills](/refguide/maia-agent-skills/) | Extends Maia with reusable knowledge. | Studio Pro 11.11 | | | [Maia Agent Instructions](/refguide/maia-instructions/) | Extends Maia with instructions to be followed with every prompt | Studio Pro 11.12 | | - ### Maia Make General Capabilities The following table lists the general capabilities of Maia Make and the Studio Pro version in which support for each capability was introduced: diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-skills.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-skills.md index 1aec546f736..1396bf50eab 100644 --- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-skills.md +++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-skills.md @@ -30,7 +30,6 @@ Agents skills are not supported for Add-on and Solution modules. For guidance on writing effective skills, see [Best Practices for Skill Creators](https://agentskills.io/skill-creation/best-practices) and [Optimizing Skill Descriptions](https://agentskills.io/skill-creation/optimizing-descriptions) in the [Agent Skills documentation](https://agentskills.io/). - ## Creating an Agent Skill {#creating-a-skill} To create a new agent skill in Studio Pro, follow these steps: @@ -122,7 +121,6 @@ successfully, including any error message, references found, and the module the {{< figure src="/attachments/refguide/mendix-ai-assistance/maia-make/maia-agent-skills/skills-pane.png" width="400px">}} - Updates to skills, whether you add a new skill or change an existing one, appear only after you start a new session. To apply the updated skills immediately, click the **Sync** button in the **Skills** pane. diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-instructions.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-instructions.md index 625f9e32f9a..81348f43906 100644 --- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-instructions.md +++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-instructions.md @@ -55,6 +55,6 @@ Project-level instructions are stored as `skillssource/AGENTS.md`, while module- ## Read More -- [Agent Skills](/refguide/maia-agent-skills/) -- [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/) -- [Maia Chat](/refguide/maia-chat/) \ No newline at end of file +* [Agent Skills](/refguide/maia-agent-skills/) +* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/) +* [Maia Chat](/refguide/maia-chat/) diff --git a/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/native-styling-element-guide.md b/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/native-styling-element-guide.md index 1a0a4bf8ffb..6e69940f930 100644 --- a/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/native-styling-element-guide.md +++ b/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/native-styling-element-guide.md @@ -376,7 +376,6 @@ The default class to style all text areas is named `TextArea`. A drop-down is an input widget that can be used to display and edit enumeration attributes. - ```javascript export const DropDown = { container: { diff --git a/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/navigation/native-navigation.md b/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/navigation/native-navigation.md index 6944d447815..d9d3f6cf673 100644 --- a/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/navigation/native-navigation.md +++ b/content/en/docs/refguide/mobile/designing-mobile-user-interfaces/navigation/native-navigation.md @@ -32,6 +32,7 @@ To achieve these native performance gains, we can no longer support certain Java ## Known Issues Please be aware of a known issue where the top **10-15 pixels** of the screen content directly below the header may be unresponsive to touch events: + * Cause: This occurs because the native header has a higher view hierarchy (z-index) than the JavaScript-based UI elements rendered below it. * Workaround: Most apps already include top padding on their pages, which avoids this issue. We recommend ensuring your page content has adequate padding below the header. -* Planned solution: We are developing a native button widget that will resolve this edge case. These will be released in a future update. \ No newline at end of file +* Planned solution: We are developing a native button widget that will resolve this edge case. These will be released in a future update. diff --git a/content/en/docs/refguide/mobile/distributing-mobile-apps/building-native-apps/build-mendix-native-appcircle.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/building-native-apps/build-mendix-native-appcircle.md index 1922a121f1e..052579578d0 100644 --- a/content/en/docs/refguide/mobile/distributing-mobile-apps/building-native-apps/build-mendix-native-appcircle.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/building-native-apps/build-mendix-native-appcircle.md @@ -73,10 +73,10 @@ To add a provisioning profile, do the following: In the **Build** module, open the iOS build profile and go to **Build Configuration**. Under the **Signing** section, choose one of the following signing methods: * **Automatic Signing** — Appcircle automatically handles provisioning profile management during the build. This process requires the following prerequisites be met: - * Xcode 13 or above - * A **Developer** or **Distribution** certificate - * An **App Store Connect API key** (configured in the **API Integrations** settings) - * The bundle identifier must already be registered in your Apple Developer account + * Xcode 13 or above + * A **Developer** or **Distribution** certificate + * An **App Store Connect API key** (configured in the **API Integrations** settings) + * The bundle identifier must already be registered in your Apple Developer account * **Manual Signing** — You manually select the certificate and provisioning profile for each build configuration. This gives you full control over which profiles are used. Select your bundle identifier from the dropdown, then choose the provisioning profile you added in the **Signing Identities** module. The certificate will be automatically matched based on the profile. {{< figure src="/attachments/refguide/mobile/distributing-mobile-apps/building-native-apps/appcircle/assign-code-signing.png" alt="Repository connection options in Appcircle" class="no-border" >}} diff --git a/content/en/docs/refguide/mobile/distributing-mobile-apps/publish-mendix-native-appcircle.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/publish-mendix-native-appcircle.md index e896eb4d483..683d13fd686 100644 --- a/content/en/docs/refguide/mobile/distributing-mobile-apps/publish-mendix-native-appcircle.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/publish-mendix-native-appcircle.md @@ -102,7 +102,6 @@ For Android, you have two options: {{< figure src="/attachments/refguide/mobile/distributing-mobile-apps/building-native-apps/appcircle/android-profile-create.png" alt="Testing Distribution module in Appcircle" class="no-border" >}} - {{% alert color="warning" %}} The Bundle ID (iOS) and Package Name (Android) cannot be changed after the profile is created. Make sure these are correct before saving. {{% /alert %}} diff --git a/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/_index.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/_index.md index dc825c17624..50959d3f656 100644 --- a/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/_index.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/_index.md @@ -57,4 +57,4 @@ Keep the following limitations in mind: * Platform support varies for individual capabilities, so not every capability behaves the same way on Android and iOS * Some integrations use standard Web APIs, which means behavior can vary between devices, operating system versions, and embedded browser engines -For build-specific constraints, see [Build PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). For capability-specific constraints, see [PWA Wrapper Capabilities](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). \ No newline at end of file +For build-specific constraints, see [Build PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). For capability-specific constraints, see [PWA Wrapper Capabilities](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). diff --git a/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md b/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md index e33a0737418..1ece040e138 100644 --- a/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md +++ b/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md @@ -1439,7 +1439,6 @@ SELECT LPAD('hello', 10) AS padded FROM Sales.Order Where `·` represents the space character. - ```sql SELECT LPAD('hello', 10, 'x') AS padded FROM Sales.Order ``` diff --git a/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/_index.md b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/_index.md index edd0a6469ac..dcb3f2a9b9b 100644 --- a/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/_index.md +++ b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/_index.md @@ -55,4 +55,4 @@ Keep the following beta limitations in mind: * Platform support varies for individual capabilities, so not every capability behaves the same way on Android and iOS * Some integrations use standard Web APIs, which means behavior can vary between devices, operating system versions, and embedded browser engines -For build-specific constraints, see [Build PWA Wrapper Apps](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). For capability-specific constraints, see [PWA Wrapper Capabilities](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). \ No newline at end of file +For build-specific constraints, see [Build PWA Wrapper Apps](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). For capability-specific constraints, see [PWA Wrapper Capabilities](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). diff --git a/content/en/docs/refguide9/version-control/version-control-faq.md b/content/en/docs/refguide9/version-control/version-control-faq.md index 56888e2fdfe..23106906c9e 100644 --- a/content/en/docs/refguide9/version-control/version-control-faq.md +++ b/content/en/docs/refguide9/version-control/version-control-faq.md @@ -15,7 +15,6 @@ Mendix Team Server is based on proven technology. Initially it was based only on Currently, SVN is the default version control system for the Team Server, but you can choose to use Git. In the future, Git will become the default system. - ## How Much Storage Space Is Provided with Team Server? Storage space is unlimited for apps connected to a commercial license. 1 GB of free storage is provided for your company account for apps not (yet) connected to a commercial license. diff --git a/content/en/docs/releasenotes/mobile/make-it-native-parent/_index.md b/content/en/docs/releasenotes/mobile/make-it-native-parent/_index.md index 02e69eaa28d..7d17deeb7b5 100644 --- a/content/en/docs/releasenotes/mobile/make-it-native-parent/_index.md +++ b/content/en/docs/releasenotes/mobile/make-it-native-parent/_index.md @@ -20,4 +20,4 @@ For older version that is compatible with Studio Pro 10 versions, please use cor * For Android - [Make It Native GH releases](https://github.com/mendix/make-it-native/releases) * For iOS - [Test Flight releases](https://apps.apple.com/tr/app/make-it-native/id6450037464) -For versions compatible with older Studio Pro versions, please visit our [GitHub page](https://github.com/mendix/make-it-native#introduction). \ No newline at end of file +For versions compatible with older Studio Pro versions, please visit our [GitHub page](https://github.com/mendix/make-it-native#introduction). diff --git a/content/en/docs/releasenotes/mobile/mendix-native-mobile-builder.md b/content/en/docs/releasenotes/mobile/mendix-native-mobile-builder.md index 100807007e0..d2164d02df4 100644 --- a/content/en/docs/releasenotes/mobile/mendix-native-mobile-builder.md +++ b/content/en/docs/releasenotes/mobile/mendix-native-mobile-builder.md @@ -161,7 +161,6 @@ After these steps, run the installer again. You can start Studio Pro again, and * We resolved an issue where remote JavaScript debugging failed in custom-built Mendix Native Developer Apps. This happened in cases of improper initialization of Firebase services during the build process. Our fix ensures Firebase dependencies are only included when explicitly required by the application. - {{% alert color="warning" %}} Please note that this is a breaking change, and thus, requires a mandatory update. You must use the latest Native Template version to implement this fix, as older versions may cause errors in your application. Failure to update could lead to potential app instability and functionality issues. {{% /alert %}} diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-19-rn.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-19-rn.md index 7480cdff407..b9698a903de 100644 --- a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-19-rn.md +++ b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-19-rn.md @@ -9,7 +9,7 @@ description: "Native Template 19" **Release date: Jul 3, 2026** -- We fixed an issue that could cause iOS apps to restart repeatedly after an OTA update. +* We fixed an issue that could cause iOS apps to restart repeatedly after an OTA update. ## 19.0.5 diff --git a/content/en/docs/releasenotes/private-platform/2.7.md b/content/en/docs/releasenotes/private-platform/2.7.md index fa0a6416948..bee8c0a2122 100644 --- a/content/en/docs/releasenotes/private-platform/2.7.md +++ b/content/en/docs/releasenotes/private-platform/2.7.md @@ -114,4 +114,4 @@ When creating a new installation of Private Mendix Platform, there is an error w ##### Disabled Publish Option -The **Publish** option in Studio Pro is disabled for Private Mendix Platform apps even after the environment is created. This issue will be resolved in an upcoming release. \ No newline at end of file +The **Publish** option in Studio Pro is disabled for Private Mendix Platform apps even after the environment is created. This issue will be resolved in an upcoming release. diff --git a/content/en/docs/releasenotes/sdk/metamodel/metamodel-11/metamodel-11.12.md b/content/en/docs/releasenotes/sdk/metamodel/metamodel-11/metamodel-11.12.md index 42801c50587..e3555b9b35c 100644 --- a/content/en/docs/releasenotes/sdk/metamodel/metamodel-11/metamodel-11.12.md +++ b/content/en/docs/releasenotes/sdk/metamodel/metamodel-11/metamodel-11.12.md @@ -105,4 +105,3 @@ weight: 55 #### Dependency (Element) * We introduced this element. - diff --git a/content/en/docs/releasenotes/studio-pro/10/10.24.md b/content/en/docs/releasenotes/studio-pro/10/10.24.md index 82e5a5b0629..339a90a48f2 100644 --- a/content/en/docs/releasenotes/studio-pro/10/10.24.md +++ b/content/en/docs/releasenotes/studio-pro/10/10.24.md @@ -20,21 +20,21 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for ### Fixes -- We fixed an issue where projects located in a folder whose name contained special characters (for example an '&') would fail to run locally. (Ticket 275109) -- We fixed an issue in React client mode where navigating between pages with the same layout left widgets unresponsive. (Ticket 276710) -- On SQL Server, when a unique constraint or foreign key constraint is dropped, we now use `IF EXISTS`. This avoids an automatic rollback of the synchronization transaction in case the constraint does not exist. (Ticket 279545) -- We fixed an issue where runtime fails to finish executing a queued task started by a user if the user is deleted during task execution. (Ticket 279891) -- We fixed an issue where the native `Switch` widget did not render correctly on iOS. (Ticket 280839) -- We fixed an issue with PWAs using Rspack where the service worker would sometimes not be created correctly. (Ticket 282616, 282601) -- We fixed the `t is not a function` crash in workflow and page editors, introduced by the recent Microsoft update for WebView. If you installed an older version of the Microsoft Edge WebView as a workaround and you have no other affected Studio Pro installations, we recommend uninstalling it to prevent future compatibility issues. (Ticket 282685) -- We fixed an issue in the call web service activity and in consumed OData services that consume services using OData version 3. The XML parser now rejects DTD declarations and external entities, because a compromised server might exploit those features. -- We fixed an issue where pressing Escape to close a modal dialog would also close the sidebar. +* We fixed an issue where projects located in a folder whose name contained special characters (for example an '&') would fail to run locally. (Ticket 275109) +* We fixed an issue in React client mode where navigating between pages with the same layout left widgets unresponsive. (Ticket 276710) +* On SQL Server, when a unique constraint or foreign key constraint is dropped, we now use `IF EXISTS`. This avoids an automatic rollback of the synchronization transaction in case the constraint does not exist. (Ticket 279545) +* We fixed an issue where runtime fails to finish executing a queued task started by a user if the user is deleted during task execution. (Ticket 279891) +* We fixed an issue where the native `Switch` widget did not render correctly on iOS. (Ticket 280839) +* We fixed an issue with PWAs using Rspack where the service worker would sometimes not be created correctly. (Ticket 282616, 282601) +* We fixed the `t is not a function` crash in workflow and page editors, introduced by the recent Microsoft update for WebView. If you installed an older version of the Microsoft Edge WebView as a workaround and you have no other affected Studio Pro installations, we recommend uninstalling it to prevent future compatibility issues. (Ticket 282685) +* We fixed an issue in the call web service activity and in consumed OData services that consume services using OData version 3. The XML parser now rejects DTD declarations and external entities, because a compromised server might exploit those features. +* We fixed an issue where pressing Escape to close a modal dialog would also close the sidebar. ### Deprecations -- We dropped support for the following database versions that are no longer supported by the vendors: - - PostgreSQL 13 - - MariaDB 10.6 +* We dropped support for the following database versions that are no longer supported by the vendors: + * PostgreSQL 13 + * MariaDB 10.6 ## 10.24.22 {#102422} @@ -44,35 +44,35 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for ### Improvements -- We fixed the issue in OData Exists queries where an XPath constraint with nested-associations would result in an incorrect OData filter. (Ticket 261698) -- We updated the .NET Runtime to version 10.0.7. -- We added a confirmation dialog when enabling anonymous user access in App Security, warning that unrestricted anonymous roles may expose data unintentionally. -- We now allow microflow and entity parameters to be optional for Java actions. -- We improved cleanup of queued tasks that are owned by missing nodes. -- Progressive web app (PWA) wrappers are now in GA. This feature allows you to package a PWA as a native app, and is especially useful when you want to keep a web-based application architecture while distributing the app through app stores. For more information, see [PWA Wrapper](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/). +* We fixed the issue in OData Exists queries where an XPath constraint with nested-associations would result in an incorrect OData filter. (Ticket 261698) +* We updated the .NET Runtime to version 10.0.7. +* We added a confirmation dialog when enabling anonymous user access in App Security, warning that unrestricted anonymous roles may expose data unintentionally. +* We now allow microflow and entity parameters to be optional for Java actions. +* We improved cleanup of queued tasks that are owned by missing nodes. +* Progressive web app (PWA) wrappers are now in GA. This feature allows you to package a PWA as a native app, and is especially useful when you want to keep a web-based application architecture while distributing the app through app stores. For more information, see [PWA Wrapper](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/). ### Fixes -- We fixed an issue when Studio Pro was not able to find Git after fresh installation if it was run from installer. (Ticket 232343, 232540, 232452, 234800, 231989) -- We fixed an issue where a native mobile app crashed with a synchronization error on startup when a user role did not have access to a module whose entity was included in the app's offline synchronization profile. The app now completes synchronization and returns no objects for that entity, matching the behavior of the previous XPath-based synchronization. (Ticket 241791) -- In the React client, we now copy files from a pluggable widget's `assets` subdirectory into the widget's directory under `dist/` during bundling, even when they are not directly imported by the widget. (Ticket 274514) -- We fixed an issue with the client where passing an empty string as a parameter to an on change microflow triggered an error. (Ticket 276118, 278248) -- We fixed an issue in offline apps where passing a Non-Persistent Entity (NPE) as a parameter to a server action would fail with `"Object hash is invalid!"` after a transparent session restore (for example, when a session expired and was automatically renewed in the background). The read-only hash key used to sign and verify NPE object hashes is now preserved across session restores via the auth token, and is only replaced on explicit logout. (Ticket 276642) -- We fixed an issue where Studio Pro crashed when pasting content from the clipboard while another application was also accessing the clipboard. (Ticket 278333) -- We fixed an issue where an app could crash on startup when a different user logged in after a previous session, due to a discrepancy between the offline database and session in some scenarios. (Ticket 280943) -- We fixed a race condition where the value setter for some widgets, for example ListView, would execute on a `destroyed` value store. This would cause a crash when opening pages with ListView. (Ticket 280988) -- We fixed SQLite Error 5, specifically the `database is locked` error. -- We fixed an issue where commit notes and metadata were empty after a rebase when there were no MPR changes and no conflicts detected by Git. -- We added a small delay between retries of saving conflicting project files due to rare occurrences of race conditions. -- We have fixed an issue where constants from protected modules were not exported when creating a portable app deployment package using MxBuild. -- We have fixed an issue where exporting a Portable App Package could fail because file copy operations were performed outside the default file-system scope. -- We fixed a rare race condition related to authtokens. -- We fixed a visual bug affecting **Call a nanoflow** action properties of widgets. Depending on the order in which the actions were configured, nanoflow settings of a different property would get displayed. -- We reverted the JavaScript `datetime` parsing fallback on `date-fns` parsing (introduced in 10.19) to ensure `datetime` parsing on the client side stays consistent and gives proper validation errors. This fix affects only client-side `datetime` parsing. +* We fixed an issue when Studio Pro was not able to find Git after fresh installation if it was run from installer. (Ticket 232343, 232540, 232452, 234800, 231989) +* We fixed an issue where a native mobile app crashed with a synchronization error on startup when a user role did not have access to a module whose entity was included in the app's offline synchronization profile. The app now completes synchronization and returns no objects for that entity, matching the behavior of the previous XPath-based synchronization. (Ticket 241791) +* In the React client, we now copy files from a pluggable widget's `assets` subdirectory into the widget's directory under `dist/` during bundling, even when they are not directly imported by the widget. (Ticket 274514) +* We fixed an issue with the client where passing an empty string as a parameter to an on change microflow triggered an error. (Ticket 276118, 278248) +* We fixed an issue in offline apps where passing a Non-Persistent Entity (NPE) as a parameter to a server action would fail with `"Object hash is invalid!"` after a transparent session restore (for example, when a session expired and was automatically renewed in the background). The read-only hash key used to sign and verify NPE object hashes is now preserved across session restores via the auth token, and is only replaced on explicit logout. (Ticket 276642) +* We fixed an issue where Studio Pro crashed when pasting content from the clipboard while another application was also accessing the clipboard. (Ticket 278333) +* We fixed an issue where an app could crash on startup when a different user logged in after a previous session, due to a discrepancy between the offline database and session in some scenarios. (Ticket 280943) +* We fixed a race condition where the value setter for some widgets, for example ListView, would execute on a `destroyed` value store. This would cause a crash when opening pages with ListView. (Ticket 280988) +* We fixed SQLite Error 5, specifically the `database is locked` error. +* We fixed an issue where commit notes and metadata were empty after a rebase when there were no MPR changes and no conflicts detected by Git. +* We added a small delay between retries of saving conflicting project files due to rare occurrences of race conditions. +* We have fixed an issue where constants from protected modules were not exported when creating a portable app deployment package using MxBuild. +* We have fixed an issue where exporting a Portable App Package could fail because file copy operations were performed outside the default file-system scope. +* We fixed a rare race condition related to authtokens. +* We fixed a visual bug affecting **Call a nanoflow** action properties of widgets. Depending on the order in which the actions were configured, nanoflow settings of a different property would get displayed. +* We reverted the JavaScript `datetime` parsing fallback on `date-fns` parsing (introduced in 10.19) to ensure `datetime` parsing on the client side stays consistent and gives proper validation errors. This fix affects only client-side `datetime` parsing. ### Breaking Changes -- Studio Pro on macOS now runs natively on Apple Silicon (arm64). Studio Pro, Version Selector, and command line tools are all built as native Apple Silicon binaries, so they no longer require Rosetta 2 translation layer, resulting in significantly improved performance. Intel-based Macs are no longer supported. +* Studio Pro on macOS now runs natively on Apple Silicon (arm64). Studio Pro, Version Selector, and command line tools are all built as native Apple Silicon binaries, so they no longer require Rosetta 2 translation layer, resulting in significantly improved performance. Intel-based Macs are no longer supported. ### Known Issues diff --git a/content/en/docs/releasenotes/studio-pro/11/11.1.md b/content/en/docs/releasenotes/studio-pro/11/11.1.md index c96e905d001..2000a2c370d 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.1.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.1.md @@ -138,4 +138,4 @@ weight: 99 * A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. - * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) \ No newline at end of file + * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.10.md b/content/en/docs/releasenotes/studio-pro/11/11.10.md index 9049cdc1124..c77a7547809 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.10.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.10.md @@ -123,4 +123,4 @@ weight: 90 * A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. - * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) \ No newline at end of file + * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.11.md b/content/en/docs/releasenotes/studio-pro/11/11.11.md index b9606fa13c9..bca461f9df1 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.11.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.11.md @@ -142,4 +142,4 @@ Mendix Portable Runtime (previously called Portable App Distribution) packages y * A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. - * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) \ No newline at end of file + * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.12.md b/content/en/docs/releasenotes/studio-pro/11/11.12.md index c460fbb53ca..f6ee47b039a 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.12.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.12.md @@ -20,42 +20,42 @@ weight: 88 ### New Features -- We added ability to see documents affected by Maia in the **Changes** pane. -- We added **Maia Explain** and **Solve problem with Maia Chat** context menu options to the error list to help you understand and resolve consistency errors directly with Maia. +* We added ability to see documents affected by Maia in the **Changes** pane. +* We added **Maia Explain** and **Solve problem with Maia Chat** context menu options to the error list to help you understand and resolve consistency errors directly with Maia. ### Improvements -- Maia now receives detailed information about errors inside microflow expressions it generates, so it can correct them more accurately. -- Embedded applications now support optional parameters for the home page and home microflow. +* Maia now receives detailed information about errors inside microflow expressions it generates, so it can correct them more accurately. +* Embedded applications now support optional parameters for the home page and home microflow. ### Fixes -- We fixed the `t is not a function` crash in microflow and workflow editors, introduced by the recent Microsoft update for WebView. If you installed an older version of the Microsoft Edge WebView as a workaround and you have no other affected Studio Pro installations, we recommend uninstalling it to prevent future compatibility issues. (Tickets 282617, 282634, 282668) -- We fixed an issue in React client mode where navigating between pages with the same layout left widgets unresponsive. (Ticket 276710) -- On SQL Server, when a unique constraint or foreign key constraint is dropped, we now use `IF EXISTS`. This avoids an automatic rollback of the synchronization transaction in case the constraint does not exist. (Ticket 279545) -- We fixed an issue where runtime fails to finish executing a queued task started by a user if the user is deleted during task execution. (Ticket 279891) -- We fixed an issue where extracting a sub-microflow from activities that referenced a predefined variable (such as `$currentUser`) created a parameter with the same reserved name on the new sub-microflow, resulting in a `Variable name is reserved` error. Predefined variables are now skipped when generating the parameters of the extracted sub-microflow, since they are already globally in scope. (Ticket 281319) -- We fixed an issue where building an application gave the following error: `System.FormatException: The input string '' was not in a correct format`. (Tickets 282176, 282223) -- We resolved the issue in Studio Pro that Java files do not get generated when deploying for Eclipse. (Ticket 282363) -- We fixed an issue with PWAs using Rspack where the service worker was not be created correctly. (Ticket 282616, 282601) -- We removed GuidMapping documents from the **Changes** pane. -- We fixed an issue where the **Extensions** setting was visible for all module types instead of only for add-ons. -- We fixed an issue in the **Call Web Service** activity and in consumed OData services that consume services using OData version 3. The XML parser now rejects DTD declarations and external entities, because a compromised server might exploit those features. -- We resolved an issue where Studio Pro hung on the **Updating original app** step when opening an app. -- 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 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. +* We fixed the `t is not a function` crash in microflow and workflow editors, introduced by the recent Microsoft update for WebView. If you installed an older version of the Microsoft Edge WebView as a workaround and you have no other affected Studio Pro installations, we recommend uninstalling it to prevent future compatibility issues. (Tickets 282617, 282634, 282668) +* We fixed an issue in React client mode where navigating between pages with the same layout left widgets unresponsive. (Ticket 276710) +* On SQL Server, when a unique constraint or foreign key constraint is dropped, we now use `IF EXISTS`. This avoids an automatic rollback of the synchronization transaction in case the constraint does not exist. (Ticket 279545) +* We fixed an issue where runtime fails to finish executing a queued task started by a user if the user is deleted during task execution. (Ticket 279891) +* We fixed an issue where extracting a sub-microflow from activities that referenced a predefined variable (such as `$currentUser`) created a parameter with the same reserved name on the new sub-microflow, resulting in a `Variable name is reserved` error. Predefined variables are now skipped when generating the parameters of the extracted sub-microflow, since they are already globally in scope. (Ticket 281319) +* We fixed an issue where building an application gave the following error: `System.FormatException: The input string '' was not in a correct format`. (Tickets 282176, 282223) +* We resolved the issue in Studio Pro that Java files do not get generated when deploying for Eclipse. (Ticket 282363) +* We fixed an issue with PWAs using Rspack where the service worker was not be created correctly. (Ticket 282616, 282601) +* We removed GuidMapping documents from the **Changes** pane. +* We fixed an issue where the **Extensions** setting was visible for all module types instead of only for add-ons. +* We fixed an issue in the **Call Web Service** activity and in consumed OData services that consume services using OData version 3. The XML parser now rejects DTD declarations and external entities, because a compromised server might exploit those features. +* We resolved an issue where Studio Pro hung on the **Updating original app** step when opening an app. +* 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 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 -- We dropped support for the following database versions that are no longer supported by the vendors: - - PostgreSQL 13 - - MariaDB 10.6 +* We dropped support for the following database versions that are no longer supported by the vendors: + * PostgreSQL 13 + * MariaDB 10.6 ## 11.12.0 {#1112} @@ -80,37 +80,37 @@ CDC can be used with the Mendix Event Broker or with a Bring Your Own Kafka (BYO #### Other New Features -- We introduced an option to purchase Maia Units. This resource allows you add additional capacity for your company to use Maia Make. For more information, see [Maia Resources](/control-center/maia-resources/). -- We introduced a modernized **Variables** pane. It now preserves expanded nodes as you step through the debugger, so you no longer lose your place between steps. -- We improved offline synchronization error handling so that when the server rejects uploaded objects (for example, due to validation rules or security constraints), the synchronization action now throws a `PartialSynchronizationError` (as long as **Throw error when server rejects objects during synchronization** option is enabled). Nanoflow developers can catch this error in a try/catch block to present a message to the user or take corrective action. -- Toggling the web fetch tool in Maia preferences now takes effect immediately, without needing to relaunch Studio Pro. -- We added the ability for the user to see the current Studio Pro version through the Preferences API. -- We added a `documentAdded` event to the `IProjectChangesApi`, allowing extensions to react when a new document is added to the project. -- We added the ability to filter the comparison pane by change status (such as added, modified, deleted, or moved). Filters are persisted across sessions, and an indicator is shown when any filter differs from the default. -- We added sortable columns to the **Comparison** pane. You can now click any column header in the **Documents** or **Elements** views to sort the list, making it easier to find and group changes. -- We implemented a new function `DATEFORMAT` in OQL. For more details, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#dateformat-function). -- We implemented two new functions in OQL: `RPAD` and `LPAD`. For more details, see the documentation for [LPAD](/refguide/oql-expression-syntax/#lpad-function) and [RPAD](/refguide/oql-expression-syntax/#rpad-function). -- You can now use Maia to work with theming and styling in Studio Pro. Maia can modify theme variables, create custom styling, and manage design properties—for example, updating colors, spacing, and typography across your app based on your styling requirements. -- Maia can now ask you clarifying questions before proceeding. When Maia needs more information, it will present one or more questions directly in the chat—supporting open-ended, single choice, and multiple choice answers—and use your responses to continue with the right approach. -- We released the Embedded Client in public Beta. You can now embed your Mendix app into any host application by configuring an [Embedded Navigation Profile](/refguide/navigation/#embedded) and following the instructions in the [Embedding the Client](/refguide/mendix-client/embedding-the-client/) guide. -- We added a `permissionsChanged` event to the Extension Permissions API, allowing extensions to be notified when permission states change. -- You can now add custom instructions on either project or module level. Project-level instructions will be added to every Maia conversation, while module-level ones will be added whenever Maia works with documents of a given module. -- Maia now thinks before responding. You can see what it is considering in real time, and revisit its reasoning at any point during the conversation. -- MCP OAuth authentication now uses a dedicated callback server on a fixed port range (44380–44384), enabling use with MCP servers that require pre-registered redirect URIs. -- MCP connections now support Mendix Identity (MxId3) authentication. MCP servers hosted on *.mendix.com automatically receive the user's platform access token. -- You can now add Maia Agent Instructions. Maia Instructions are agent instructions that are automatically added to the conversation context. You can add them to the project or module level. For more information, see [Maia Agent Instructions (AGENTS.md)](/refguide/maia-instructions/). -- We introduced the following new features to skills in Maia: - - A new **Skills** pane in Maia shows all custom skills that are currently loaded, their status, and which module they belong to (for module-level skills). You can filter the list to show only skills with errors. To apply the updated skills immediately, you can sync the skills. For more information, see [Skill Overview](/refguide/maia-agent-skills/#skill-overview) section in Maia Agent Skills. - - You can now add custom skills to non-protected app modules. These skills are exported together with other contents of the module. - - Maia now shows which custom skill (or which resource within a skill) it is drawing on while working, so you can follow along as it applies your project's conventions. -- We released a feature in public beta that lets you configure a custom LLM provider. In addition to the default Mendix Platform provider, you can now configure OpenAI-compatible providers or AWS Bedrock on a per-project basis. Mendix still recommends using the Mendix Platform provider for the best experience. For more information, see [Configuring a Custom AI Provider](/refguide/maia-make/#custom-provider). -- Maia is now better at fetching and understanding content from web pages by focusing on the main content. -- You can now attach Markdown files (*.md*, *.mdx*) to your Maia chat messages. Each file can be up to 50 KB, and you can attach as many as you need. The file contents are sent to Maia as context alongside your prompt. -- Maia Agent session can be saved by navigating **Help** > **Support Tools** > **Capture Maia Agent Session**, making it easier to share session details when troubleshooting or reporting issues. -- Data Transformers are now generally available. This allows you to transform complex JSON data, including cases that were never supported before. - - You can use a Data Transformer as a preprocessing step before passing the data into an Import Mapping, or use the transformed JSON directly, for example to send data to another system. - - Maia support has been added, so Maia can help creating and modifying Data Transformers. - - For more information, see [Data Transformer](/refguide/data-transformers/). +* We introduced an option to purchase Maia Units. This resource allows you add additional capacity for your company to use Maia Make. For more information, see [Maia Resources](/control-center/maia-resources/). +* We introduced a modernized **Variables** pane. It now preserves expanded nodes as you step through the debugger, so you no longer lose your place between steps. +* We improved offline synchronization error handling so that when the server rejects uploaded objects (for example, due to validation rules or security constraints), the synchronization action now throws a `PartialSynchronizationError` (as long as **Throw error when server rejects objects during synchronization** option is enabled). Nanoflow developers can catch this error in a try/catch block to present a message to the user or take corrective action. +* Toggling the web fetch tool in Maia preferences now takes effect immediately, without needing to relaunch Studio Pro. +* We added the ability for the user to see the current Studio Pro version through the Preferences API. +* We added a `documentAdded` event to the `IProjectChangesApi`, allowing extensions to react when a new document is added to the project. +* We added the ability to filter the comparison pane by change status (such as added, modified, deleted, or moved). Filters are persisted across sessions, and an indicator is shown when any filter differs from the default. +* We added sortable columns to the **Comparison** pane. You can now click any column header in the **Documents** or **Elements** views to sort the list, making it easier to find and group changes. +* We implemented a new function `DATEFORMAT` in OQL. For more details, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#dateformat-function). +* We implemented two new functions in OQL: `RPAD` and `LPAD`. For more details, see the documentation for [LPAD](/refguide/oql-expression-syntax/#lpad-function) and [RPAD](/refguide/oql-expression-syntax/#rpad-function). +* You can now use Maia to work with theming and styling in Studio Pro. Maia can modify theme variables, create custom styling, and manage design properties—for example, updating colors, spacing, and typography across your app based on your styling requirements. +* Maia can now ask you clarifying questions before proceeding. When Maia needs more information, it will present one or more questions directly in the chat—supporting open-ended, single choice, and multiple choice answers—and use your responses to continue with the right approach. +* We released the Embedded Client in public Beta. You can now embed your Mendix app into any host application by configuring an [Embedded Navigation Profile](/refguide/navigation/#embedded) and following the instructions in the [Embedding the Client](/refguide/mendix-client/embedding-the-client/) guide. +* We added a `permissionsChanged` event to the Extension Permissions API, allowing extensions to be notified when permission states change. +* You can now add custom instructions on either project or module level. Project-level instructions will be added to every Maia conversation, while module-level ones will be added whenever Maia works with documents of a given module. +* Maia now thinks before responding. You can see what it is considering in real time, and revisit its reasoning at any point during the conversation. +* MCP OAuth authentication now uses a dedicated callback server on a fixed port range (44380–44384), enabling use with MCP servers that require pre-registered redirect URIs. +* MCP connections now support Mendix Identity (MxId3) authentication. MCP servers hosted on *.mendix.com automatically receive the user's platform access token. +* You can now add Maia Agent Instructions. Maia Instructions are agent instructions that are automatically added to the conversation context. You can add them to the project or module level. For more information, see [Maia Agent Instructions (AGENTS.md)](/refguide/maia-instructions/). +* We introduced the following new features to skills in Maia: + * A new **Skills** pane in Maia shows all custom skills that are currently loaded, their status, and which module they belong to (for module-level skills). You can filter the list to show only skills with errors. To apply the updated skills immediately, you can sync the skills. For more information, see [Skill Overview](/refguide/maia-agent-skills/#skill-overview) section in Maia Agent Skills. + * You can now add custom skills to non-protected app modules. These skills are exported together with other contents of the module. + * Maia now shows which custom skill (or which resource within a skill) it is drawing on while working, so you can follow along as it applies your project's conventions. +* We released a feature in public beta that lets you configure a custom LLM provider. In addition to the default Mendix Platform provider, you can now configure OpenAI-compatible providers or AWS Bedrock on a per-project basis. Mendix still recommends using the Mendix Platform provider for the best experience. For more information, see [Configuring a Custom AI Provider](/refguide/maia-make/#custom-provider). +* Maia is now better at fetching and understanding content from web pages by focusing on the main content. +* You can now attach Markdown files (*.md*, *.mdx*) to your Maia chat messages. Each file can be up to 50 KB, and you can attach as many as you need. The file contents are sent to Maia as context alongside your prompt. +* Maia Agent session can be saved by navigating **Help** > **Support Tools** > **Capture Maia Agent Session**, making it easier to share session details when troubleshooting or reporting issues. +* Data Transformers are now generally available. This allows you to transform complex JSON data, including cases that were never supported before. + * You can use a Data Transformer as a preprocessing step before passing the data into an Import Mapping, or use the transformed JSON directly, for example to send data to another system. + * Maia support has been added, so Maia can help creating and modifying Data Transformers. + * For more information, see [Data Transformer](/refguide/data-transformers/). ### Improvements diff --git a/content/en/docs/releasenotes/studio-pro/11/11.2.md b/content/en/docs/releasenotes/studio-pro/11/11.2.md index 8c6a51a20e0..838752d20c2 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.2.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.2.md @@ -86,4 +86,4 @@ weight: 98 * A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. - * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) \ No newline at end of file + * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.3.md b/content/en/docs/releasenotes/studio-pro/11/11.3.md index ec678f4599c..8e7586d88a5 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.3.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.3.md @@ -113,4 +113,4 @@ weight: 97 * A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. - * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) \ No newline at end of file + * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.4.md b/content/en/docs/releasenotes/studio-pro/11/11.4.md index 3b9c4c8f524..cf596c8f0c4 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.4.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.4.md @@ -118,4 +118,4 @@ These additions make it easier to inspect server-side changes and stay up to dat * A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. - * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) \ No newline at end of file + * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.5.md b/content/en/docs/releasenotes/studio-pro/11/11.5.md index 8ef84e1051a..60db67132b8 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.5.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.5.md @@ -87,4 +87,4 @@ weight: 95 * A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. - * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) \ No newline at end of file + * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.7.md b/content/en/docs/releasenotes/studio-pro/11/11.7.md index bf3e0706d16..2dfaf5af4cb 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.7.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.7.md @@ -112,4 +112,4 @@ weight: 93 * A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. - * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) \ No newline at end of file + * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.8.md b/content/en/docs/releasenotes/studio-pro/11/11.8.md index 431c7eab128..c00789e6dae 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.8.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.8.md @@ -131,4 +131,4 @@ This ensures your app uses the current ISO 639 standard and avoids future compat * A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. - * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) \ No newline at end of file + * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.9.md b/content/en/docs/releasenotes/studio-pro/11/11.9.md index 885155565a3..792373a6085 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.9.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.9.md @@ -191,4 +191,4 @@ We changed how Studio Pro stores Marketplace identity data for widgets. This dat * A known issue occurs in multiple logic editors due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150: * When creating a new microflow, nanoflow or rule, the error above occurs.  The document is created but the editor does not open, preventing further development activities. * When opening the Logic Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error. - * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) \ No newline at end of file + * Fixed in [11.12.1](/releasenotes/studio-pro/11.12/#fix-t-is-not-a-function) diff --git a/content/en/docs/workstation/client/wks-batch-registration.md b/content/en/docs/workstation/client/wks-batch-registration.md index c7c7847880e..4028e74ed33 100644 --- a/content/en/docs/workstation/client/wks-batch-registration.md +++ b/content/en/docs/workstation/client/wks-batch-registration.md @@ -27,12 +27,12 @@ If you are developing or testing Workstation configurations, you can register a {{< figure src="/attachments/workstation/wks-install7.png" class="no-border" >}} -4. Open the Workstation Client and paste the copied registration token into the **Enter your registration token** field. -5. Click **Register computer**. +6. Open the Workstation Client and paste the copied registration token into the **Enter your registration token** field. +7. Click **Register computer**. {{< figure src="/attachments/workstation/wks-install8.png" class="no-border" >}} -6. In Workstation Management, in the **Computer Registration** dialog, click **Done**. +8. In Workstation Management, in the **Computer Registration** dialog, click **Done**. {{< figure src="/attachments/workstation/wks-install9.png" class="no-border" >}} diff --git a/content/en/docs/workstation/client/wks-client-proxy-settings.md b/content/en/docs/workstation/client/wks-client-proxy-settings.md index b99e3c8c433..40a2a127d6c 100644 --- a/content/en/docs/workstation/client/wks-client-proxy-settings.md +++ b/content/en/docs/workstation/client/wks-client-proxy-settings.md @@ -26,4 +26,4 @@ To use a custom proxy configuration, you must start the Workstation Client from ``` set HTTPS_PROXY=[PROXY_IP_ADDRESS] && "C:\Program Files\Mendix Workstation\Mendix Workstation.exe" -``` \ No newline at end of file +``` diff --git a/content/en/docs/workstation/connector/wks-connector-configure.md b/content/en/docs/workstation/connector/wks-connector-configure.md index a26e01ffa71..da10bd08655 100644 --- a/content/en/docs/workstation/connector/wks-connector-configure.md +++ b/content/en/docs/workstation/connector/wks-connector-configure.md @@ -40,4 +40,4 @@ You can invite other Workstation Management users to your workspace to share con To invite a user, click **Team** in the left navigation menu, then click **Invite Team Member**. Enter the user's email address and select a role. For more information about the available roles, see [Managing the Team](/mendix-workstation/management-team/). -To change a user's role or remove them from the workspace, click the **three dot** icon in the right column of the user list. This action requires the Owner or Workspace Admin role. \ No newline at end of file +To change a user's role or remove them from the workspace, click the **three dot** icon in the right column of the user list. This action requires the Owner or Workspace Admin role. diff --git a/content/en/docs/workstation/connector/wks-connector.md b/content/en/docs/workstation/connector/wks-connector.md index 21d9ecd8d5d..43d5072a9ed 100644 --- a/content/en/docs/workstation/connector/wks-connector.md +++ b/content/en/docs/workstation/connector/wks-connector.md @@ -37,4 +37,4 @@ To install and configure the Workstation Connector, perform the following steps: For more information, see [Registering Workstation Clients](/mendix-workstation/register/). -4. Configure your application. For more information, see [Integrating with Mendix Studio Pro](/mendix-workstation/configure-connector/). \ No newline at end of file +4. Configure your application. For more information, see [Integrating with Mendix Studio Pro](/mendix-workstation/configure-connector/). diff --git a/content/en/docs/workstation/management/wks-management-admin.md b/content/en/docs/workstation/management/wks-management-admin.md index 8b1c9540702..877e00890b8 100644 --- a/content/en/docs/workstation/management/wks-management-admin.md +++ b/content/en/docs/workstation/management/wks-management-admin.md @@ -111,4 +111,4 @@ When developer mode is enabled, users of the Workstation Client can perform the {{% alert color="info" %}} For production environments, it is strongly recommended to disable Developer Mode. This prevents Workstation operators from accidentally quitting or deregistering the Workstation Client, and restricts access to debugging tools that are not needed in a live operational setting. -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/workstation/management/wks-management-settings.md b/content/en/docs/workstation/management/wks-management-settings.md index f297c3d3e39..c4731f80e91 100644 --- a/content/en/docs/workstation/management/wks-management-settings.md +++ b/content/en/docs/workstation/management/wks-management-settings.md @@ -49,4 +49,4 @@ The option to delete a workspace is available only to the workspace [Owner](/men {{% alert color="warning" %}} Deleting a workspace cannot be reverted. The entire repository and all associated cloud environments are deleted permanently. Selecting this option makes the project inaccessible to all team members, including the workspace Owner. -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/workstation/management/wks-management-team.md b/content/en/docs/workstation/management/wks-management-team.md index 911a484d36d..635850211fd 100644 --- a/content/en/docs/workstation/management/wks-management-team.md +++ b/content/en/docs/workstation/management/wks-management-team.md @@ -82,4 +82,4 @@ You can assign the following roles to your users: * Viewing configurations without editing them * Exporting stations (single and in bulk). -All members except for the workspace owner can leave a workspace. \ No newline at end of file +All members except for the workspace owner can leave a workspace. diff --git a/content/en/docs/workstation/management/wks-management.md b/content/en/docs/workstation/management/wks-management.md index fc774e3a023..c5831aabecd 100644 --- a/content/en/docs/workstation/management/wks-management.md +++ b/content/en/docs/workstation/management/wks-management.md @@ -35,4 +35,4 @@ To start using Mendix Workstation, you must first create a workspace and a stati 2. Click **Edit Station**. 3. Clear the **Detect Card Readers** check box. -After you create a workspace and station, you can proceed with installing the Workstation Clients on the computers which you want to connect to your devices. For more information, see [Mendix Workstation Client](/mendix-workstation/client/). \ No newline at end of file +After you create a workspace and station, you can proceed with installing the Workstation Clients on the computers which you want to connect to your devices. For more information, see [Mendix Workstation Client](/mendix-workstation/client/). diff --git a/content/en/docs/workstation/management/wks-monitoring.md b/content/en/docs/workstation/management/wks-monitoring.md index fcb55f874ec..09b42add03c 100644 --- a/content/en/docs/workstation/management/wks-monitoring.md +++ b/content/en/docs/workstation/management/wks-monitoring.md @@ -18,16 +18,15 @@ You can access the Usage Reports by performing the following steps: 1. To view the reports for all workspaces that you own or administer, go to Workstation Management, and click **My Usage Report**. - {{< figure src="/attachments/workstation/wks-usage1.png" class="no-border" >}} + {{< figure src="/attachments/workstation/wks-usage1.png" >}} 2. To view a report for all workspaces that are owned by your company, go to Workstation Management and click **Company Usage Report**. -{{% alert color="info" %}} -The **Company Usage Report** tab is accessible only to users who have the Mendix Admin role assigned in [Control Center](/control-center/). -{{% /alert %}} + {{% alert color="info" %}}The **Company Usage Report** tab is accessible only to users who have the Mendix Admin role assigned in [Control Center](/control-center/). + {{% /alert %}} 3. To view the reports for a specific workspace, open the workspace in Workstation Management, and then click **Usage**. - {{< figure src="/attachments/workstation/wks-usage2.png" class="no-border" >}} + {{< figure src="/attachments/workstation/wks-usage2.png" >}} -The Usage Reports display information about the usage trends for each Workstation Client both daily and over time. \ No newline at end of file +The Usage Reports display information about the usage trends for each Workstation Client both daily and over time. diff --git a/content/en/docs/workstation/troubleshooting/_index.md b/content/en/docs/workstation/troubleshooting/_index.md index 00d2443dd39..72e419ed35d 100644 --- a/content/en/docs/workstation/troubleshooting/_index.md +++ b/content/en/docs/workstation/troubleshooting/_index.md @@ -11,4 +11,3 @@ weight: 20 ## Introduction If you encounter any issues with your Workstation Management, Connector, or Client, use the following troubleshooting tips to help you solve them. - diff --git a/content/en/docs/workstation/troubleshooting/wks-troubleshooting-mgmt.md b/content/en/docs/workstation/troubleshooting/wks-troubleshooting-mgmt.md index a2fa9650517..8157156e964 100644 --- a/content/en/docs/workstation/troubleshooting/wks-troubleshooting-mgmt.md +++ b/content/en/docs/workstation/troubleshooting/wks-troubleshooting-mgmt.md @@ -22,4 +22,4 @@ Manually deregister the station in Workstation Management. The Workspace's owner account has been deactivated, and the owner did not transfer the ownership to another Workspace member. -Contact Mendix Support to transfer workspace ownership. \ No newline at end of file +Contact Mendix Support to transfer workspace ownership. diff --git a/content/en/docs/workstation/wks-quickstart.md b/content/en/docs/workstation/wks-quickstart.md index 894da83f14e..811a711a614 100644 --- a/content/en/docs/workstation/wks-quickstart.md +++ b/content/en/docs/workstation/wks-quickstart.md @@ -95,12 +95,12 @@ The following instructions assume that you are registering a single computer for {{< figure src="/attachments/workstation/wks-install7.png" class="no-border" >}} -4. Open the Workstation Client and paste the copied registration token into the **Enter your registration token** field. -5. Click **Register computer**. +6. Open the Workstation Client and paste the copied registration token into the **Enter your registration token** field. +7. Click **Register computer**. {{< figure src="/attachments/workstation/wks-install8.png" class="no-border" >}} -6. In Workstation Management, in the **Computer Registration** dialog, click **Done**. +8. In Workstation Management, in the **Computer Registration** dialog, click **Done**. {{< figure src="/attachments/workstation/wks-install9.png" class="no-border" >}} @@ -180,4 +180,4 @@ For more information, see [Security Best Practices for Mendix Workstation](/mend ### Maintenance Guidelines * Periodically review and update workstation and device configurations. -* Monitor workstation health and resolve any connectivity issues promptly. \ No newline at end of file +* Monitor workstation health and resolve any connectivity issues promptly.