diff --git a/content/en/docs/apidocs-mxsdk/apidocs/audit-logs-api.md b/content/en/docs/apidocs-mxsdk/apidocs/audit-logs-api.md index 4de79a1e734..2145331bde1 100755 --- a/content/en/docs/apidocs-mxsdk/apidocs/audit-logs-api.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/audit-logs-api.md @@ -34,4 +34,4 @@ Two types of Authorization headers are supported: `Bearer` (Client credentials o The following API reference includes information on which scope and token type is required for each endpoint. -{{< swaggerui src="/openapi-spec/audit-logging-v1.yaml" >}} \ No newline at end of file +{{< swaggerui src="/openapi-spec/audit-logging-v1.yaml" >}} diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md index 2f0c83d2fd7..840a1cd8dce 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md @@ -482,7 +482,6 @@ Then the Studio Pro UI for the property appears like this: ### Action {#action} - The action property type allows a user to configure an action which can do things like call nanoflows, save changes, and open pages. If a `dataSource` attribute is not specified, the client will receive an `ActionValue` representing the action or `undefined` if the **Do nothing** action was selected. @@ -838,7 +837,6 @@ The [`action`](#action), [`attribute`](#attribute), [`association`](#association ### Selection {#selection} - The selection property allows a widget to read and set a selection that can be used in actions, expressions, or a `Listen to` data source of a data view. #### XML Attributes @@ -909,7 +907,6 @@ Label property allows a pluggable widget to have labeling functionality similar #### setLabel {#setLabel} - You can use `setLabel` to specify which properties can be used to set the `Label` property value. Configuring the value of a property with the `setLabel` attribute will automatically update the value of `Label`. diff --git a/content/en/docs/deployment/mx-azure/mx-azure-cluster-visibility.md b/content/en/docs/deployment/mx-azure/mx-azure-cluster-visibility.md index c06e31a2768..6240676c574 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-cluster-visibility.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-cluster-visibility.md @@ -16,8 +16,8 @@ Below is a short summary of the key aspects of cluster visibility. For more info * Visibility - All cluster namespace members can view initialized clusters to facilitate support and monitoring. * Security - Only Cluster Managers with appropriate Azure RBAC roles (Owner or Contributor) can modify cluster settings. * Separation of Concerns: - * Initialized clusters are visible to all namespace members regardless of Azure RBAC. - * Editing capabilities require both Cluster Manager role or Azure Owner or Contributor permissions. + * Initialized clusters are visible to all namespace members regardless of Azure RBAC. + * Editing capabilities require both Cluster Manager role or Azure Owner or Contributor permissions. ## Cluster Visibility diff --git a/content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy-pad.md b/content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy-pad.md index f99ebe814d3..5b056c0334b 100644 --- a/content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy-pad.md +++ b/content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy-pad.md @@ -71,4 +71,5 @@ To deploy your app to Cloud Foundry, perform the following steps: ``` 5. Run the `cf push` command. + 6. Verify that the Mendix app has started successfully. diff --git a/content/en/docs/marketplace/genai/reference-guide/agent-editor.md b/content/en/docs/marketplace/genai/reference-guide/agent-editor.md index 661886cc007..d5f27b48121 100644 --- a/content/en/docs/marketplace/genai/reference-guide/agent-editor.md +++ b/content/en/docs/marketplace/genai/reference-guide/agent-editor.md @@ -225,6 +225,7 @@ If a call fails during testing, a generic error message is shown in the Agent Ed ### Including the Agent in the App Logic {#call-agent} Include an agent in the app logic by calling it from a microflow. Agent Editor provides **Call Agent** toolbox actions in the **Agent Editor** category: + * **Call Agent without History** focuses on single-call, task-style execution * **Call Agent with History** supports conversational scenarios with multiple messages diff --git a/content/en/docs/marketplace/platform-supported-content/modules/excel-exporter.md b/content/en/docs/marketplace/platform-supported-content/modules/excel-exporter.md index e0235c3f6f1..610e7d38563 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/excel-exporter.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/excel-exporter.md @@ -57,10 +57,10 @@ On the template details page, you can define the template with the following ite {{% alert color="info" %}}If you use an uploaded Excel file as a template, the names of the sheets and columns in your template will be used. However, the background color in your template will be overruled by the **Background color** (including **none**) specified in the applicable style. {{% /alert %}} * **Sanitize formulas to text**: When enabled, the module automatically sanitizes any string values that begin with potentially dangerous characters: - - `=` (equals) - - `+` (plus) - - `-` (minus/hyphen) - - `@` (at) + * `=` (equals) + * `+` (plus) + * `-` (minus/hyphen) + * `@` (at) {{% alert color="info" %}} When sanitization is enabled, the exporter prepends a apostrophe (`'`) to any string value starting with these characters. This forces Excel and CSV applications to treat the value as literal text rather than a formula. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md index 11449485fb1..791877e3521 100755 --- a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md @@ -76,7 +76,7 @@ If you want to use specific resources, you should instead expose a new endpoint 9. Click **Back** to return to the **Details** page. 10. Click the **Ingestion Configuration** tab to set up your ingestion destination table. 11. Click **Create** to start setting up the Ingestion Configuration. - * **Target Database** – Name of the database for data ingestion + ***Target Database** – Name of the database for data ingestion * **Target Schema** – Target schema where all data will be ingested 12. Click **Save**. 13. Click the **Data Ingestion** tab, where you can start your data ingestion or set up a schedule. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-mcp-byo.md b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-mcp-byo.md index 962d30761e1..d7e6fc7d63a 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-mcp-byo.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-mcp-byo.md @@ -42,7 +42,7 @@ Because Snowflake conforms to the API specification of OpenAI, you can use the O For example, the URL may look like the following: `https:/.snowflakecomputing.com/api/v2/cortex/v1/`. - 5. Save your changes. + 1. Save your changes. {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/save-changes.png" >}} @@ -52,7 +52,7 @@ Because Snowflake conforms to the API specification of OpenAI, you can use the O {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/manage-deployed-models.png" >}} - 2. Click **Add new model** to add an LLM from the [list of available LLMs](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-rest-api#model-availability) in your Snowflake account. + 1. Click **Add new model** to add an LLM from the [list of available LLMs](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-rest-api#model-availability) in your Snowflake account. {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/new-deployed-model.png" >}} @@ -60,8 +60,8 @@ Because Snowflake conforms to the API specification of OpenAI, you can use the O The **Model name** field in the Deployed Model configuration in Mendix must match exactly with the model name in Snowflake. - 3. Complete the configuration for your model. - 4. Save your changes. + 1. Complete the configuration for your model. + 2. Save your changes. 3. Test the configuration by performing the following steps: @@ -69,7 +69,7 @@ Because Snowflake conforms to the API specification of OpenAI, you can use the O {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/test-option.png" >}} - 2. Select your deployed model from the drop-down list. - 3. Click **Test**. + 1. Select your deployed model from the drop-down list. + 2. Click **Test**. - {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/test.png" >}} \ No newline at end of file + {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/test.png" >}} diff --git a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-mcp.md b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-mcp.md index 380c6f6a8d0..8ee9980c6cd 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-mcp.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-mcp.md @@ -410,7 +410,7 @@ After setting up the MCP server, you can now create a Mendix AI agent and connec 8. On the **Consumed MCP Services** page, click **MCP Client** and configure the following properties of your Snowflake MCP server: 1. Enter a name. - 2. Specify the MCP endpoint in the following format: `https://.snowflakecomputing.com/api/v2/databases//schemas//mcp-servers/ ` + 2. Specify the MCP endpoint in the following format: `https://.snowflakecomputing.com/api/v2/databases//schemas//mcp-servers/` {{% alert color="info" %}} If your Snowflake account ID contains underscores (`_`), replace them with `-` in the endpoint. This is only required for the account ID, not for the database name, schema name, or MCP server name. @@ -472,4 +472,4 @@ The primary table is SNOWFLAKE_MCP_DEMO.TESTDATA.TICKETS: - Always confirm successful operations by showing the user what was created or retrieved. - Use fully qualified table names (DATABASE.SCHEMA.TABLE) in all tool calls. - If a tool call returns an error, explain the issue clearly and suggest a correction. -``` \ No newline at end of file +``` diff --git a/content/en/docs/private-platform/nist-controls/_index.md b/content/en/docs/private-platform/nist-controls/_index.md index 254d1d3397b..375e14b3d2c 100644 --- a/content/en/docs/private-platform/nist-controls/_index.md +++ b/content/en/docs/private-platform/nist-controls/_index.md @@ -15,4 +15,3 @@ Documents in this section provide more information about Private Mendix Platform In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. ## Control Categories - diff --git a/content/en/docs/private-platform/nist-controls/ac/_index.md b/content/en/docs/private-platform/nist-controls/ac/_index.md index ce691ab220c..8af6a77945d 100644 --- a/content/en/docs/private-platform/nist-controls/ac/_index.md +++ b/content/en/docs/private-platform/nist-controls/ac/_index.md @@ -12,4 +12,4 @@ simple_list: true Documents in this section provide more information about Private Mendix Platform's compliance with the Access Control (AC) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect. -In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. \ No newline at end of file +In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac01.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac01.md index 7cf48c7bda7..27d551c704d 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac01.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac01.md @@ -67,4 +67,4 @@ Private Mendix Platform offers integrations to customer IdP over industry-standa {{< figure src="/attachments/private-platform/nist-ac/nist-ac-01-1.png" class="no-border" >}} -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-01-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-01-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac02-1103.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac02-1103.md index 808c208a3f2..da335b35603 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac02-1103.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac02-1103.md @@ -49,4 +49,4 @@ The user is logged out after the configured time period: If the **Show notification** option is on, the user is alerted before they are logged out: -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-02-1103-3.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-02-1103-3.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac02.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac02.md index 5e3e3632006..0f1ec23598a 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac02.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac02.md @@ -42,19 +42,19 @@ The organization: * Reviews accounts for compliance with account management requirements at an organization-defined frequency. * Establishes a process for reissuing shared and group account credentials (if deployed) when individuals are removed from the group. - ### Supplemental Guidance +### Supplemental Guidance Information system account types include the following: - * Individual - * Shared - * Group - * System - * Guest or anonymous - * Emergency - * Developer, manufacturer, or vendor - * Temporary - * Service. +* Individual +* Shared +* Group +* System +* Guest or anonymous +* Emergency +* Developer, manufacturer, or vendor +* Temporary +* Service. Some of the account management requirements listed above can be implemented by organizational information systems. The identification of authorized users of the information system and the specification of access privileges reflects the requirements in other security controls in the security plan. @@ -66,8 +66,8 @@ The organization: Conditions for disabling or deactivating accounts include, for example: - * When shared, group, emergency, or temporary accounts are no longer required - * When individuals are transferred or terminated. +* When shared, group, emergency, or temporary accounts are no longer required +* When individuals are transferred or terminated. Some types of information system accounts may require specialized training. @@ -120,4 +120,4 @@ Private Mendix Platform offers integrations to customer IdP over industry-standa {{< figure src="/attachments/private-platform/nist-ac/nist-ac-01-1.png" class="no-border" >}} -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-01-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-01-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0201.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0201.md index 3fb743bb1ec..81e776e2860 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0201.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0201.md @@ -55,4 +55,4 @@ Private Mendix Platform offers integrations to customer IdP over industry-standa {{< figure src="/attachments/private-platform/nist-ac/nist-ac-01-1.png" class="no-border" >}} -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-01-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-01-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0203.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0203.md index d37a8232a3f..16c16ae3cde 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0203.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0203.md @@ -36,4 +36,4 @@ Private Mendix Platform provides the setting to configure **Inactivity Period fo Private Mendix Platform provides a setting to configure the inactivity period at **Settings > Identity & Access > Preferences**: -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0203-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0203-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0204.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0204.md index 550b77259eb..1c7b8373bcd 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0204.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0204.md @@ -41,4 +41,4 @@ As an example IdP, Microsoft Entra ID natively captures all account lifecycle ev * For long-term log retention, audit logs should be forwarded to a Log Analytics Workspace or Azure Storage Account via Diagnostic Settings. * Customers may implement alerts using their audit and logging management system of choice, such as Microsoft Sentinel or any third-party SIEM integrated by using Azure Event Hub. -Other IdP systems would offer similar approaches to fulfilling this control. \ No newline at end of file +Other IdP systems would offer similar approaches to fulfilling this control. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0212.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0212.md index f81482f906e..7ca64ee0ce5 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0212.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0212.md @@ -62,4 +62,4 @@ The Private Mendix Platform provides platform-level audit logs capturing account The Mendix App Developer implements application-level audit logging within each Mendix application to capture user activity relevant to atypical usage detection. The customer ingests both platform and application logs into their monitoring tool of choice (for example, Microsoft Sentinel, Splunk Enterprise Security) and configures detection rules, alerting, and response workflows for atypical account behavior. -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0212-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0212-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac03.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac03.md index 9809282ee15..223362c6561 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac03.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac03.md @@ -104,4 +104,4 @@ For row-level or attribute-based security, see below: For Mendix Published API authentication and authorization, see below: -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-03-3.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-03-3.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0421.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0421.md index c57a2b8de44..755ff7193ac 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0421.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0421.md @@ -51,4 +51,4 @@ For access rule configurations of the Mendix application model, see below: Mendix role-based access control (RBAC) can be combined with microflows to enforce separation of information flows at runtime: -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0412-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0412-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac05.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac05.md index a57a4b5aa34..ee4213cfc46 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac05.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac05.md @@ -60,4 +60,4 @@ The Platform provides dashboards and overviews for administrators to monitor gro For more information about role and group management features, see [Dynamic Role Management](/private-mendix-platform/dynamic-role-management/). -For more information about application-level security and role assignment, see [Security Reference Guide](/refguide/security/). \ No newline at end of file +For more information about application-level security and role assignment, see [Security Reference Guide](/refguide/security/). diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0601.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0601.md index 8d5fe9d70d6..03f3e9f1e0c 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0601.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0601.md @@ -77,4 +77,4 @@ Define privileged roles to grant privileged permissions and only assign trusted Review all role and group assignments from Private Mendix Platform administrator view: -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0601-3.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0601-3.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0602.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0602.md index f5fbe586d3c..44f79cfb03c 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0602.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0602.md @@ -64,4 +64,4 @@ Customers should: For more information, see the following documents: * [Mendix Security Reference Guide](/refguide/security/) -* [Dynamic Role Management in Private Mendix Platform](/private-mendix-platform/dynamic-role-management/) \ No newline at end of file +* [Dynamic Role Management in Private Mendix Platform](/private-mendix-platform/dynamic-role-management/) diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0605.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0605.md index 17d4b517db5..d661352eb1e 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0605.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0605.md @@ -64,4 +64,4 @@ Customers should: For more information, see the following documents: * [Mendix Security Reference Guide](/refguide/security/) -* [Dynamic Role Management in Private Mendix Platform](/private-mendix-platform/dynamic-role-management/) \ No newline at end of file +* [Dynamic Role Management in Private Mendix Platform](/private-mendix-platform/dynamic-role-management/) diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0607.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0607.md index efbed73e678..b4f987fe2a1 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0607.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0607.md @@ -75,4 +75,4 @@ Audit logs provide evidence of privilege changes, reassignments, and removals: {{< figure src="/attachments/private-platform/nist-ac/nist-ac-0607-4.png" alt="Audit activity logs in Private Mendix Platform" class="no-border" >}} -Customers should retain documentation of privilege review activities and corrective actions as compliance evidence. \ No newline at end of file +Customers should retain documentation of privilege review activities and corrective actions as compliance evidence. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0608.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0608.md index a714830f439..7e8a401b483 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0608.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0608.md @@ -66,4 +66,4 @@ Private Mendix Platform offers a default runtime base image which uses normal us {{< figure src="/attachments/private-platform/nist-ac/nist-ac-0608-2.png" class="no-border" >}} -For information about configuring Mendix storage plans with IRSA, see [Storage Plans](/developerportal/deploy/private-cloud-storage-plans/#walkthrough-aws-irsa). \ No newline at end of file +For information about configuring Mendix storage plans with IRSA, see [Storage Plans](/developerportal/deploy/private-cloud-storage-plans/#walkthrough-aws-irsa). diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0609.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0609.md index a16ae5234f7..391a0c40c71 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0609.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0609.md @@ -114,4 +114,4 @@ Private Mendix Platform provides the following settings to configure the period Private Mendix Platform provides the following settings archive, back up, or download logs permanently after a period (duration) in days: -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0609-5.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0609-5.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac07.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac07.md index 14d2437692a..de28c80b5e2 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac07.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac07.md @@ -50,4 +50,4 @@ Private Mendix Platform provides the setting to configure **Failed Login Attempt The setting to configure **Failed Login Attempts to Lockout** is available at **Settings > Identity & Access > Preferences**. -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-07-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-07-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac08.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac08.md index 71a8fc18cb2..117bb549cef 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac08.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac08.md @@ -61,4 +61,4 @@ Private Mendix Platform displays an access banner on the login page: Private Mendix Platform displays a banner after login: -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-08-3.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-08-3.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac10.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac10.md index 70437bc2410..96614b96431 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac10.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac10.md @@ -38,4 +38,4 @@ Private Mendix Platform provides the setting to configure maximum concurrent ses ## Proof and Remarks -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-10-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-10-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac12.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac12.md index 2879aae60ee..7f8c45234f6 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac12.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac12.md @@ -34,4 +34,4 @@ In Admin mode, Private Mendix Platform admins can access the **Logout All Users* ## Proof and Remarks -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-12-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-12-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac14.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac14.md index 0a5587d5418..d7e707636af 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac14.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac14.md @@ -54,4 +54,4 @@ For more information, see the following documents: For more information, see the following documents: * [Set Up Anonymous User Security](/howto/security/set-up-anonymous-user-security/) -* [Create a Secure App](/howto/security/create-a-secure-app/) \ No newline at end of file +* [Create a Secure App](/howto/security/create-a-secure-app/) diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac17.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac17.md index 2332fa29673..9bf4c046d9d 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac17.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac17.md @@ -82,4 +82,4 @@ Mendix provides [OIDC](/appstore/modules/oidc/) and [SAML SSO](/appstore/modules Private Mendix Platform supports OIDC and SAML configuration. -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-17-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-17-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1701.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1701.md index e47206722fa..63a1a75f6e3 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1701.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1701.md @@ -48,4 +48,4 @@ Mendix does not provide native monitoring or control of remote access within Pri ## Proof and Remarks -For more information about configuring monitoring tools, see [Monitoring Environments in Mendix on Kubernetes](/developerportal/deploy/private-cloud-monitor/). \ No newline at end of file +For more information about configuring monitoring tools, see [Monitoring Environments in Mendix on Kubernetes](/developerportal/deploy/private-cloud-monitor/). diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1702.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1702.md index 9bb5fad1ac9..086a8b52473 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1702.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1702.md @@ -47,4 +47,4 @@ Mendix does not implement or manage cryptographic protection for remote access s ## Proof and Remarks -For more information about setting up Kubernetes Ingress with TLS, see [Network Ingress Settings in Mendix on Kubernetes](/developerportal/deploy/private-cloud-cluster/private-cloud-ingress-settings/). \ No newline at end of file +For more information about setting up Kubernetes Ingress with TLS, see [Network Ingress Settings in Mendix on Kubernetes](/developerportal/deploy/private-cloud-cluster/private-cloud-ingress-settings/). diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1703.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1703.md index 19aa809a65e..8495ded95aa 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1703.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1703.md @@ -44,4 +44,4 @@ Customers should periodically review access control point configuration and plac Any changes to access control points should be documented and tested to ensure continued compliance and operational effectiveness. -Mendix does not create, configure, or maintain network access control points in Private Mendix Platform. All such controls are managed at the infrastructure level by the customer and their designated providers. \ No newline at end of file +Mendix does not create, configure, or maintain network access control points in Private Mendix Platform. All such controls are managed at the infrastructure level by the customer and their designated providers. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1704.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1704.md index 4b704a091a1..7e6baa12056 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1704.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1704.md @@ -45,4 +45,4 @@ The App Implementer is responsible for configuring the Mendix application so tha For example, access to critical API endpoints or administrative functions should be protected by appropriate access control mechanisms and permissions in line with organizational requirements. -Mendix does not determine or enforce privileged remote access policies. It is the customer's responsibility to define, document, and implement these controls. \ No newline at end of file +Mendix does not determine or enforce privileged remote access policies. It is the customer's responsibility to define, document, and implement these controls. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1706.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1706.md index 200ad833dec..186b77c3cdf 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1706.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1706.md @@ -49,4 +49,4 @@ Access to documentation, credentials, and technical details of remote access sho Regular reviews should be performed to verify that information about remote access mechanisms is protected and not improperly disclosed or misused. -Mendix does not manage or oversee the protection of information about customer-specific remote access mechanisms. Responsibility rests entirely with the customer and their designated teams. \ No newline at end of file +Mendix does not manage or oversee the protection of information about customer-specific remote access mechanisms. Responsibility rests entirely with the customer and their designated teams. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1709.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1709.md index 07122fadbbb..96ad405fdc5 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1709.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1709.md @@ -65,4 +65,4 @@ Users can be logged out and disabled in the **Manage > Users > User Management** {{< figure src="/attachments/private-platform/nist-ac/nist-ac-1709-2.png" class="no-border" >}} -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-1709-3.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-1709-3.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac18.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac18.md index d22a250fd8c..fd75b43c763 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac18.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac18.md @@ -60,4 +60,4 @@ Infrastructure implementers and operators are responsible for configuring and ma Customers should regularly review wireless access configurations, maintain an inventory of authorized devices and users, and provide security awareness training on wireless access risks and procedures. -Mendix does not define, implement, or enforce wireless access controls within the Platform. All requirements and controls are managed by the customer and their implementation teams. \ No newline at end of file +Mendix does not define, implement, or enforce wireless access controls within the Platform. All requirements and controls are managed by the customer and their implementation teams. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1801.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1801.md index d6de8222988..e3f6fb2b1d0 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1801.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1801.md @@ -47,4 +47,4 @@ Responsibility for implementing these protections resides entirely with the cust ## Proof and Remarks -This control is not relevant for applications (level 7). \ No newline at end of file +This control is not relevant for applications (level 7). diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1803.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1803.md index a86c63c3551..71b6ef34a03 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1803.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1803.md @@ -46,4 +46,4 @@ Responsibility for managing, disabling, and auditing wireless networking capabil ## Proof and Remarks -This control is not relevant for applications (level 7). \ No newline at end of file +This control is not relevant for applications (level 7). diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac19.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac19.md index 9dc755586d5..b0a577bf24c 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac19.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac19.md @@ -93,4 +93,4 @@ The customer is solely responsible for compliance with mobile device access cont ## Proof and Remarks -This control is not relevant for applications (level 7). \ No newline at end of file +This control is not relevant for applications (level 7). diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1905.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1905.md index c6d210acd26..eefe835f2d1 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1905.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac1905.md @@ -56,4 +56,4 @@ Mendix recommends enterprise customers to leverage the appropriate device manage ## Proof and Remarks -Mendix does not select or manage mobile devices for customers. \ No newline at end of file +Mendix does not select or manage mobile devices for customers. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac20.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac20.md index ef35a6d0316..f1f9e84244e 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac20.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac20.md @@ -58,4 +58,4 @@ Customers should establish access authorization procedures and keep records of w ## Proof and Remarks -Mendix is not responsible for this task. Customers will be the implementer and the operator for their Mendix app and the supporting infrastructure. \ No newline at end of file +Mendix is not responsible for this task. Customers will be the implementer and the operator for their Mendix app and the supporting infrastructure. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac2001.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac2001.md index eaa992803c9..68d5977bb16 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac2001.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac2001.md @@ -49,4 +49,4 @@ The customer should verify the external information systems contain the necessar ## Proof and Remarks -Mendix is not responsible for this task. The infrastructure implementer and operator, as well as the app implementer and operator must implement these controls and enforce access restrictions for using external information systems according to the customer's policies. \ No newline at end of file +Mendix is not responsible for this task. The infrastructure implementer and operator, as well as the app implementer and operator must implement these controls and enforce access restrictions for using external information systems according to the customer's policies. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac2002.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac2002.md index eac62fe62fc..24015e40f7c 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac2002.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac2002.md @@ -46,4 +46,4 @@ Infrastructure implementers and operators are responsible for managing portable ## Proof and Remarks -Mendix is not responsible for this task. \ No newline at end of file +Mendix is not responsible for this task. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac21.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac21.md index 4fa36b28426..052d5b395fc 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac21.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac21.md @@ -65,4 +65,4 @@ Private Mendix Platform enables sharing Marketplace contents based on Company, O Private Mendix Platform supports sharing Mendix apps to groups and accessing apps through group membership: -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-21-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-21-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac22.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac22.md index f9050177970..8a2ec8d2d1f 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac22.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac22.md @@ -53,4 +53,4 @@ Management and control practices may include periodic scanning all Mendix soluti ## Proof and Remarks -Mendix is not responsible for this task. \ No newline at end of file +Mendix is not responsible for this task. diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac23.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac23.md index 43c163be1eb..b17e58d4fc1 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac23.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac23.md @@ -59,4 +59,4 @@ Private Mendix Platform is protected against data-mining attacks and vulnerabili Mendix app metrics, health and status via Grafana and Prometheus can be disabled: -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-23-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-23-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/au/_index.md b/content/en/docs/private-platform/nist-controls/au/_index.md index 537c4508d15..645028cdee5 100644 --- a/content/en/docs/private-platform/nist-controls/au/_index.md +++ b/content/en/docs/private-platform/nist-controls/au/_index.md @@ -12,4 +12,4 @@ simple_list: true Documents in this section provide more information about Private Mendix Platform's compliance with the Audit and Accountability (AU) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect. -In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. \ No newline at end of file +In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0203.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0203.md index d06b82ac124..89f24ef2fdf 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0203.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0203.md @@ -42,4 +42,4 @@ The customer should review and update the set of audited events periodically to ## Proof and Remarks -Mendix is not responsible for this task. The customer must review and update the audited events. \ No newline at end of file +Mendix is not responsible for this task. The customer must review and update the audited events. diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au03.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au03.md index ecbb3b5b932..0bc93c42dbc 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au03.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au03.md @@ -69,4 +69,4 @@ Private Mendix Platform displays activity logs when the detail level of the acti Private Mendix Platform displays activity logs when the detail level of the action log is set to **Complete**: -{{< figure src="/attachments/private-platform/nist-au/nist-au-03-4.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-au/nist-au-03-4.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0301.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0301.md index 6a4d8620c89..f368e536be2 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0301.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0301.md @@ -44,4 +44,4 @@ The customer should limit the additional audit information to only the informati ## Proof and Remarks -Mendix is not responsible for this task. The customer must decide what additional audit information is required. \ No newline at end of file +Mendix is not responsible for this task. The customer must decide what additional audit information is required. diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au04.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au04.md index 56af9cd419e..eb55588cc0f 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au04.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au04.md @@ -53,4 +53,4 @@ The customer should allocate sufficient audit storage capacity to avoid capacity ## Proof and Remarks -Mendix is not responsible for this task. The customer must define audit storage type and allocate storage capacity. \ No newline at end of file +Mendix is not responsible for this task. The customer must define audit storage type and allocate storage capacity. diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0401.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0401.md index 07686210268..41776e816c7 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0401.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0401.md @@ -77,4 +77,4 @@ Private Mendix Platform provides a setting for specifying the logging format (PD Private Mendix Platform provides a setting for specifying the duration in days for keeping logs in the database (with a maximum of 365): -{{< figure src="/attachments/private-platform/nist-au/nist-au-0401-3.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-au/nist-au-0401-3.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au05.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au05.md index 438ef6a3ff3..669a0158d02 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au05.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au05.md @@ -60,4 +60,4 @@ Private Mendix Platform provides the **Settings > Notification > Email** page to Private Mendix Platform provides the **Send email when any audit logging fails** setting on the **Settings > Activity Logs > Log Settings** page. The user must enable or disable this setting according to their requirements, and specify the email addresses that will receive the notification if the setting is toggled on: -{{< figure src="/attachments/private-platform/nist-au/nist-au-05-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-au/nist-au-05-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0601.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0601.md index c393aedf7d7..744ae1b2d24 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0601.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0601.md @@ -49,4 +49,4 @@ The customer should integrate audit review, analysis, and reporting processes t ## Proof and Remarks -Mendix is not responsible for this task. The customer must define audit storage type and allocate storage capacity. \ No newline at end of file +Mendix is not responsible for this task. The customer must define audit storage type and allocate storage capacity. diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0604.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0604.md index 89ec9debf46..5defab94a1e 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0604.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0604.md @@ -53,4 +53,4 @@ The customer should set up automation mechanisms for centralized reviews and ana Private Mendix Platform provides the **Settings > Activity Logs > Log Settings** page where customers can configure an external database to which logs must be written for centralized review and analysis: -{{< figure src="/attachments/private-platform/nist-au/nist-au-0604-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-au/nist-au-0604-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0610.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0610.md index 81aa5fcff0b..5411e2c49fd 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0610.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0610.md @@ -63,4 +63,4 @@ Private Mendix Platform displays activity logs when the detail level of the acti Private Mendix Platform displays activity logs when the detail level of the action log is set to **Complete**: -{{< figure src="/attachments/private-platform/nist-au/nist-au-03-4.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-au/nist-au-03-4.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au07.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au07.md index a8509f65f84..f9015392fd8 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au07.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au07.md @@ -63,4 +63,4 @@ Private Mendix Platform provides the **Create Custom Report** button to generate Private Mendix Platform provides the settings to configure the log detail level, file format, and date-time duration for custom report generation: -{{< figure src="/attachments/private-platform/nist-au/nist-au-07-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-au/nist-au-07-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0701.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0701.md index 7c67284db96..5457a2d9e71 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0701.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au0701.md @@ -22,7 +22,6 @@ The information system provides the capability to process audit records for even ### Supplemental Guidance - Events of interest can be identified by the content of specific audit record fields including, for example, identities of individuals, event types, event locations, event times, event dates, system resources involved, IP addresses involved, or information objects accessed. Organizations may define audit event criteria to any degree of granularity required, for example, locations selectable by general networking location (for example, by network or subnetwork) or selectable by specific information system component. The following controls are related to this control: @@ -49,4 +48,4 @@ Private Mendix Platform does not currently support automatically processing audi For more information, see the following documents: * [Private Mendix Platform Functionalities - Activity Logs](/private-mendix-platform/reference-guide/admin/company/#activity-logs) -* [Private Mendix Platform Functionalities - Log Settings](/private-mendix-platform/reference-guide/admin/company/#log-settings) \ No newline at end of file +* [Private Mendix Platform Functionalities - Log Settings](/private-mendix-platform/reference-guide/admin/company/#log-settings) diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au08.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au08.md index 15d01c6b9af..8f8d92184a0 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au08.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au08.md @@ -80,4 +80,4 @@ Private Mendix Platform provides a setting to configure the output for logged ti Private Mendix Platform displays logs with timestamps in milliseconds and the UTC offset *(-04:00)* in the customer-preferred time zone: -{{< figure src="/attachments/private-platform/nist-au/nist-au-08-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-au/nist-au-08-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au09.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au09.md index d905d9dfb7a..8a1bffcb492 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au09.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au09.md @@ -26,6 +26,7 @@ The information system protects audit information and audit tools from unauthori The audit information includes all information needed to successfully audit information system activity (for example, audit records, audit settings, and audit reports). This control focuses on technical protection of audit information. Physical protection of audit information is addressed by media protection controls and physical and environmental protection controls. The following controls are related to this control: + * AC-3 * AC-6 * MP-2 @@ -62,4 +63,4 @@ The customer should ensure that audit information and systems of record are prot Private Mendix Platform restricts the rights to access and view audit information. Only users with the Admin role are allowed to view this information: -{{< figure src="/attachments/private-platform/nist-au/nist-au-09-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-au/nist-au-09-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/cm/_index.md b/content/en/docs/private-platform/nist-controls/cm/_index.md index 1cd787daee9..4349ee786c4 100644 --- a/content/en/docs/private-platform/nist-controls/cm/_index.md +++ b/content/en/docs/private-platform/nist-controls/cm/_index.md @@ -12,4 +12,4 @@ simple_list: true Documents in this section provide more information about Private Mendix Platform's compliance with the Configuration Management (CM) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect. -In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. \ No newline at end of file +In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0401.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0401.md index 021fe6c627d..f1180f0e633 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0401.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0401.md @@ -54,4 +54,4 @@ To meet these requirements, the customer must carry out the following actions: 3. Vet all changes before production implementation. - The infrastructure operator and app operator must ensure all new versions and system changes are vetted as dictated by the customer before implementation in the operational environment. This includes conducting security impact assessments for flaws, weaknesses, incompatibility, and intentional malice, and documenting the results before promoting changes to production. \ No newline at end of file + The infrastructure operator and app operator must ensure all new versions and system changes are vetted as dictated by the customer before implementation in the operational environment. This includes conducting security impact assessments for flaws, weaknesses, incompatibility, and intentional malice, and documenting the results before promoting changes to production. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0601.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0601.md index 3da8912a470..7efdbbb60ec 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0601.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0601.md @@ -41,4 +41,4 @@ The Private Mendix Platform runs on customer-managed infrastructure, and configu * Customer - Determines which automated mechanisms are appropriate for security hardening configuration management. Defines the scope of information system components subject to centralized configuration management. Establishes policies, standards, and procedures governing configuration settings. * Infra Implementer - Implements and configures the selected automated mechanisms to manage infrastructure components. Ensures that configuration settings are applied consistently across all in-scope components. Integrates automated mechanisms with the target environment (for example, Private Mendix Platform infrastructure, underlying operating systems, databases, and network devices). -* Infra Operator - Operates and maintains automated configuration management mechanisms on an ongoing basis. Monitors compliance with established configuration baselines. Addresses configuration drift and remediates non-compliant settings. Verifies that configuration settings remain applied and effective through continuous monitoring or periodic assessments. \ No newline at end of file +* Infra Operator - Operates and maintains automated configuration management mechanisms on an ongoing basis. Monitors compliance with established configuration baselines. Addresses configuration drift and remediates non-compliant settings. Verifies that configuration settings remain applied and effective through continuous monitoring or periodic assessments. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm07.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm07.md index 49f9e3040d7..760e55b1af4 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm07.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm07.md @@ -93,4 +93,4 @@ The App Implementer is responsible for: * Configuring Mendix applications to use only approved integrations. * Removing unused modules and features from Mendix apps. * Implementing application-level access controls. -* Ensuring the app adheres to the principle of least functionality. \ No newline at end of file +* Ensuring the app adheres to the principle of least functionality. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0701.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0701.md index 4c4c509cead..7eb09411e36 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0701.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0701.md @@ -78,4 +78,4 @@ The App implementer is responsible for: * Updating application configurations to remove insecure protocols. * Removing deprecated or insecure integrations. * Ensuring the Mendix app only exposes required services. -* Testing application functionality after changes. \ No newline at end of file +* Testing application functionality after changes. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0702.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0702.md index 118984c1016..27ddb048b2d 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0702.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0702.md @@ -95,4 +95,4 @@ It is the responsibility of the App Operator to ensure ongoing compliance of the * Coordinate with customer for approval of new modules or updates. * Maintain application inventory and dependency tracking. * Report any compliance deviations to customer. -* Ensure running applications remain within approved execution boundaries. \ No newline at end of file +* Ensure running applications remain within approved execution boundaries. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0803.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0803.md index 72f5ff6117a..cc4604dc45a 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0803.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0803.md @@ -75,4 +75,4 @@ The customer is responsible for communicating the selected mechanisms and respon #### Ensure Ongoing Compliance -The customer should periodically review the effectiveness of the detection mechanisms and response actions, especially after system changes or new threat intelligence. The Infra Operator should provide regular reports on detections and actions taken, which the customer uses to verify compliance and adjust the strategy as needed. \ No newline at end of file +The customer should periodically review the effectiveness of the detection mechanisms and response actions, especially after system changes or new threat intelligence. The Infra Operator should provide regular reports on detections and actions taken, which the customer uses to verify compliance and adjust the strategy as needed. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm1001.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm1001.md index 896657ab1f8..9060c5ae744 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm1001.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm1001.md @@ -118,4 +118,4 @@ Ensure ongoing compliance of OSS components in the running Mendix app. The following figure shows the process flowchart for Open Source Software clearing at Mendix: -{{< figure src="/attachments/private-platform/nist-cm/nist-cm-1001-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-cm/nist-cm-1001-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/cp/_index.md b/content/en/docs/private-platform/nist-controls/cp/_index.md index a323aadd109..d360b32c42e 100644 --- a/content/en/docs/private-platform/nist-controls/cp/_index.md +++ b/content/en/docs/private-platform/nist-controls/cp/_index.md @@ -12,4 +12,4 @@ simple_list: true Documents in this section provide more information about Private Mendix Platform's compliance with the Contingency Planning (CP) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect. -In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. \ No newline at end of file +In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. diff --git a/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp02.md b/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp02.md index 5b41128ff20..4dc8cd26d0d 100644 --- a/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp02.md +++ b/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp02.md @@ -88,4 +88,4 @@ The following baseline practices are recommended to establish a resilient infras For more information about namespace-level backup and restore procedures, see [Use Velero to Back Up Mendix on Kubernetes Namespaces](/developerportal/deploy/private-cloud-velero/). -For more information about data migration, see [Migrating Data in Mendix on Kubernetes Environments (Preview)](/developerportal/deploy/private-cloud-data-transfer/). \ No newline at end of file +For more information about data migration, see [Migrating Data in Mendix on Kubernetes Environments (Preview)](/developerportal/deploy/private-cloud-data-transfer/). diff --git a/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp09.md b/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp09.md index 3ec326810c0..e74cc66772d 100644 --- a/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp09.md +++ b/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp09.md @@ -67,4 +67,4 @@ The following baseline practices are recommended to establish a resilient infras For more information about namespace-level backup and restore procedures, see [Use Velero to Back Up Mendix on Kubernetes Namespaces](/developerportal/deploy/private-cloud-velero/). -For more information about data migration, see [Migrating Data in Mendix on Kubernetes Environments (Preview)](/developerportal/deploy/private-cloud-data-transfer/). \ No newline at end of file +For more information about data migration, see [Migrating Data in Mendix on Kubernetes Environments (Preview)](/developerportal/deploy/private-cloud-data-transfer/). diff --git a/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp1002.md b/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp1002.md index e92400599eb..045df1a1fee 100644 --- a/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp1002.md +++ b/content/en/docs/private-platform/nist-controls/cp/pmp-nist-cp1002.md @@ -72,4 +72,4 @@ For more information about error handling, see [Error Handling in Microflows](/r For more information about namespace-level backup and restore procedures, see [Use Velero to Back Up Mendix on Kubernetes Namespaces](/developerportal/deploy/private-cloud-velero/). -For more information about data migration, see [Migrating Data in Mendix on Kubernetes Environments (Preview)](/developerportal/deploy/private-cloud-data-transfer/). \ No newline at end of file +For more information about data migration, see [Migrating Data in Mendix on Kubernetes Environments (Preview)](/developerportal/deploy/private-cloud-data-transfer/). diff --git a/content/en/docs/private-platform/nist-controls/ia/_index.md b/content/en/docs/private-platform/nist-controls/ia/_index.md index 8cc6d988c1d..7c24b6dba3f 100644 --- a/content/en/docs/private-platform/nist-controls/ia/_index.md +++ b/content/en/docs/private-platform/nist-controls/ia/_index.md @@ -12,4 +12,4 @@ simple_list: true Documents in this section provide more information about Private Mendix Platform's compliance with the Identification and Authentication (IA) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect. -In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. \ No newline at end of file +In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia04.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia04.md index 25fdd0cc432..86bc8345ba9 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia04.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia04.md @@ -89,4 +89,4 @@ Session timeout can be configured. {{< figure src="/attachments/private-platform/nist-ia/nist-ia-04-3.png" class="no-border" >}} -For more information about connecting to the customer's IdP, see [Private Mendix Platform Functionalities - System Administrators](/private-mendix-platform/reference-guide/admin/system/#identity--access). \ No newline at end of file +For more information about connecting to the customer's IdP, see [Private Mendix Platform Functionalities - System Administrators](/private-mendix-platform/reference-guide/admin/system/#identity--access). diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0404.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0404.md index 6985f7491e5..8611469b6d1 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0404.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0404.md @@ -43,7 +43,7 @@ The customer is responsible for implementing this control in an appropriate mann Defines the categorizations, groups, or tags used to classify individuals, and applies the corresponding metadata in accordance with organizational and security requirements. -#### Infra Implementer +#### Infra Implementer Ensures the customer's identity provider (IdP) supports the required categorizations, groups, or tags, and establishes secure, compliant integration between the infrastructure and the customer's IdP. @@ -53,4 +53,4 @@ Ensures the Mendix app correctly reads and applies individual account metadata a #### Infra Operator and App Operator -Jointly maintains ongoing alignment with the customer's requirements by performing regular updates to individual account metadata, IdP configurations, and supporting infrastructure, and addresses any changes in categorization or tagging needs over time. \ No newline at end of file +Jointly maintains ongoing alignment with the customer's requirements by performing regular updates to individual account metadata, IdP configurations, and supporting infrastructure, and addresses any changes in categorization or tagging needs over time. diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia05-1126.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia05-1126.md index 133baefc01c..c32b932fe88 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia05-1126.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia05-1126.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-051126-4.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ia/nist-ia-051126-4.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia05-1127.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia05-1127.md index 0cc8c9eb0f0..cac0218d5bc 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia05-1127.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia05-1127.md @@ -58,4 +58,4 @@ After the specified interval, the screen is locked, and the user must click the If the user remains idle after the screen is locked, after the specified interval, the user is logged out. -{{< figure src="/attachments/private-platform/nist-ia/nist-ia-051127-4.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ia/nist-ia-051127-4.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0501.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0501.md index 9edc155814b..cd2f2ebc829 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0501.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0501.md @@ -65,4 +65,4 @@ The App Implementer is responsible for ensuring that the Mendix app integrates w Private Mendix Platforms allows customers to define the required password complexity: -{{< figure src="/attachments/private-platform/nist-ia/nist-ia-05-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ia/nist-ia-05-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0502.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0502.md index 8ef17de736f..2ad0649b1dd 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0502.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0502.md @@ -65,4 +65,4 @@ For more information, refer to the following documents: * [Private Mendix Platform Functionalities - System Administrators](/private-mendix-platform/reference-guide/admin/system/#identity--access) * [OIDC SSO](/appstore/modules/oidc/) -* [SAML](/appstore/modules/saml/) \ No newline at end of file +* [SAML](/appstore/modules/saml/) diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0504.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0504.md index 425aacbfbc4..84459f66c99 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0504.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0504.md @@ -46,4 +46,4 @@ It is the responsibility of the Infra Implementer to ensure infrastructure integ It is the responsibility of the App Implementer to ensure the Mendix App integrates with the customer's IdP and strong password tooling. -It is the responsibility of the Infra Operator and App Operator to ensure ongoing integration with the customers IdP and strong password tooling throughout the lifecycle of the system. \ No newline at end of file +It is the responsibility of the Infra Operator and App Operator to ensure ongoing integration with the customers IdP and strong password tooling throughout the lifecycle of the system. diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0506.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0506.md index 5c82061d967..d5c7f9c1d16 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0506.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia0506.md @@ -40,4 +40,4 @@ It is the responsibility of the Infra Implementer to ensure the infrastructure e It is the responsibility of the App Implementer to ensure the Mendix App protects its information and authenticators at the appropriate level to handle the SC of the solution and to comply with the customer's directives. -It is the responsibility of the Infra Operator and the App Operator to ensure ongoing compliance as the SC of the solution changes or customer directives change. \ No newline at end of file +It is the responsibility of the Infra Operator and the App Operator to ensure ongoing compliance as the SC of the solution changes or customer directives change. diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia06.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia06.md index 0cf62729894..00b9b44bd0a 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia06.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia06.md @@ -57,4 +57,4 @@ It is the responsibility of the App Operator to ensure that changes to the Mendi Below is a description of the approach mechanism: 1. When a new user account is created, its password is encrypted by Bcrypt algorithm (a one-way hashing process to store password safely). In a one-way process, an encrypted hashing password can never be calculated reversely to its prior string before encryption. -2. During login, the password which the user enters is hashed by the same algorithm. After that, the hashed input string is compared to the encrypted password to proceed with authentication. \ No newline at end of file +2. During login, the password which the user enters is hashed by the same algorithm. After that, the hashed input string is compared to the encrypted password to proceed with authentication. diff --git a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia07.md b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia07.md index 3e90723bfdb..35c558e4ecd 100644 --- a/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia07.md +++ b/content/en/docs/private-platform/nist-controls/ia/pmp-nist-ia07.md @@ -75,4 +75,4 @@ IdP SAML configuration in Private Mendix Platform: SAML client configuration in Private Mendix Platform: -{{< figure src="/attachments/private-platform/nist-ia/nist-ia-07-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ia/nist-ia-07-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ir/_index.md b/content/en/docs/private-platform/nist-controls/ir/_index.md index f2b5fb00eec..1860dd934b4 100644 --- a/content/en/docs/private-platform/nist-controls/ir/_index.md +++ b/content/en/docs/private-platform/nist-controls/ir/_index.md @@ -12,4 +12,4 @@ simple_list: true Documents in this section provide more information about Private Mendix Platform's compliance with the Incident Response (IR) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect. -In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. \ No newline at end of file +In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. diff --git a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir03.md b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir03.md index 5c2d5014127..186e5ea95c8 100644 --- a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir03.md +++ b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir03.md @@ -43,4 +43,4 @@ The customer is responsible for planning, executing, evaluating, and documenting Mendix is willing to collaborate on incident response tests in alignment with our support organization. Please contact Mendix Support to coordinate an incident response test. -Certain incident responses, such as penetration tests against Mendix public capabilities, require additional signed documentation as per the Mendix Terms of Service and other agreements. It is the customer's responsibility to review these documents and comply with their requirements before executing the covered incident testing. \ No newline at end of file +Certain incident responses, such as penetration tests against Mendix public capabilities, require additional signed documentation as per the Mendix Terms of Service and other agreements. It is the customer's responsibility to review these documents and comply with their requirements before executing the covered incident testing. diff --git a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0401.md b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0401.md index 4fb3b03eb18..b65d8932062 100644 --- a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0401.md +++ b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0401.md @@ -40,4 +40,4 @@ It is the responsibility of the Infra Implementer to integrate these tools into It is the responsibility of the App Implementer to integrate these tools into the Mendix App as directed by the Customer. -It is the responsibility of the Infra Operator and App Operator to ensure proper ongoing integration of automated incident response mechanisms with the infrastructure and Mendix App throughout the lifecycle of the system. \ No newline at end of file +It is the responsibility of the Infra Operator and App Operator to ensure proper ongoing integration of automated incident response mechanisms with the infrastructure and Mendix App throughout the lifecycle of the system. diff --git a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0406.md b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0406.md index 8b7d4b6a632..6f31ad621c0 100644 --- a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0406.md +++ b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0406.md @@ -36,4 +36,4 @@ The customer is responsible for defining incident handling capabilities for insi It is the responsibility of the customer to dictate incident handling capabilities for insider threats. -It is the responsibility of the Infra Implementer, and App Implementer to ensure the Mendix App, infrastructure, and components support the insider threat incident handling capabilities as dictated by the customer. \ No newline at end of file +It is the responsibility of the Infra Implementer, and App Implementer to ensure the Mendix App, infrastructure, and components support the insider threat incident handling capabilities as dictated by the customer. diff --git a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0408.md b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0408.md index a2a48709b83..b53c9ae4ca2 100644 --- a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0408.md +++ b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0408.md @@ -38,4 +38,4 @@ The customer should establish and maintain coordination with relevant external o The customer should ensure that appropriate processes and agreements are in place for the timely correlation and sharing of incident information, enabling a broader, cross-organizational view of threats and incidents. -Additionally, the customer should leverage insights gained from external collaboration to enhance situational awareness, improve response effectiveness, and strengthen overall risk management across the organization’s operations, assets, and personnel. \ No newline at end of file +Additionally, the customer should leverage insights gained from external collaboration to enhance situational awareness, improve response effectiveness, and strengthen overall risk management across the organization’s operations, assets, and personnel. diff --git a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0501.md b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0501.md index 0bf5c1f082c..391c1187a6f 100644 --- a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0501.md +++ b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0501.md @@ -49,4 +49,4 @@ It is the responsibility of the App Implementer to integrate the Mendix app with It is the responsibility of the Infra Operator to ensure the infrastructure and Private Mendix Platform remain integrated with the automated security incident mechanisms dictated by the customer and App Operator to do the same for the Mendix app. -It is also the responsibility of the Infra Operator and App Operator to respond to changes to the automated security incident mechanisms dictated by the customer as well as infrastructure and Mendix App changes. \ No newline at end of file +It is also the responsibility of the Infra Operator and App Operator to respond to changes to the automated security incident mechanisms dictated by the customer as well as infrastructure and Mendix App changes. diff --git a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0601.md b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0601.md index a82d6cb1d07..6707ac23c3d 100644 --- a/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0601.md +++ b/content/en/docs/private-platform/nist-controls/ir/pmp-nist-ir0601.md @@ -42,4 +42,4 @@ It is the responsibility of the Infra Implementer to integrate the infrastructur It is the responsibility of the App Implementer to ensure the Mendix App is integrated with the automated security incident tools dictated by the customer. -It is the responsibility of the Infra Operator and App Operator to ensure successful ongoing integration with the Customer's automated security incident tools. \ No newline at end of file +It is the responsibility of the Infra Operator and App Operator to ensure successful ongoing integration with the Customer's automated security incident tools. diff --git a/content/en/docs/private-platform/nist-controls/pl/_index.md b/content/en/docs/private-platform/nist-controls/pl/_index.md index f0dcde8cca4..3c1b5b5114f 100644 --- a/content/en/docs/private-platform/nist-controls/pl/_index.md +++ b/content/en/docs/private-platform/nist-controls/pl/_index.md @@ -12,4 +12,4 @@ simple_list: true Documents in this section provide more information about Private Mendix Platform's compliance with the Planning (PL) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect. -In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. \ No newline at end of file +In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. diff --git a/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl01.md b/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl01.md index e4216f082cf..44a082f836a 100644 --- a/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl01.md +++ b/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl01.md @@ -64,4 +64,4 @@ To meet these requirements, the customer must carry out the following actions: * Maintain ongoing communication with operations teams. - Establish procedures to ensure that the Infra Operator and App Operator keep the customer continuously informed of security planning implications throughout the entire lifecycle of the Mendix solution. This includes implementing regular reporting mechanisms, change notification processes, and feedback loops to capture operational insights that may affect security planning policies and procedures as outlined in NIST SP 800-100. \ No newline at end of file + Establish procedures to ensure that the Infra Operator and App Operator keep the customer continuously informed of security planning implications throughout the entire lifecycle of the Mendix solution. This includes implementing regular reporting mechanisms, change notification processes, and feedback loops to capture operational insights that may affect security planning policies and procedures as outlined in NIST SP 800-100. diff --git a/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl02.md b/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl02.md index 614fe98fdaa..b61a2f8f67a 100644 --- a/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl02.md +++ b/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl02.md @@ -96,4 +96,4 @@ In order to demonstrate compliance, the customer is expected to implement the me * Implement review, update, and protection procedures. - Establish organization-defined frequencies for reviewing the security plan in accordance with NIST SP 800-53 Rev 5, and implement procedures to update the plan to address changes to the information system, environment of operation, or problems identified during plan implementation or security control assessments. Protect the security plan from unauthorized disclosure and modification through appropriate access controls and handling procedures, ensuring all stakeholders maintain current versions throughout the Mendix solution lifecycle. \ No newline at end of file + Establish organization-defined frequencies for reviewing the security plan in accordance with NIST SP 800-53 Rev 5, and implement procedures to update the plan to address changes to the information system, environment of operation, or problems identified during plan implementation or security control assessments. Protect the security plan from unauthorized disclosure and modification through appropriate access controls and handling procedures, ensuring all stakeholders maintain current versions throughout the Mendix solution lifecycle. diff --git a/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl0203.md b/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl0203.md index 18e0a026045..c218280dddf 100644 --- a/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl0203.md +++ b/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl0203.md @@ -55,4 +55,4 @@ The following steps define the customer's obligations for this control: * Coordinate with Mendix for activities impacting Mendix products and systems. - Plan and coordinate with Mendix any security activities that would directly impact Mendix products and solutions or customers on publicly available Mendix systems, such as phishing tests, penetration tests, vulnerability scanning, or other security assessments. Provide advance notice to Mendix in accordance with terms of service or support agreements to ensure proper coordination and minimize disruption to services. \ No newline at end of file + Plan and coordinate with Mendix any security activities that would directly impact Mendix products and solutions or customers on publicly available Mendix systems, such as phishing tests, penetration tests, vulnerability scanning, or other security assessments. Provide advance notice to Mendix in accordance with terms of service or support agreements to ensure proper coordination and minimize disruption to services. diff --git a/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl08.md b/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl08.md index db84d3d8682..57f7d7c8d58 100644 --- a/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl08.md +++ b/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl08.md @@ -72,4 +72,4 @@ To meet these requirements, the customer must carry out the following actions: * Coordinate architecture changes and maintain current documentation. - Establish procedures to ensure that the Infra Operator and App Operator coordinate with the Customer to reflect planned information security architecture changes in the security plan, security CONOPS, and other organizational documents including procurements and acquisitions. Review and update the information security architecture at organization-defined frequencies to reflect updates in the enterprise architecture, ensuring coordination with the Senior Agency Official for Privacy (SAOP)/Chief Privacy Officer (CPO) as described in NIST SP 800-53 Rev 5. \ No newline at end of file + Establish procedures to ensure that the Infra Operator and App Operator coordinate with the Customer to reflect planned information security architecture changes in the security plan, security CONOPS, and other organizational documents including procurements and acquisitions. Review and update the information security architecture at organization-defined frequencies to reflect updates in the enterprise architecture, ensuring coordination with the Senior Agency Official for Privacy (SAOP)/Chief Privacy Officer (CPO) as described in NIST SP 800-53 Rev 5. diff --git a/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl0801.md b/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl0801.md index 099e42039ec..58abbde1909 100644 --- a/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl0801.md +++ b/content/en/docs/private-platform/nist-controls/pl/pmp-nist-pl0801.md @@ -57,4 +57,4 @@ The following steps define the customer's obligations for this control: * Maintain ongoing compliance through Operations teams. - Establish procedures for the Infra Operator and App Operator to ensure ongoing compliance with the defense-in-depth controls as dictated by the Customer throughout the Mendix solution lifecycle. Implement monitoring, validation, and update processes to verify that allocated security safeguards continue to operate in a coordinated and mutually reinforcing manner, adjusting configurations as needed to maintain effectiveness against evolving threats while preventing safeguard interference. \ No newline at end of file + Establish procedures for the Infra Operator and App Operator to ensure ongoing compliance with the defense-in-depth controls as dictated by the Customer throughout the Mendix solution lifecycle. Implement monitoring, validation, and update processes to verify that allocated security safeguards continue to operate in a coordinated and mutually reinforcing manner, adjusting configurations as needed to maintain effectiveness against evolving threats while preventing safeguard interference. diff --git a/content/en/docs/private-platform/nist-controls/ps/_index.md b/content/en/docs/private-platform/nist-controls/ps/_index.md index 8630f5098da..8e2edcc2c31 100644 --- a/content/en/docs/private-platform/nist-controls/ps/_index.md +++ b/content/en/docs/private-platform/nist-controls/ps/_index.md @@ -12,4 +12,4 @@ simple_list: true Documents in this section provide more information about Private Mendix Platform's compliance with the Personnel Security (PS) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect. -In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. \ No newline at end of file +In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. diff --git a/content/en/docs/private-platform/nist-controls/ps/pmp-nist-ps02.md b/content/en/docs/private-platform/nist-controls/ps/pmp-nist-ps02.md index d375f2a6d22..2cec1a341b6 100644 --- a/content/en/docs/private-platform/nist-controls/ps/pmp-nist-ps02.md +++ b/content/en/docs/private-platform/nist-controls/ps/pmp-nist-ps02.md @@ -60,4 +60,4 @@ To meet these requirements, the customer must carry out the following actions: * Review and update position risk designations. - Implement a documented process to review and update position risk designations at organization-defined frequencies, ensuring that changes in job responsibilities, threat landscape, or organizational policy are reflected. The Customer must direct Infra Implementer, App Implementer, Infra Operator, and App Operator to maintain ongoing compliance with personnel directives throughout the system's lifecycle \ No newline at end of file + Implement a documented process to review and update position risk designations at organization-defined frequencies, ensuring that changes in job responsibilities, threat landscape, or organizational policy are reflected. The Customer must direct Infra Implementer, App Implementer, Infra Operator, and App Operator to maintain ongoing compliance with personnel directives throughout the system's lifecycle diff --git a/content/en/docs/private-platform/nist-controls/ps/pmp-nist-ps0303.md b/content/en/docs/private-platform/nist-controls/ps/pmp-nist-ps0303.md index 2c4b0f91fe0..23bf3d394de 100644 --- a/content/en/docs/private-platform/nist-controls/ps/pmp-nist-ps0303.md +++ b/content/en/docs/private-platform/nist-controls/ps/pmp-nist-ps0303.md @@ -51,4 +51,4 @@ In order to demonstrate compliance, the customer is expected to implement the me * Maintain ongoing personnel and system compliance. - Direct Infra Operator and App Operator to ensure continuous compliance with screening requirements and access authorizations throughout the system's lifecycle, including periodic re-verification of personnel credentials and access rights. The Customer must establish procedures for revoking access when personnel no longer meet screening criteria or when their official government duties change, ensuring that special protection requirements remain enforced at all times. \ No newline at end of file + Direct Infra Operator and App Operator to ensure continuous compliance with screening requirements and access authorizations throughout the system's lifecycle, including periodic re-verification of personnel credentials and access rights. The Customer must establish procedures for revoking access when personnel no longer meet screening criteria or when their official government duties change, ensuring that special protection requirements remain enforced at all times. diff --git a/content/en/docs/private-platform/nist-controls/ra/_index.md b/content/en/docs/private-platform/nist-controls/ra/_index.md index ea077e85711..250c2533510 100644 --- a/content/en/docs/private-platform/nist-controls/ra/_index.md +++ b/content/en/docs/private-platform/nist-controls/ra/_index.md @@ -12,4 +12,4 @@ simple_list: true Documents in this section provide more information about Private Mendix Platform's compliance with the Risk Assessment (RA) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect. -In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. \ No newline at end of file +In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. diff --git a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra01.md b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra01.md index cfed6a3891b..bb12951e3c8 100644 --- a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra01.md +++ b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra01.md @@ -64,4 +64,4 @@ To meet these requirements, the customer must carry out the following actions: * Maintain ongoing policy reviews and updates. - Direct Infra Operator and App Operator to ensure ongoing collaboration on changes to the risk assessment policy and procedure impacts of the Mendix solution throughout its lifecycle. The Customer must establish organization-defined frequencies for reviewing and updating risk assessment policies and procedures, ensuring they remain aligned with the organizational risk management strategy and reflect changes in the threat landscape, federal requirements, and system environment. \ No newline at end of file + Direct Infra Operator and App Operator to ensure ongoing collaboration on changes to the risk assessment policy and procedure impacts of the Mendix solution throughout its lifecycle. The Customer must establish organization-defined frequencies for reviewing and updating risk assessment policies and procedures, ensuring they remain aligned with the organizational risk management strategy and reflect changes in the threat landscape, federal requirements, and system environment. diff --git a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra02.md b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra02.md index 4bf655a3480..467403c8487 100644 --- a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra02.md +++ b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra02.md @@ -61,4 +61,4 @@ To meet these requirements, the customer must carry out the following actions: * Maintain ongoing security categorization throughout the lifecycle. - Direct both App Operator and Infra Operators to provide ongoing collaboration around any impacts to the security categorization over the system's lifecycle. This includes reporting significant changes to the application, data processed, or the underlying infrastructure (e.g., architectural shifts or changes in cloud services). The customer must establish procedures to review and update the security categorization at organization-defined frequencies or whenever operational changes occur, ensuring the categorization remains accurate and current. \ No newline at end of file + Direct both App Operator and Infra Operators to provide ongoing collaboration around any impacts to the security categorization over the system's lifecycle. This includes reporting significant changes to the application, data processed, or the underlying infrastructure (e.g., architectural shifts or changes in cloud services). The customer must establish procedures to review and update the security categorization at organization-defined frequencies or whenever operational changes occur, ensuring the categorization remains accurate and current. diff --git a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra03.md b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra03.md index 4f976cf8b43..1212c593b29 100644 --- a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra03.md +++ b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra03.md @@ -65,4 +65,4 @@ To meet these requirements, the customer must carry out the following actions: * Maintain ongoing risk assessment throughout the lifecycle. - Direct all parties to provide ongoing collaboration on risk assessments throughout the lifecycle of the Mendix solution, ensuring risk assessments are reviewed at organization-defined frequencies and updated whenever significant changes occur to the information system, environment of operation, threat landscape, or other conditions that may impact the security state. The Customer must ensure risk assessments remain current and inform security control selection, implementation, assessment, authorization, and monitoring decisions. \ No newline at end of file + Direct all parties to provide ongoing collaboration on risk assessments throughout the lifecycle of the Mendix solution, ensuring risk assessments are reviewed at organization-defined frequencies and updated whenever significant changes occur to the information system, environment of operation, threat landscape, or other conditions that may impact the security state. The Customer must ensure risk assessments remain current and inform security control selection, implementation, assessment, authorization, and monitoring decisions. diff --git a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra05.md b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra05.md index 2b1f7e5df15..eb0cfcfc4f7 100644 --- a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra05.md +++ b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra05.md @@ -129,4 +129,4 @@ The following screenshots shows an example of a Runtime scan: The following screenshots shows an example of a Studio Pro scan: -{{< figure src="/attachments/private-platform/nist-ra/nist-ra-05-3.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ra/nist-ra-05-3.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra0503.md b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra0503.md index f3f3f392c68..8e2c9883a21 100644 --- a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra0503.md +++ b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra0503.md @@ -44,4 +44,4 @@ To meet these requirements, the customer must carry out the following actions: * Maintain comprehensive coverage throughout the lifecycle. - Direct Infra Implementer, App Implementer, Infra Operator, and App Operator to ensure appropriate breadth and depth of coverage is maintained throughout the lifecycle of the Mendix solution. The Customer must regularly review coverage reports, identify and remediate coverage gaps, update scanning procedures when new components are added or system architecture changes, and ensure all critical system components remain within the scope of vulnerability scanning activities. \ No newline at end of file + Direct Infra Implementer, App Implementer, Infra Operator, and App Operator to ensure appropriate breadth and depth of coverage is maintained throughout the lifecycle of the Mendix solution. The Customer must regularly review coverage reports, identify and remediate coverage gaps, update scanning procedures when new components are added or system architecture changes, and ensure all critical system components remain within the scope of vulnerability scanning activities. diff --git a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra0505.md b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra0505.md index 99150c008ba..0310abea5c4 100644 --- a/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra0505.md +++ b/content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra0505.md @@ -48,4 +48,4 @@ To meet these requirements, the customer must carry out the following actions: * Maintain privileged access throughout lifecycle. - Direct the App Implementer to ensure the customer's identified vulnerability scanning tools have appropriate privileged access to the Mendix App for effective application vulnerability scanning, and require Infra Operator and App Operator to ensure scanning tools continue to have appropriate privileged access throughout the lifecycle. The customer must regularly review and validate privileged access authorizations for vulnerability scanning, ensuring credentials remain current, access remains properly controlled, and privileged scanning activities are monitored and audited. \ No newline at end of file + Direct the App Implementer to ensure the customer's identified vulnerability scanning tools have appropriate privileged access to the Mendix App for effective application vulnerability scanning, and require Infra Operator and App Operator to ensure scanning tools continue to have appropriate privileged access throughout the lifecycle. The customer must regularly review and validate privileged access authorizations for vulnerability scanning, ensuring credentials remain current, access remains properly controlled, and privileged scanning activities are monitored and audited. diff --git a/content/en/docs/private-platform/nist-controls/sa/_index.md b/content/en/docs/private-platform/nist-controls/sa/_index.md index 2d6d960e8e5..16343509c3e 100644 --- a/content/en/docs/private-platform/nist-controls/sa/_index.md +++ b/content/en/docs/private-platform/nist-controls/sa/_index.md @@ -12,4 +12,4 @@ simple_list: true Documents in this section provide more information about Private Mendix Platform's compliance with the System and Services Acquisition (SA) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect. -In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. \ No newline at end of file +In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa02.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa02.md index 53615d47b6b..cef8a58ebba 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa02.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa02.md @@ -59,4 +59,4 @@ To meet these requirements, the customer must carry out the following actions: 3. Collect resource requirements from implementation and operations teams. - Establish a formal process to collect input from the Infra Implementer, App Implementer, Infra Operator, and App Operator regarding the resources needed to properly protect the Mendix solution over its lifecycle. Ensure this input informs capital planning decisions, budgeting allocations, and resource distribution to support comprehensive security requirements throughout all phases of the system development lifecycle and ongoing operations. \ No newline at end of file + Establish a formal process to collect input from the Infra Implementer, App Implementer, Infra Operator, and App Operator regarding the resources needed to properly protect the Mendix solution over its lifecycle. Ensure this input informs capital planning decisions, budgeting allocations, and resource distribution to support comprehensive security requirements throughout all phases of the system development lifecycle and ongoing operations. diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa03.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa03.md index 14980a8c559..6e9b83be73e 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa03.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa03.md @@ -67,4 +67,4 @@ To meet these requirements, the customer must carry out the following actions: 3. Establish direct SDLC compliance across all implementation and operations roles. - Establish clear direction for how the Infra Implementer must deliver the infrastructure and Private Mendix Platform, how the App Implementer must deliver Mendix applications, how the Infra Operator must deliver infrastructure changes, and how the App Operator must deliver application changes—all in compliance with the customer-defined SDLC. Ensure all parties appropriately incorporate information security concerns at each phase as directed by the Customer, provide input on resources needed to support SDLC compliance, and maintain security considerations throughout the entire lifecycle of the Mendix solution. \ No newline at end of file + Establish clear direction for how the Infra Implementer must deliver the infrastructure and Private Mendix Platform, how the App Implementer must deliver Mendix applications, how the Infra Operator must deliver infrastructure changes, and how the App Operator must deliver application changes—all in compliance with the customer-defined SDLC. Ensure all parties appropriately incorporate information security concerns at each phase as directed by the Customer, provide input on resources needed to support SDLC compliance, and maintain security considerations throughout the entire lifecycle of the Mendix solution. diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa04.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa04.md index 475ad38cc9b..6489e64c21e 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa04.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa04.md @@ -55,4 +55,4 @@ Mendix makes Compliance Certifications (for example, SOC2, ISO 27001) available {{% alert color="info" %}} Customers and prospects can request access to the latest SOC2 report using [Conveyor](https://app.conveyor.com/profile/mendix). -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0401.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0401.md index 7125ba472a3..c2dd707b9bd 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0401.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0401.md @@ -118,4 +118,4 @@ As a low-code management platform built on Mendix, Private Mendix Platform provi * Session timeout management - To mitigate the risk of unauthorized access through unattended workstations, Private Mendix Platform enforces an inactivity session timeout. The Platform monitors user activity and automatically terminates or locks the session after a predefined period of inactivity. This ensures that security tokens are invalidated when not in use, preventing long-lived session exploitation. - {{< figure src="/attachments/private-platform/nist-sa/nist-sa-0401-7.png" class="no-border" >}} \ No newline at end of file + {{< figure src="/attachments/private-platform/nist-sa/nist-sa-0401-7.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0402.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0402.md index e36f2e7a91e..63e01b58842 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0402.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0402.md @@ -98,4 +98,4 @@ Portunus for Private Mendix Platform is a newly-developed component. It can be i * Infrastructure as Code (IaC) - The Platform infrastructure is defined and managed using tools such as Terraform and Helm charts. These artifacts represent the intended system configuration and support consistent and repeatable deployments. The infra implementer is responsible for the required configuration. - {{< figure src="/attachments/private-platform/nist-sa/nist-sa-0402-2.png" class="no-border" >}} \ No newline at end of file + {{< figure src="/attachments/private-platform/nist-sa/nist-sa-0402-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0407.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0407.md index 62adfaccc32..913aff7595c 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0407.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0407.md @@ -110,4 +110,4 @@ The Studio Pro core team has validated these capabilities specifically for the W #### Customer Scope (Shared Responsibility) -The customer is responsible for ensuring that the developer's local workstations or Virtual Desktop Infrastructure (VDI) are configured in FIPS-compliant mode and run on supported Windows versions. \ No newline at end of file +The customer is responsible for ensuring that the developer's local workstations or Virtual Desktop Infrastructure (VDI) are configured in FIPS-compliant mode and run on supported Windows versions. diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0408.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0408.md index 7125378f317..99d67816dfc 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0408.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0408.md @@ -80,4 +80,4 @@ Mendix maintains several comprehensive reports and audits, including a SOC2 Type {{% alert color="info" %}} Customers and prospects can request access to our latest audits and certifications using [Conveyor](https://app.conveyor.com/profile/mendix). -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0409.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0409.md index 49536d00bac..42bf313240a 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0409.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0409.md @@ -84,4 +84,4 @@ Mendix maintains a comprehensive SOC2 Type II report that independently validate {{% alert color="info" %}} Customers and prospects can request access to the latest SOC2 report using [Conveyor](https://app.conveyor.com/profile/mendix). -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0410.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0410.md index e06aff2417b..91b0b38bb48 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0410.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa0410.md @@ -75,4 +75,4 @@ The toggle to enable or disable local user sign-ups is available at **Settings > ### Protocol Flexibility and Compliance -By providing native support for industry-standard protocols and a mechanism to eliminate local credential bypass, Private Mendix Platform offloads PIV credential validation to the customer's approved infrastructure while ensuring the integrity of the end-to-end authentication process. \ No newline at end of file +By providing native support for industry-standard protocols and a mechanism to eliminate local credential bypass, Private Mendix Platform offloads PIV credential validation to the customer's approved infrastructure while ensuring the integrity of the end-to-end authentication process. diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa05.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa05.md index d4661da072c..00dcee856b6 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa05.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa05.md @@ -94,4 +94,4 @@ The organization obtains administrator and user documentation for the informatio Customers and prospects can request access to the latest SOC2 report using [Conveyor](https://app.conveyor.com/profile/mendix). {{% /alert %}} -* Implementation verification - This external guidance is validated against the internal EKS Deployment Manifests to ensure alignment with organizational security requirements (for example, restricted ports and localized data processing). \ No newline at end of file +* Implementation verification - This external guidance is validated against the internal EKS Deployment Manifests to ensure alignment with organizational security requirements (for example, restricted ports and localized data processing). diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa10.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa10.md index a7b23f12614..38ab62e018b 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa10.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa10.md @@ -99,4 +99,4 @@ The organization requires the developer of the information system, system compon {{% alert color="info" %}} Customers and prospects can request access to the latest SOC2 report using [Conveyor](https://app.conveyor.com/profile/mendix). - {{% /alert %}} \ No newline at end of file + {{% /alert %}} diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1001.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1001.md index 5b81294b73d..b2b9ba14598 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1001.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1001.md @@ -84,4 +84,4 @@ The organization requires the developer of the information system, system compon {{% alert color="info" %}} While deployment is initiated through versioned tags (for example, `v1.2.3`), the organization captures and logs the unique Image Digest (SHA256) automatically generated by the Mendix Official Registry during the initial pull. By referencing this immutable digest in our deployment records, we ensure that the software image remains untampered and consistent with the vendor-certified baseline throughout its lifecycle. -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1101.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1101.md index 30de31b5009..82ab3d3718d 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1101.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1101.md @@ -92,4 +92,4 @@ Customers and prospects can request access to the latest SOC2 report using [Conv * Customer (app and infra) - The App Operator and Infra Operator use tools like Sigrid and Snyk to generate periodic security and quality reports. These reports identify common flaws in the customer's Mendix Apps, container images, and IaC files. * Review and remediation process - There is a defined process to review these scan reports on a regular basis. High-severity vulnerabilities or critical weaknesses identified by Snyk or Sigrid are prioritized for remediation. -* Evidence records - Historical scan reports and snapshots from the Sigrid and Snyk dashboards are maintained as audit evidence. These records prove that the organization proactively identifies flaws and tracks their resolution over time. \ No newline at end of file +* Evidence records - Historical scan reports and snapshots from the Sigrid and Snyk dashboards are maintained as audit evidence. These records prove that the organization proactively identifies flaws and tracks their resolution over time. diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1102.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1102.md index a50291ec1fc..61102a39129 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1102.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1102.md @@ -86,4 +86,4 @@ The organization requires the developer of the information system, system compon {{< figure src="/attachments/private-platform/nist-sa/nist-sa-0408-3.png" class="no-border" >}} - For an example release note showing compliant vulnerability fixes, see [Private Mendix Platform 2.0: Fixes](/releasenotes/private-platform/2-0/#fixes). \ No newline at end of file + For an example release note showing compliant vulnerability fixes, see [Private Mendix Platform 2.0: Fixes](/releasenotes/private-platform/2-0/#fixes). diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1108.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1108.md index c389116dbc5..82b57c92c55 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1108.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa1108.md @@ -61,4 +61,4 @@ The organization requires the developer of the information system, system compon {{< figure src="/attachments/private-platform/nist-sa/nist-sa-0408-3.png" alt="Snapshot of the" class="no-border" >}} - For an example release note showing compliant vulnerability fixes, see [Private Mendix Platform 2.0: Fixes](/releasenotes/private-platform/2-0/#fixes). \ No newline at end of file + For an example release note showing compliant vulnerability fixes, see [Private Mendix Platform 2.0: Fixes](/releasenotes/private-platform/2-0/#fixes). diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa12.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa12.md index b748cc52da9..2193e1b09b3 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa12.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa12.md @@ -139,4 +139,4 @@ Mendix is certified with the following security certifications and Attestations. To know about other components customers are dependent on, and what licenses they make use of, customers can [generate the SBOM of the app](/refguide/sbom-generation/). -The customers can additionally protect their supply chain by [scanning marketplace bundles](/private-mendix-platform/reference-guide/admin/company/#import-content) before importing them from the public Mendix Marketplace. \ No newline at end of file +The customers can additionally protect their supply chain by [scanning marketplace bundles](/private-mendix-platform/reference-guide/admin/company/#import-content) before importing them from the public Mendix Marketplace. diff --git a/content/en/docs/private-platform/nist-controls/sc/_index.md b/content/en/docs/private-platform/nist-controls/sc/_index.md index 4da3c1b5973..7846089f534 100644 --- a/content/en/docs/private-platform/nist-controls/sc/_index.md +++ b/content/en/docs/private-platform/nist-controls/sc/_index.md @@ -12,4 +12,4 @@ simple_list: true Documents in this section provide more information about Private Mendix Platform's compliance with the System and Communications Protection (SC) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect. -In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. \ No newline at end of file +In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below. diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc02.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc02.md index 20cd69f1686..1e30877c211 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc02.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc02.md @@ -84,4 +84,4 @@ The Admin home page showing all available admin actions: The User home page showing only actions available to users: -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-02-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-02-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc04.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc04.md index 95c310c66bb..85e2c77d29d 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc04.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc04.md @@ -99,4 +99,4 @@ Private Mendix Platform database: Application database: -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-04-4.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-04-4.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc07.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc07.md index 5f6b2ba53d7..c9df4595a48 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc07.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc07.md @@ -102,4 +102,4 @@ Boundary protection is maintained by limiting external system boundaries to a ma The cluster-wide `PeerAuthentication` manifest (named default in the `istio-system` namespace) enforces a `Global STRICT mTLS` policy. This ensures that all internal communications across all namespaces are encrypted and authenticated, effectively preventing unauthorized or unencrypted information transfer at the internal system boundaries. -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-07-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-07-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0710.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0710.md index 7c23e4be292..71ea5013ad9 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0710.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0710.md @@ -84,4 +84,4 @@ The presence of the `BlackHoleCluster` and `PassthroughCluster` within the Envoy The application pod is in full synchronization with the Istio control plane, ensuring all traffic is intercepted by a managed interface governed by current security configurations. -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-0710-3.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-0710-3.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0711.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0711.md index 981c0a52129..02fb51fb486 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0711.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0711.md @@ -76,4 +76,4 @@ Organizations should select appropriate tools and solutions to control and manag ## Proof and Remarks -Mendix is not responsible for this task. \ No newline at end of file +Mendix is not responsible for this task. diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0712.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0712.md index 1f61fbb8d63..671b81f5fe4 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0712.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0712.md @@ -79,4 +79,4 @@ An AWS security group configured to allow traffic only on ports 80 and 443: Kubernetes security contexts for restricting container capabilities: -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-0712-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-0712-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0714.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0714.md index d2d2eb86454..f4334e13df2 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0714.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0714.md @@ -64,4 +64,4 @@ Physical security measures include: ## Proof and Remarks -Mendix is not responsible for this task. \ No newline at end of file +Mendix is not responsible for this task. diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc08.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc08.md index 6249383f402..f2b10ffb7f6 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc08.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc08.md @@ -96,4 +96,4 @@ Mendix supports encryption at rest. It can be configured through the following s * For Azure, see [Runtime Customization](/refguide/custom-settings/#azure-blob) * For RDS, refer to the following screenshot: -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-08-3.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-08-3.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0801.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0801.md index e8ea0aecb77..1067472c6f9 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0801.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0801.md @@ -85,4 +85,4 @@ It is the customer's responsibility to: This output verifies that the system satisfies this control by enforcing `STRICT mTLS`, ensuring all data in transit is encrypted using validated, rotating certificates to prevent unauthorized disclosure. The inclusion of `SPIFFE ID verification (SAN)` and `CA-backed trust` further ensures information integrity by detecting and preventing unauthorized modifications during transmission. -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-0801-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-0801-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0802.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0802.md index adf7707fdbf..a70e895b198 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0802.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc0802.md @@ -84,4 +84,4 @@ The presence of the `istio-proxy sidecar` and the `MUTUAL TLS` mode on the ingre {{< figure src="/attachments/private-platform/nist-sc/nist-sc-0802-1.png" class="no-border" >}} -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-0802-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-0802-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc10.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc10.md index dc34ee73557..c64e6c72bdf 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc10.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc10.md @@ -62,4 +62,4 @@ Mendix supports configuring session timeouts and configuring related settings. T The custom runtime settings can be configured on the **Runtime** tab of the environment details page. -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-10-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-10-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc12.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc12.md index 31dd9cec462..654c6928aff 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc12.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc12.md @@ -85,4 +85,4 @@ Mendix supports integration with external KMS like AWS Secret Manager, HashiCorp * [Configuring External Secret Management with AWS Secret Manager](/private-mendix-platform/configure-aws-secret-manager/) * [Configuring External Secret Management with Azure Key Vault](/private-mendix-platform/configure-azure-key-vault/) -* [Configuring External Secret Management with HashiCorp Vault](/private-mendix-platform/configure-hashicorp-vault/) \ No newline at end of file +* [Configuring External Secret Management with HashiCorp Vault](/private-mendix-platform/configure-hashicorp-vault/) diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc13.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc13.md index 14e0272ddc6..d58cbb8244a 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc13.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc13.md @@ -97,4 +97,4 @@ While Mendix ensures platform‑wide FIPS readiness, implementers and operators The output confirms the system is operating in FIPS mode (`fips_enabled: 1`), ensuring that all cryptographic operations used for data protection and digital signatures utilize FIPS-validated modules. This demonstrates compliance with federal standards by restricting the information system to organization-defined, approved cryptographic types for all security-sensitive functions. -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-13-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-13-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc17.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc17.md index acc7faf02b2..7b515c71327 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc17.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc17.md @@ -74,4 +74,4 @@ The customer can add certificate for the Private Mendix Platform URL when instal {{< figure src="/attachments/private-platform/nist-sc/nist-sc-17-1.png" class="no-border" >}} -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-17-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-17-2.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc18.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc18.md index 953530f387b..87a410ad79b 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc18.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc18.md @@ -54,4 +54,4 @@ The Customer must define and document: * Usage restrictions and implementation guidance for each allowed mobile code technology * Authorization and monitoring procedures for mobile code within the information system -It is the responsibility of the Infra Implementer, App Implementer, Infra Operator, and App Operator to only use allowed mobile code and mobile code technologies throughout the lifecycle of the Mendix solution as directed by the Customer. \ No newline at end of file +It is the responsibility of the Infra Implementer, App Implementer, Infra Operator, and App Operator to only use allowed mobile code and mobile code technologies throughout the lifecycle of the Mendix solution as directed by the Customer. diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc20.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc20.md index ecde09e1025..e24ec451dcb 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc20.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc20.md @@ -55,4 +55,4 @@ The Customer and Infra Implementer must ensure that: * External clients can verify data origin authentication and integrity of DNS responses. * DNSSEC is properly configured in accordance with OMB Memorandum 08-23 and NIST SP 800-81. -It is the responsibility of the Infra Operator to ensure ongoing compliance with DNSSEC requirements. \ No newline at end of file +It is the responsibility of the Infra Operator to ensure ongoing compliance with DNSSEC requirements. diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc21.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc21.md index 1960298b8d2..6cbcf574bf3 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc21.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc21.md @@ -48,4 +48,4 @@ The customer and Infra Implementer must ensure that: * Clients use authenticated channels to trusted validation providers if not performing validation directly * DNS infrastructure supports validation of DNSSEC signatures in accordance with NIST SP 800-81 -It is the responsibility of the Infra Operator to ensure ongoing compliance with DNSSEC validation requirements. \ No newline at end of file +It is the responsibility of the Infra Operator to ensure ongoing compliance with DNSSEC validation requirements. diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc23.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc23.md index cd3574cae70..2208c955250 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc23.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc23.md @@ -49,4 +49,4 @@ The customer and Infra Implementer must ensure that: * Both ends of communications sessions can verify the ongoing identities of the other parties. * Session-level protections prevent insertion of false information into active sessions. -It is the responsibility of the Infra Operator to ensure ongoing compliance with TLS and session authenticity requirements. \ No newline at end of file +It is the responsibility of the Infra Operator to ensure ongoing compliance with TLS and session authenticity requirements. diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2301.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2301.md index fe0a42d0c94..fcc96e10d11 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2301.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2301.md @@ -68,4 +68,4 @@ The **Logout All Users** option is available in Admin mode under [User Managemen The Private Mendix Platform System Admin can go to **Settings > Identity & Access Settings** and configure the maximum period for automatic session expiration, with the option to show a notification before logging the user out. -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-2301-3.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-2301-3.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2303.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2303.md index b7d04a334e2..0bd34a3b336 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2303.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2303.md @@ -140,4 +140,4 @@ In addition to `XASSESSIONID`, the Runtime issues a separate `authtoken` cookie: * HttpOnly: `true` * Duration: Token expiration period -This is a second server-generated cryptographic identifier stored separately from the session ID, used for long-lived authentication persistence. Both tokens are Runtime-generated, HttpOnly, and serve independent purposes — XASSESSIONID for the current session, authtoken for persistent authentication. This layered, server-generated approach is consistent with the SC-23(3) requirement for system-generated identifiers. \ No newline at end of file +This is a second server-generated cryptographic identifier stored separately from the session ID, used for long-lived authentication persistence. Both tokens are Runtime-generated, HttpOnly, and serve independent purposes — XASSESSIONID for the current session, authtoken for persistent authentication. This layered, server-generated approach is consistent with the SC-23(3) requirement for system-generated identifiers. diff --git a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2305.md b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2305.md index c7f7bf5b8cd..d8ab487b2c7 100644 --- a/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2305.md +++ b/content/en/docs/private-platform/nist-controls/sc/pmp-nist-sc2305.md @@ -70,4 +70,4 @@ The following evidence demonstrates compliance with SC-23 (05): {{< figure src="/attachments/private-platform/nist-sc/nist-sc-2305-1.png" class="no-border" >}} -{{< figure src="/attachments/private-platform/nist-sc/nist-sc-2305-2.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-sc/nist-sc-2305-2.png" class="no-border" >}} 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 591f9118329..40f8ef6e06b 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(1) - FIPS Mode: AES-256 and FIPS 140-2 Validated Cryptography -The sibling control SC-28 (1) 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 (1) 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/refguide/installation/system-requirements.md b/content/en/docs/refguide/installation/system-requirements.md index 6b9d3f344b0..3e9f02cb54d 100644 --- a/content/en/docs/refguide/installation/system-requirements.md +++ b/content/en/docs/refguide/installation/system-requirements.md @@ -126,7 +126,6 @@ For more information on ports and modifying Studio Pro's default ports, see [Con For information on how to ensure the smooth operation of Mendix AI Assistance (Maia), see the [Network Configuration Requirements](/refguide/mendix-ai-assistance/#maia-network-requirement) section in *Mendix AI Assistance (Maia)*. - ### File Locations For active development and running your application locally, your app folder should be on a local drive (such as C:) or a network folder that has been mapped to a [Windows drive letter](https://support.microsoft.com/en-us/windows/map-a-network-drive-in-windows-10-29ce55d1-34e3-a7e2-4801-131475f9557d). diff --git a/content/en/docs/refguide/modeling/integration/data-transformers/data-transformer-use-cases.md b/content/en/docs/refguide/modeling/integration/data-transformers/data-transformer-use-cases.md index df553c3bb4e..ec852ea4c07 100644 --- a/content/en/docs/refguide/modeling/integration/data-transformers/data-transformer-use-cases.md +++ b/content/en/docs/refguide/modeling/integration/data-transformers/data-transformer-use-cases.md @@ -123,7 +123,6 @@ The transformation is straightforward. Each field in the output is explicitly ma For more information about dot accessors, see this [GitHub resource](https://github.com/schibsted/jslt/blob/master/tutorial.md#dot-accessors). - ## Normalizing Objects to Arrays {#normalizing-objects-to-arrays} Some APIs return collections of records as a keyed object, where each key acts as a unique identifier for that record (also known as dynamic keys). Mendix works more naturally with lists of objects, so this transformation converts that keyed structure into a flat, normalized array that can be directly mapped to a Mendix entity list. @@ -512,4 +511,3 @@ let vars = .head.vars The variable names are captured into `vars` at the root level before any looping begins. The transformation then iterates over each binding in the results. Because `.` is rebound inside the inner loop, the current binding is saved into `binding` immediately. The inner for loop iterates over the variable names, using each variable name as both the key and the lookup argument. `get-key($binding, .)` retrieves the typed value wrapper for that variable from the saved binding, and `.value` extracts the plain value from it. `fallback` ensures that if a variable is missing from a binding, an empty string is used instead of null. The result is a clean, flat list of objects with no type wrappers that you can easily use as a source for import mapping. For more information about `get-key`, `fallback`, and other functions, see this [GitHub resource](https://github.com/schibsted/jslt/blob/master/functions.md#get-keyobject-key-fallback---value). - diff --git a/content/en/docs/refguide/modeling/menus/translatable-texts/language-operations.md b/content/en/docs/refguide/modeling/menus/translatable-texts/language-operations.md index 65bbe479bbe..b8b86ca451f 100644 --- a/content/en/docs/refguide/modeling/menus/translatable-texts/language-operations.md +++ b/content/en/docs/refguide/modeling/menus/translatable-texts/language-operations.md @@ -38,6 +38,7 @@ Click **Apply** to apply the selected language operation. Select the **Source language** and the **Destination language** from the drop-down menus. {{% alert color="info" %}} + * Texts that are absent in the source language are absent in the destination language – any original text is removed * All the texts in the source language are deleted {{% /alert %}} diff --git a/content/en/docs/refguide/modeling/menus/view-menu/changes-pane.md b/content/en/docs/refguide/modeling/menus/view-menu/changes-pane.md index a49b3ba9c47..78e88e87b7d 100644 --- a/content/en/docs/refguide/modeling/menus/view-menu/changes-pane.md +++ b/content/en/docs/refguide/modeling/menus/view-menu/changes-pane.md @@ -85,7 +85,6 @@ The toolbar at this level contains the following buttons: For text-based properties, you can double-click a property row to open the [File Differences Viewer](/refguide/file-diff-viewer/), which shows a detailed side-by-side comparison of the old and new values. To compare file-level changes at the top level, double-click a file row or right-click and select **Compare with original**. - The left side of the grid contains the following columns: * **Element** – the name of the modified element diff --git a/content/en/docs/refguide/runtime/custom-settings/configure-cors.md b/content/en/docs/refguide/runtime/custom-settings/configure-cors.md index a512ddf399b..ca0dcd5edef 100644 --- a/content/en/docs/refguide/runtime/custom-settings/configure-cors.md +++ b/content/en/docs/refguide/runtime/custom-settings/configure-cors.md @@ -65,4 +65,4 @@ If CORS is not working as expected, check the following: * **Browser console errors** — Look for CORS-related error messages in the browser developer tools console. These typically indicate which header is missing or misconfigured. * **Origin mismatch** — Ensure the value of `Access-Control-Allow-Origin` exactly matches the origin shown in the browser error, including the scheme (`https://`) and port number (if applicable). * **Missing `SameSiteCookies` setting** — Without `com.mendix.core.SameSiteCookies` set to `None`, cookies will not be sent on cross-origin requests, which can cause authentication failures. -* **HTTPS requirement** — When `SameSiteCookies` is set to `None`, the `Secure` attribute is automatically added to cookies, meaning both the runtime and the client must be served over HTTPS. \ No newline at end of file +* **HTTPS requirement** — When `SameSiteCookies` is set to `None`, the `Secure` attribute is automatically added to cookies, meaning both the runtime and the client must be served over HTTPS. diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md index 85225aca7f7..0e7faac3063 100644 --- a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md +++ b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md @@ -11,8 +11,8 @@ description: "Native Template 14" ### Fixes -- We fixed an issue where version logs events were not recorded in Firebase for Android. -- We fixed an issue which occurred when building apps in Xcode 26.4 and above. +* We fixed an issue where version logs events were not recorded in Firebase for Android. +* We fixed an issue which occurred when building apps in Xcode 26.4 and above. ## 14.1.15 {#1425} diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-17-rn.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-17-rn.md index f6b8453832d..a7916631de2 100644 --- a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-17-rn.md +++ b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-17-rn.md @@ -9,7 +9,7 @@ description: "Native Template 17" **Release date: May 12, 2026** -- We fixed the CocoaPods installation issue that was caused by `xcodeproj object version` 70. +* We fixed the CocoaPods installation issue that was caused by `xcodeproj object version` 70. ## 17.2.0 @@ -17,8 +17,8 @@ description: "Native Template 17" ### Fixes -- We fixed an issue where version logs events were not recorded in Firebase for Android. -- We fixed an issue which occurred when building apps in Xcode 26.4 and above. +* We fixed an issue where version logs events were not recorded in Firebase for Android. +* We fixed an issue which occurred when building apps in Xcode 26.4 and above. ## 17.1.0 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 82d9dc4bd0c..5516c94e5d3 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: May 12, 2026** -- We fixed the CocoaPods installation issue that was caused by `xcodeproj object version` 70. +* We fixed the CocoaPods installation issue that was caused by `xcodeproj object version` 70. ## 19.0.4 @@ -17,7 +17,7 @@ description: "Native Template 19" ### Improvements -- We updated vulnerable `okhttp`, `jackson`, and `security-crypto` dependencies. +* We updated vulnerable `okhttp`, `jackson`, and `security-crypto` dependencies. ## 19.0.3 @@ -25,8 +25,8 @@ description: "Native Template 19" ### Fixes -- We fixed an issue where version logs events were not recorded in Firebase for Android. -- We fixed an issue which occurred when building apps in Xcode 26.4 and above. +* We fixed an issue where version logs events were not recorded in Firebase for Android. +* We fixed an issue which occurred when building apps in Xcode 26.4 and above. ## 19.0.2 {#1902} 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 a1d07b4fcd9..2f5c155b00a 100644 --- a/content/en/docs/releasenotes/studio-pro/10/10.24.md +++ b/content/en/docs/releasenotes/studio-pro/10/10.24.md @@ -22,27 +22,27 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for #### Rspack -- We now support **Rspack** as a new bundler for React client applications, which delivers faster bundling and lower memory usage. Rspack aims to be the replacement for Rollup. While Rollup remains fully supported as the default bundler, we recommend trying Rspack by selecting it via the new `App bundler` setting under **Project** > **Settings** > **Runtime**. The bundler setting is stored in a file named `app-bundler` in the project root. -- Rspack is now generally available for React client applications. It delivers faster bundling and lower memory usage. Rollup remains the default bundler for now, but we recommend switching to Rspack. +* We now support **Rspack** as a new bundler for React client applications, which delivers faster bundling and lower memory usage. Rspack aims to be the replacement for Rollup. While Rollup remains fully supported as the default bundler, we recommend trying Rspack by selecting it via the new `App bundler` setting under **Project** > **Settings** > **Runtime**. The bundler setting is stored in a file named `app-bundler` in the project root. +* Rspack is now generally available for React client applications. It delivers faster bundling and lower memory usage. Rollup remains the default bundler for now, but we recommend switching to Rspack. ### Improvements -- We now automatically stop Gradle daemons when you exit Studio Pro, so unnecessary background processes no longer continue running. (Ticket 258422) -- Runtime nodes now automatically shut down when heartbeat updates fail or when the node's database entry is missing, improving cluster reliability and preventing orphaned nodes. -- We improved observability for retrieve and other runtime operations by including XPath constraints, entity paths, object types, and microflow names in OpenTelemetry span names. -- We clean up duplicate cluster management tasks during startup. -- We added *themecache.css* files to *.gitignore* to reduce conflicts when edited by multiple users. -- We added temporary Java files to *.gitignore* to reduce conflicts when edited by multiple users. +* We now automatically stop Gradle daemons when you exit Studio Pro, so unnecessary background processes no longer continue running. (Ticket 258422) +* Runtime nodes now automatically shut down when heartbeat updates fail or when the node's database entry is missing, improving cluster reliability and preventing orphaned nodes. +* We improved observability for retrieve and other runtime operations by including XPath constraints, entity paths, object types, and microflow names in OpenTelemetry span names. +* We clean up duplicate cluster management tasks during startup. +* We added *themecache.css* files to *.gitignore* to reduce conflicts when edited by multiple users. +* We added temporary Java files to *.gitignore* to reduce conflicts when edited by multiple users. ### Fixes -- We upgraded Netty dependencies to fix CVE-2026-42578, CVE-2026-42583, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-42577, CVE-2026-42579. (Tickets 278202, 278290, 277691, 278290) -- We fixed an issue in the **Select Elements** dialog of an XML import or export mapping where reopening the dialog with previously checked elements that contained inheritance or choice-type children caused a validation error `"Element '…' cannot be checked without a checked child element."` when clicking **OK**. This happened because those elements were not expanded, so their children were not loaded and could not be validated. Studio Pro now automatically expands such elements before clicking OK in the **Select Elements** dialog, ensuring all required child elements are properly loaded and resolved. (Ticket 268403) -- We fixed an issue with the client where passing an empty string as a parameter to a microflow triggered an error. For example, when filtering options of a combo box with a microflow, clearing the search string would trigger the error. (Ticket 271819) -- We fixed an issue where **Import** and **Cancel** buttons were not visible for certain resolutions and scalings. (Ticket 274077) -- 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 resolved an OS command injection vulnerability in the Git process runner reported by Veracode. -- We fixed an issue when using the Rollup bundler with the React client. +* We upgraded Netty dependencies to fix CVE-2026-42578, CVE-2026-42583, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-42577, CVE-2026-42579. (Tickets 278202, 278290, 277691, 278290) +* We fixed an issue in the **Select Elements** dialog of an XML import or export mapping where reopening the dialog with previously checked elements that contained inheritance or choice-type children caused a validation error `"Element '…' cannot be checked without a checked child element."` when clicking **OK**. This happened because those elements were not expanded, so their children were not loaded and could not be validated. Studio Pro now automatically expands such elements before clicking OK in the **Select Elements** dialog, ensuring all required child elements are properly loaded and resolved. (Ticket 268403) +* We fixed an issue with the client where passing an empty string as a parameter to a microflow triggered an error. For example, when filtering options of a combo box with a microflow, clearing the search string would trigger the error. (Ticket 271819) +* We fixed an issue where **Import** and **Cancel** buttons were not visible for certain resolutions and scalings. (Ticket 274077) +* 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 resolved an OS command injection vulnerability in the Git process runner reported by Veracode. +* We fixed an issue when using the Rollup bundler with the React client. ## 10.24.20 {#102420} @@ -52,13 +52,13 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for ### Improvements -- We clarified the error message when upgrading solutions with files that have paths that are too long. +* We clarified the error message when upgrading solutions with files that have paths that are too long. ### Fixes -- We fixed an issue where import and export mappings incorrectly showed consistency errors for microflows with unmapped optional parameters. Optional parameters now use their default values when not provided in the payload. Converter microflows must have exactly one required parameter which receives the value to be converted and may have additional optional parameters. (Ticket 250969) -- We fixed an issue when an older offline client (from a Mendix version below 10.24.17) would fail to synchronize with an **HTTP 560 (Invalid JSONRequest)** error, preventing the offline app from loading. (Ticket 274811) -- We added Microsoft-related MIME types. (Tickets 276471, 276598, 276604, 276958) +* We fixed an issue where import and export mappings incorrectly showed consistency errors for microflows with unmapped optional parameters. Optional parameters now use their default values when not provided in the payload. Converter microflows must have exactly one required parameter which receives the value to be converted and may have additional optional parameters. (Ticket 250969) +* We fixed an issue when an older offline client (from a Mendix version below 10.24.17) would fail to synchronize with an **HTTP 560 (Invalid JSONRequest)** error, preventing the offline app from loading. (Ticket 274811) +* We added Microsoft-related MIME types. (Tickets 276471, 276598, 276604, 276958) ## 10.24.19 {#102419} 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 233e17747a9..6f385f5f69a 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.10.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.10.md @@ -19,32 +19,32 @@ weight: 90 #### New Maia Features -- We introduced a new Maia MCP Client Settings editor to make configuring and managing MCP Client Settings easier. -- Maia's capabilities can now be exposed as an MCP server, which you can enable in Maia preferences. This allows external agentic coding tools like Claude Code or Copilot to make modifications to your Mendix app, with changes reflected directly in Studio Pro. -- Maia can now fetch and interpret static web content such as external documentation, JSON specifications, and other publicly available documents. Note that it does not support content requiring authentication, dynamic web pages, or non-text formats. -- Maia can organize documents (excluding pages) into folders, following your existing folder structure, or using standard Mendix best practices. -- Maia can now generate new JavaScript actions, add new parameters to existing JavaScript actions, and create or update the JavaScript file associated with a JavaScript action. -- Maia can now generate and configure [Multi-user task](/refguide/multi-user-task/) in workflows. +* We introduced a new Maia MCP Client Settings editor to make configuring and managing MCP Client Settings easier. +* Maia's capabilities can now be exposed as an MCP server, which you can enable in Maia preferences. This allows external agentic coding tools like Claude Code or Copilot to make modifications to your Mendix app, with changes reflected directly in Studio Pro. +* Maia can now fetch and interpret static web content such as external documentation, JSON specifications, and other publicly available documents. Note that it does not support content requiring authentication, dynamic web pages, or non-text formats. +* Maia can organize documents (excluding pages) into folders, following your existing folder structure, or using standard Mendix best practices. +* Maia can now generate new JavaScript actions, add new parameters to existing JavaScript actions, and create or update the JavaScript file associated with a JavaScript action. +* Maia can now generate and configure [Multi-user task](/refguide/multi-user-task/) in workflows. #### Other New Features -- We introduced Update Assistant (beta) as a bottom panel in Studio Pro, where you can check Java action deprecations in your app. -- We implemented a new function `DATEPARSE` in OQL. For more information, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#dateparse-function). -- We added support for the interrupting behavior on the workflow notification event sub-process **Start** event. When configured as interrupting, the event sub-process interrupts the parent workflow, terminating all active execution paths within the global scope, including activities in the main process and any nested sub-processes, before initiating the event sub-process flow. -- We added a **Show** button in the element selector. Clicking it opens the selected element. -- We added the optional `selectedElementId` in the select methods of the element selector. When passed in, it highlights the node with the corresponding ID in the tree. -- We added the `http.nonProxyHosts` runtime configuration setting to specify hosts for which the runtime does not use a proxy. -- We added the ability to revert a commit from the history pane. You can now right-click a commit and select **Revert Commit** to reverse the changes introduced by that specific commit. -- We added a new runtime setting `FileStorage.S3.DisableChunkedEncoding` to allow disabling chunked encoding for S3 storage. (Tickets 274327, 272789) -- We added a new Java API to create spans for tracing. The API is accessible via `com.mendix.core.Core.tracing()`. -- The Mendix Runtime now responds to Cross-Origin Resource Sharing (CORS) preflight (`OPTIONS`) requests for client-facing endpoints. The responses include the custom headers configured in the runtime settings, allowing you to set up CORS for your app. +* We introduced Update Assistant (beta) as a bottom panel in Studio Pro, where you can check Java action deprecations in your app. +* We implemented a new function `DATEPARSE` in OQL. For more information, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#dateparse-function). +* We added support for the interrupting behavior on the workflow notification event sub-process **Start** event. When configured as interrupting, the event sub-process interrupts the parent workflow, terminating all active execution paths within the global scope, including activities in the main process and any nested sub-processes, before initiating the event sub-process flow. +* We added a **Show** button in the element selector. Clicking it opens the selected element. +* We added the optional `selectedElementId` in the select methods of the element selector. When passed in, it highlights the node with the corresponding ID in the tree. +* We added the `http.nonProxyHosts` runtime configuration setting to specify hosts for which the runtime does not use a proxy. +* We added the ability to revert a commit from the history pane. You can now right-click a commit and select **Revert Commit** to reverse the changes introduced by that specific commit. +* We added a new runtime setting `FileStorage.S3.DisableChunkedEncoding` to allow disabling chunked encoding for S3 storage. (Tickets 274327, 272789) +* We added a new Java API to create spans for tracing. The API is accessible via `com.mendix.core.Core.tracing()`. +* The Mendix Runtime now responds to Cross-Origin Resource Sharing (CORS) preflight (`OPTIONS`) requests for client-facing endpoints. The responses include the custom headers configured in the runtime settings, allowing you to set up CORS for your app. ### Improvements -- We introduced a stricter requirements check on the server synchronization APIs for offline apps. This prevents entities from synchronizing changes when they are configured with the synchronization modes Online, Nothing, or Never. To allow older offline clients that have an All Objects or By XPath synchronization mode to still synchronize while the new app version has the entity configured with an Online, Nothing, or Never synchronization mode, we added a **Compatibility mode** checkbox. -- Pluggable widgets can now select any file or image entity on the page when configuring a file or image property. Previously, this was limited to the immediate surrounding data view. -- We added a text indicator to the comparison pane toolbar showing information about what is being compared. -- We made improvements to the **Collect Support Information** feature: +* We introduced a stricter requirements check on the server synchronization APIs for offline apps. This prevents entities from synchronizing changes when they are configured with the synchronization modes Online, Nothing, or Never. To allow older offline clients that have an All Objects or By XPath synchronization mode to still synchronize while the new app version has the entity configured with an Online, Nothing, or Never synchronization mode, we added a **Compatibility mode** checkbox. +* Pluggable widgets can now select any file or image entity on the page when configuring a file or image property. Previously, this was limited to the immediate surrounding data view. +* We added a text indicator to the comparison pane toolbar showing information about what is being compared. +* We made improvements to the **Collect Support Information** feature: * The **Collect Support Information** progress dialog is now cancellable. * We made the **Collect Support Information** feature available to macOS users. * We added useful information to aid Mendix Support in diagnosing issues, such as: @@ -53,61 +53,61 @@ weight: 90 * Number of modules * Total document count and document type breakdown * Whether the project directory has been excluded from Windows Defender Antivirus -- We fixed an issue where OQL-based view entities used an outdated ID column alias, leading to mismatches with domain model association names. A new app conversion step now detects these mismatches when opening the app and updates the column alias in OQL accordingly. -- We fixed an issue where copying a view entity together with its associated entity failed to include the connecting association. This association is now correctly copied whenever both elements are selected. Additionally, copying and pasting a view entity now duplicates any linked in-module or cross-module associations, assigning them new names and automatically updating their OQL references. -- Maia answers now also include sources from the Mendix Support Knowledge Base. -- We improved the Maia Chat experience with several UI enhancements. -- We upgraded to React 19.2 and React Native 0.83, bringing the latest performance improvements and features from both ecosystems. These updates provide enhanced rendering performance, improved native module integration, and a more modern foundation for building your apps. -- We improved how Studio Pro stores the configuration microflow and the headers microflow in consumed OData services. These microflows are now stored in two separate fields instead of the same field. When you switch from using a headers microflow to a configuration microflow, Studio Pro asks if you want to clear the headers microflow. Studio Pro does the same check if you switch from a configuration microflow to a headers microflow. -- We now delete sessions when the associated user is deleted. -- We added the `com.mendix.tracing.Span.setAttribute` methods to set attributes of spans that are already started. -- Java action tracing span names now include the Java action name. -- We clarified the error message when upgrading solutions with files that have paths that are too long. -- We replaced the custom error screen in the App Explorer with a unified global error screen that provides a consistent experience and includes a refresh button and a direct link to Mendix Support. -- The modernized console table now supports multi-selection via the context menu flow, allowing you to copy messages and stack traces for multiple selected log lines. -- The `app-bundler` file in the project directory has been removed and replaced by a property in the model. The bundler selection (Rspack or Rollup) is now stored as part of the **App Settings** instead of in a file. -- We expanded the consistency checker to detect more page URL conflicts, so ambiguous navigation patterns are caught during design time rather than at runtime. For example, `product/123` now correctly reports a conflict with `product/{Product/Id}`. For another example, the combination of `overview` and `over{view}` now reports a conflict. +* We fixed an issue where OQL-based view entities used an outdated ID column alias, leading to mismatches with domain model association names. A new app conversion step now detects these mismatches when opening the app and updates the column alias in OQL accordingly. +* We fixed an issue where copying a view entity together with its associated entity failed to include the connecting association. This association is now correctly copied whenever both elements are selected. Additionally, copying and pasting a view entity now duplicates any linked in-module or cross-module associations, assigning them new names and automatically updating their OQL references. +* Maia answers now also include sources from the Mendix Support Knowledge Base. +* We improved the Maia Chat experience with several UI enhancements. +* We upgraded to React 19.2 and React Native 0.83, bringing the latest performance improvements and features from both ecosystems. These updates provide enhanced rendering performance, improved native module integration, and a more modern foundation for building your apps. +* We improved how Studio Pro stores the configuration microflow and the headers microflow in consumed OData services. These microflows are now stored in two separate fields instead of the same field. When you switch from using a headers microflow to a configuration microflow, Studio Pro asks if you want to clear the headers microflow. Studio Pro does the same check if you switch from a configuration microflow to a headers microflow. +* We now delete sessions when the associated user is deleted. +* We added the `com.mendix.tracing.Span.setAttribute` methods to set attributes of spans that are already started. +* Java action tracing span names now include the Java action name. +* We clarified the error message when upgrading solutions with files that have paths that are too long. +* We replaced the custom error screen in the App Explorer with a unified global error screen that provides a consistent experience and includes a refresh button and a direct link to Mendix Support. +* The modernized console table now supports multi-selection via the context menu flow, allowing you to copy messages and stack traces for multiple selected log lines. +* The `app-bundler` file in the project directory has been removed and replaced by a property in the model. The bundler selection (Rspack or Rollup) is now stored as part of the **App Settings** instead of in a file. +* We expanded the consistency checker to detect more page URL conflicts, so ambiguous navigation patterns are caught during design time rather than at runtime. For example, `product/123` now correctly reports a conflict with `product/{Product/Id}`. For another example, the combination of `overview` and `over{view}` now reports a conflict. ### Fixes -- We now ensure a `SELECT *` OQL query returns the same columns independent of the optimistic locking setting value. Previously, the `MxObjectVersion` column was returned when optimistic locking was enabled. -- We fixed INSERT OQL statements when optimistic locking is enabled. -- We fixed an error in offline synchronization when objects with sync mode set to **Never** are selectively synced after a full synchronization. (Ticket 266442) -- We improved the error message for invalid save actions when trying to save an unexpected object type while strict mode is enabled. (Ticket 270333) -- We fixed image rendering for offline web applications during local development. We also enabled service worker and disabled service worker caching by default for local development. (Tickets 271956, 273435) -- We fixed an issue where saving changes in the **Select Elements** dialog of an XML import mapping incorrectly allowed saving an invalid selection where a parent element was checked but its required child element was not, without showing the expected error "Element '…' cannot be checked without a checked child element." (Ticket 273820) -- We fixed an issue where filtering for objects using a constraint like `[not(association)]` in offline apps incorrectly returned no results. (Ticket 274157) -- We fixed an issue in the **Select Elements** dialog of an XML export mapping where clicking **OK** on a checked parent element whose required child elements had not been expanded caused the error "Element '…' cannot be checked without a checked child element." Studio Pro now automatically checks required child elements of unexpanded parent nodes before saving. (Ticket 274683) -- We fixed an issue when running with Oracle where task queue queries generated invalid SQL. (Ticket 275597) -- We made the event sub-process start activity in workflows not draggable. -- We made the main start activity in workflows not draggable to prevent you from accidentally dragging it and losing your progress. -- We fixed an issue where renaming a view entity association in the domain model editor did not update the corresponding ID alias in the OQL query, ensuring the OQL definition now stays consistent with the new association name. -- We fixed an issue in the logic editors where the LogicBot recommender dialog remained open after running the app, causing an error. The dialog is now closed when suggestions are cleared. -- We fixed an issue where documents generated and then edited by Maia were not deleted properly when **Undo** was pressed. -- We fixed an issue where using **Undo all** in Maia would trigger an unexpected error dialog. -- We fixed an issue where Maia context menu items in the App Explorer were enabled when multiple documents were selected. These items are now disabled for multi-document selections. -- We added an additional fix for cases where an external keyboard does not traverse properly through elements marked as accessible on mobile devices. -- We fixed an issue on iOS where specific scenarios of using custom styled widgets inside containers did not show the desired styling. -- We fixed an issue where an error dialog appeared when re-selecting a modified JSON structure in an import mapping. This happened after updating the JSON structure's content and then re-opening the **Select Elements** dialog to select the same structure again. -- We fixed an issue in consumed REST services. Path-level parameters are now added to the parameters table when importing an OpenAPI or Swagger contract. -- We fixed an issue in published REST services using CORS. The runtime now includes CORS headers in error responses. -- We fixed an issue in published REST services in Studio Pro. Studio Pro used the same field for (internal) documentation and public documentation (used in OpenAPI documents). Now these are two separate fields. -- We fixed an issue in the modernized Console panel where new logs appeared at the bottom of the table instead of the top when sorted in descending order. -- We fixed an issue where native macOS context menus appeared instead of the intended Studio Pro context menus. -- We fixed an issue in the modernized Runtime Console where the **Restart** and **Stop** buttons stopped working after the first restart. -- We fixed an issue where the modernized App Explorer was not rendered on startup. -- We fixed an issue in the modernized Console panel where the logs did not clear when another app was created or opened. -- We fixed an issue in the modernized Console panel where log levels were not always reset to their defaults when opening a new app. -- We fixed an issue in the JavaScript Action Editor where multiline import statements were not parsed correctly. -- We fixed an issue where an app rejected valid localized dates for custom date patterns that use month names. This affected patterns with abbreviated month names such as `dd MMM yyyy` and standalone abbreviated month names such as `dd LLL yyyy`, so values like the Dutch `16 mrt 2027 10:02` were treated as invalid. -- We fixed an issue where the `Filter` interface in `mx-api/data` incorrectly used `amount` instead of `limit` to specify the maximum number of records to retrieve. While `amount` is supported, we recommend using `limit`. -- We fixed an issue where module roles were not sorted in alphabetical order in the entity access rules editor. +* We now ensure a `SELECT *` OQL query returns the same columns independent of the optimistic locking setting value. Previously, the `MxObjectVersion` column was returned when optimistic locking was enabled. +* We fixed INSERT OQL statements when optimistic locking is enabled. +* We fixed an error in offline synchronization when objects with sync mode set to **Never** are selectively synced after a full synchronization. (Ticket 266442) +* We improved the error message for invalid save actions when trying to save an unexpected object type while strict mode is enabled. (Ticket 270333) +* We fixed image rendering for offline web applications during local development. We also enabled service worker and disabled service worker caching by default for local development. (Tickets 271956, 273435) +* We fixed an issue where saving changes in the **Select Elements** dialog of an XML import mapping incorrectly allowed saving an invalid selection where a parent element was checked but its required child element was not, without showing the expected error "Element '…' cannot be checked without a checked child element." (Ticket 273820) +* We fixed an issue where filtering for objects using a constraint like `[not(association)]` in offline apps incorrectly returned no results. (Ticket 274157) +* We fixed an issue in the **Select Elements** dialog of an XML export mapping where clicking **OK** on a checked parent element whose required child elements had not been expanded caused the error "Element '…' cannot be checked without a checked child element." Studio Pro now automatically checks required child elements of unexpanded parent nodes before saving. (Ticket 274683) +* We fixed an issue when running with Oracle where task queue queries generated invalid SQL. (Ticket 275597) +* We made the event sub-process start activity in workflows not draggable. +* We made the main start activity in workflows not draggable to prevent you from accidentally dragging it and losing your progress. +* We fixed an issue where renaming a view entity association in the domain model editor did not update the corresponding ID alias in the OQL query, ensuring the OQL definition now stays consistent with the new association name. +* We fixed an issue in the logic editors where the LogicBot recommender dialog remained open after running the app, causing an error. The dialog is now closed when suggestions are cleared. +* We fixed an issue where documents generated and then edited by Maia were not deleted properly when **Undo** was pressed. +* We fixed an issue where using **Undo all** in Maia would trigger an unexpected error dialog. +* We fixed an issue where Maia context menu items in the App Explorer were enabled when multiple documents were selected. These items are now disabled for multi-document selections. +* We added an additional fix for cases where an external keyboard does not traverse properly through elements marked as accessible on mobile devices. +* We fixed an issue on iOS where specific scenarios of using custom styled widgets inside containers did not show the desired styling. +* We fixed an issue where an error dialog appeared when re-selecting a modified JSON structure in an import mapping. This happened after updating the JSON structure's content and then re-opening the **Select Elements** dialog to select the same structure again. +* We fixed an issue in consumed REST services. Path-level parameters are now added to the parameters table when importing an OpenAPI or Swagger contract. +* We fixed an issue in published REST services using CORS. The runtime now includes CORS headers in error responses. +* We fixed an issue in published REST services in Studio Pro. Studio Pro used the same field for (internal) documentation and public documentation (used in OpenAPI documents). Now these are two separate fields. +* We fixed an issue in the modernized Console panel where new logs appeared at the bottom of the table instead of the top when sorted in descending order. +* We fixed an issue where native macOS context menus appeared instead of the intended Studio Pro context menus. +* We fixed an issue in the modernized Runtime Console where the **Restart** and **Stop** buttons stopped working after the first restart. +* We fixed an issue where the modernized App Explorer was not rendered on startup. +* We fixed an issue in the modernized Console panel where the logs did not clear when another app was created or opened. +* We fixed an issue in the modernized Console panel where log levels were not always reset to their defaults when opening a new app. +* We fixed an issue in the JavaScript Action Editor where multiline import statements were not parsed correctly. +* We fixed an issue where an app rejected valid localized dates for custom date patterns that use month names. This affected patterns with abbreviated month names such as `dd MMM yyyy` and standalone abbreviated month names such as `dd LLL yyyy`, so values like the Dutch `16 mrt 2027 10:02` were treated as invalid. +* We fixed an issue where the `Filter` interface in `mx-api/data` incorrectly used `amount` instead of `limit` to specify the maximum number of records to retrieve. While `amount` is supported, we recommend using `limit`. +* We fixed an issue where module roles were not sorted in alphabetical order in the entity access rules editor. ### Deprecations -- Starting with Mendix version 11.12, we drop support for the following database versions that are no longer supported by the vendors: - - PostgreSQL 13 - - MariaDB 10.6 +* Starting with Mendix version 11.12, we drop support for the following database versions that are no longer supported by the vendors: + * PostgreSQL 13 + * MariaDB 10.6 ### Breaking Changes 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 cc0b4631fc7..45a4b650005 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.11.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.11.md @@ -24,102 +24,103 @@ We are releasing the beta version of the data transformer, which allows you to t #### Other New Features -- We introduced a modernized Debugger pane as part of the updated Debugger experience. -- The modernized **Debug Windows** can now be switched off in **Edit** > **Preferences** > **New features** by deselecting **Use the modernized Debug Windows (Requires restart of Studio Pro)**. -- We introduced a modernized **Breakpoints** pane as part of the updated Debugger experience. The new pane supports sorting by any column, multi-selection, enabling/disabling breakpoints with the Space key, selecting all breakpoints with Ctrl + A (Cmd + A on macOS), and navigating directly to the breakpoint location with Enter. -- The modernized Debugger can be switched off in **Edit > Preferences > New features** by deselecting **Use the modernized Debugger (Requires restart of Studio Pro)**. -- We added a fast reload capability for custom blob documents. -- We increased the minimum compatibility mode for Azure SQL to 160. This is equivalent to SQL Server 2022. -- We added the ability to add new documents and entities from the element selector. -- We implemented three new functions in OQL: `TRIM`, `LTRIM`, and `RTRIM`. For more information, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#trim). -- Viewing textual differences for a modified value (or file on disk) no longer requires installation of a third-party tool. You can now directly view a text diff inside Studio Pro by clicking the modified value or file in the **Changes** or **Comparison** pane. -- We reimplemented the domain model editor using web technology. This new editor is functionally equivalent to the classic version. You can switch between the two using the toggle in the **Domain Model** toolbar. -- We reimplemented the regular expression dialog in web. This dialog is feature equal to the old version and introduces no new features. -- Maia can now generate and update app-level **Navigation** and **Menu** documents. For example, you can ask Maia to build the menu items based on the pages in an app. +* We introduced a modernized Debugger pane as part of the updated Debugger experience. +* The modernized **Debug Windows** can now be switched off in **Edit** > **Preferences** > **New features** by deselecting **Use the modernized Debug Windows (Requires restart of Studio Pro)**. +* We introduced a modernized **Breakpoints** pane as part of the updated Debugger experience. The new pane supports sorting by any column, multi-selection, enabling/disabling breakpoints with the Space key, selecting all breakpoints with Ctrl + A (Cmd + A on macOS), and navigating directly to the breakpoint location with Enter. +* The modernized Debugger can be switched off in **Edit > Preferences > New features** by deselecting **Use the modernized Debugger (Requires restart of Studio Pro)**. +* We added a fast reload capability for custom blob documents. +* We increased the minimum compatibility mode for Azure SQL to 160. This is equivalent to SQL Server 2022. +* We added the ability to add new documents and entities from the element selector. +* We implemented three new functions in OQL: `TRIM`, `LTRIM`, and `RTRIM`. For more information, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#trim). +* Viewing textual differences for a modified value (or file on disk) no longer requires installation of a third-party tool. You can now directly view a text diff inside Studio Pro by clicking the modified value or file in the **Changes** or **Comparison** pane. +* We reimplemented the domain model editor using web technology. This new editor is functionally equivalent to the classic version. You can switch between the two using the toggle in the **Domain Model** toolbar. +* We reimplemented the regular expression dialog in web. This dialog is feature equal to the old version and introduces no new features. +* Maia can now generate and update app-level **Navigation** and **Menu** documents. For example, you can ask Maia to build the menu items based on the pages in an app. + * We introduced [object data sources](/apidocs-mxsdk/apidocs/pluggable-widgets-property-types/#object-datasource) to the Pluggable Widget API. Widget developers can now declare a data source property with `isList="false"` for data sources that are intended to return a single object. Other properties can be linked to object data sources in the same way they are linked to list data sources. This enhancement allows you, for example, to build your own data view widget. -- We added a scroll-to-bottom button in Maia chat that includes a loading indicator to show when Maia is processing. Chat messages now auto-scroll only when you are at the bottom, preventing interruptions while reading previous messages. -- We implemented support for editable file and image types (`EditableFileValue` and `EditableImageValue`) on native. Set `allowUpload="true"` on a file or image property to use the new editable API on native widgets. -- We added support for optimistic locking with offline-first applications. Previously, enabling optimistic locking was not allowed when an offline-based navigation profile was configured. Now, offline changes are synchronized to the server without being blocked by optimistic locking version checks. -- We added support for agent skills. You can now create your own skill definitions via the **skills** section in the App Explorer under **Maia**. Each skill is defined by a `SKILL.md` file stored in the `skillssource/` directory of your app. Skill names and descriptions are included in Maia's context at the start of each chat session, while the full skill content and any reference files are loaded on demand. -- You can now disable the web fetch tool in Maia preferences. -- We added support for reference files in agent skills. You can now add markdown files to a `references/` subdirectory inside a skill folder to provide Maia with additional context, such as domain knowledge or glossaries. Reference files can be managed directly from the **App Explorer**. -- Rspack is now generally available for React client applications. It delivers faster bundling and lower memory usage. Rollup remains the default bundler for now, but we recommend switching to Rspack. -- We added support for notification boundary events in workflows. Similar to the timer boundary event, a notification boundary event can be attached to a workflow activity and triggered via the Notify Workflow microflow activity. Both interrupting and non-interrupting variants are supported. -- We added notification events to workflows, which are similar to wait-for-notification events, with the distinctions that they appear as a circle and cannot have boundary events. +* We added a scroll-to-bottom button in Maia chat that includes a loading indicator to show when Maia is processing. Chat messages now auto-scroll only when you are at the bottom, preventing interruptions while reading previous messages. +* We implemented support for editable file and image types (`EditableFileValue` and `EditableImageValue`) on native. Set `allowUpload="true"` on a file or image property to use the new editable API on native widgets. +* We added support for optimistic locking with offline-first applications. Previously, enabling optimistic locking was not allowed when an offline-based navigation profile was configured. Now, offline changes are synchronized to the server without being blocked by optimistic locking version checks. +* We added support for agent skills. You can now create your own skill definitions via the **skills** section in the App Explorer under **Maia**. Each skill is defined by a `SKILL.md` file stored in the `skillssource/` directory of your app. Skill names and descriptions are included in Maia's context at the start of each chat session, while the full skill content and any reference files are loaded on demand. +* You can now disable the web fetch tool in Maia preferences. +* We added support for reference files in agent skills. You can now add markdown files to a `references/` subdirectory inside a skill folder to provide Maia with additional context, such as domain knowledge or glossaries. Reference files can be managed directly from the **App Explorer**. +* Rspack is now generally available for React client applications. It delivers faster bundling and lower memory usage. Rollup remains the default bundler for now, but we recommend switching to Rspack. +* We added support for notification boundary events in workflows. Similar to the timer boundary event, a notification boundary event can be attached to a workflow activity and triggered via the Notify Workflow microflow activity. Both interrupting and non-interrupting variants are supported. +* We added notification events to workflows, which are similar to wait-for-notification events, with the distinctions that they appear as a circle and cannot have boundary events. ### Improvements #### Performance -- We made local deployment faster by skipping Java proxy file regeneration for model elements that have not changed since the previous deployment. -- We reduced the time it takes to open pop-up dialogs for selecting elements like entities or attributes. +* We made local deployment faster by skipping Java proxy file regeneration for model elements that have not changed since the previous deployment. +* We reduced the time it takes to open pop-up dialogs for selecting elements like entities or attributes. #### Other Improvements -- We improved the **Maia Undo All** button so it now reverts changes at the session level instead of the prompt level. -- The `OQL INSERT INTO SELECT` statement no longer requires column names in the `SELECT` part. -- In the logic editors, optional parameters are now visually distinguished with a dotted border, making it easier to identify which parameters are not required. -- We added a **Refresh schema** button to the mapping editor toolbar. This button appears when the mapping is out of sync with its underlying schema, allowing you to update the mapping elements to match the current schema directly from the editor. -- The modernized **Console** panel is now enabled by default. If you encounter any issues, you can revert to the legacy **Console** panel by deselecting **Preferences** > **New Features** > **Use the modernized Console**. -- We improved the **Comparison** feature. The **Stop Comparison** button is now always available, allowing you to cancel at any time, including when an action is still in progress. -- We added a search bar to the comparison pane that lets you filter the list of changed documents by name, module, change type, or details. -- We improved tooltips for the Comparison pane: now you see what you expect in a single tooltip, for properties it is trimmed. -- We upgraded the `react-native` to 0.84.1 and bumped related dependencies. -- We improved offline database performance by removing unnecessary SQL transactions from read operations, reducing overhead particularly for read-heavy nanoflows. -- We updated the consistency error to appear on each duplicate operation within a resource of a Published REST service, instead of on the resource itself. -- We improved default values for the `SessionKeepAliveUpdatesInterval` (now 100 seconds) and `ClusterManagerActionInterval` (now five minutes) runtime settings. If these defaults are incompatible with the configured SessionTimeout, they will be automatically derived as before. -- We clean up duplicate cluster management tasks during startup. -- We added *themecache.css* files to *.gitignore* to reduce conflicts when edited by multiple users. -- We added temporary Java files to *.gitignore* to reduce conflicts when edited by multiple users. -- The modernized JavaScript Action Editor now updates when Maia edits the currently open JavaScript action. -- We changed conflicting page and microflow URLs from a consistency error to a warning. Conflicting URLs can indicate potential navigation issues, but they do not always occur in practice. -- Widgets with conditional visibility set to **false** are now excluded from exported pages. +* We improved the **Maia Undo All** button so it now reverts changes at the session level instead of the prompt level. +* The `OQL INSERT INTO SELECT` statement no longer requires column names in the `SELECT` part. +* In the logic editors, optional parameters are now visually distinguished with a dotted border, making it easier to identify which parameters are not required. +* We added a **Refresh schema** button to the mapping editor toolbar. This button appears when the mapping is out of sync with its underlying schema, allowing you to update the mapping elements to match the current schema directly from the editor. +* The modernized **Console** panel is now enabled by default. If you encounter any issues, you can revert to the legacy **Console** panel by deselecting **Preferences** > **New Features** > **Use the modernized Console**. +* We improved the **Comparison** feature. The **Stop Comparison** button is now always available, allowing you to cancel at any time, including when an action is still in progress. +* We added a search bar to the comparison pane that lets you filter the list of changed documents by name, module, change type, or details. +* We improved tooltips for the Comparison pane: now you see what you expect in a single tooltip, for properties it is trimmed. +* We upgraded the `react-native` to 0.84.1 and bumped related dependencies. +* We improved offline database performance by removing unnecessary SQL transactions from read operations, reducing overhead particularly for read-heavy nanoflows. +* We updated the consistency error to appear on each duplicate operation within a resource of a Published REST service, instead of on the resource itself. +* We improved default values for the `SessionKeepAliveUpdatesInterval` (now 100 seconds) and `ClusterManagerActionInterval` (now five minutes) runtime settings. If these defaults are incompatible with the configured SessionTimeout, they will be automatically derived as before. +* We clean up duplicate cluster management tasks during startup. +* We added *themecache.css* files to *.gitignore* to reduce conflicts when edited by multiple users. +* We added temporary Java files to *.gitignore* to reduce conflicts when edited by multiple users. +* The modernized JavaScript Action Editor now updates when Maia edits the currently open JavaScript action. +* We changed conflicting page and microflow URLs from a consistency error to a warning. Conflicting URLs can indicate potential navigation issues, but they do not always occur in practice. +* Widgets with conditional visibility set to **false** are now excluded from exported pages. ### Fixes -- We fixed an issue where import and export mappings incorrectly showed consistency errors for microflows with unmapped optional parameters. Optional parameters now use their default values when not provided in the payload. Converter microflows must have exactly one required parameter which receives the value to be converted and may have additional optional parameters. (Ticket 250969) -- We fixed an issue in the **Select Elements** dialog of an XML import or export mapping where reopening the dialog with previously checked elements that contained inheritance or choice-type children caused a validation error "Element '…' cannot be checked without a checked child element." when clicking OK. This happened because those elements were not expanded, so their children were not loaded and could not be validated. Studio Pro now automatically expands such elements before clicking OK in the **Select Elements** dialog, ensuring all required child elements are properly loaded and resolved. (Ticket 268403) -- We fixed an issue with the client where passing an empty string as a parameter to a microflow triggered an error. For example, when filtering options of a **Combobox** with a microflow, clearing the search string triggered the error. This occurred for apps with the [new string behavior](/refguide/runtime-tab/#new-string-behavior) disabled. (Ticket 271819) -- We fixed an issue where **Import** and **Cancel** buttons are not visible for certain resolutions and scalings. (Ticket 274077) -- We fixed an issue when an older offline client (from a Mendix version before 11.9.0) failed to synchronize with a HTTP 560 (Invalid JSONRequest) error, preventing the offline app from loading. (Ticket 274811) -- We fixed an issue where projects located in a folder whose name contained special characters (for example an '&') failed to run locally. (Ticket 275109) -- We fixed an issue where deployment of an application resulted in a "System.ArgumentOutOfRangeException: StartIndex cannot be less than zero." error. (Tickets 276326, 277841) -- We added Microsoft-related MIME types. (Tickets 276471, 276598, 276604, 276958) -- We fixed running OQL statements using INSERT INTO SELECT where the SELECT returns an empty result. (Ticket 277749) -- We fixed an issue where consistency checks for blob documents did not trigger when a previously excluded document it depended on was re-included. -- We fixed an issue where an extension contained in an add-on module did not get reloaded when the module got replaced with another with the same name. -- We fixed an issue where DEV extensions were not being displayed in the Extensions Overview. -- We fixed an issue where passing the icon as data URL in the Notification API did not show the icon. -- We fixed an issue where the **Go to** and **Back** buttons were incorrectly enabled when refreshing the comparison pane. -- We fixed an issue where the Comparison pane incorrectly showed "This is not a version controlled app" for a versioned app. -- We fixed an issue where the comparison pane got stuck on a loading spinner when starting a comparison with a comparison that’s already selected. -- We fixed an issue where the Microsoft Defender exclusion utility failed to run. -- Maia: We fixed an issue where microflows created by Maia had entity access enabled by default. -- We fixed an issue where Maia generated multiple **Create Variable** actions with the same variable name. -- In the logic editors, we fixed an Oops dialog when java actions parameters were not configured correctly. We added a new consistency check for this. -- We fixed an inconsistency where annotation connection point indices were stored in a different order than those of other microflow objects. -- We fixed an issue where Maia overlapped elements when trying to change existing microflows. -- We fixed an issue where Maia removed an element and did not fix the layout of a microflow. -- We fixed an issue where the chat input area did not increase in size based on the prompt length. -- We fixed an issue where the Maia input field was not cleared when opening or switching to a different app in Studio Pro. -- We fixed an issue where the Maia chat input area did not resize back to its original size after submitting a message. -- We fixed an issue where the Maia chat input area did not resize back to its original size when switching to a different or new app. -- We fixed an issue where Maia could not continue conversations that exceed context window limits. -- We fixed an issue related to a security improvement where entities configured with the **Nothing** or **Never** synchronization modes had their upload synchronization incorrectly blocked. Only entities with the **Online** synchronization mode should block client uploads. Additionally, when **Compatibility Mode** is enabled for an entity, it now fully restores **All Objects** behavior for both upload and download as originally intended. -- We fixed a runtime exception in Published OData when publishing an association to an object that is inaccessible due to OData security constraints. -- We fixed a runtime error in OData search queries for a `varchar` attribute with a limited column length and a search string longer than that limit. -- Page-editing tools are now available in the MCP server. -- We improved conversation overflow handling to prevent large messages from breaking the conversation. -- MCP server now uses coding agent's native web fetch tools instead of the ones exposed in Studio Pro. -- We fixed an issue where Studio Pro hung when renaming an entity attribute. -- We fixed various issues with MCP client stability. -- We fixed an issue where OQL generation would freeze. -- We fixed an issue where right-clicking a node in the app explorer would select the node's text label on macOS. -- We fixed an issue in the modernized console panel where the **Start built in database viewer** button was not disabled when the database viewer is not available. -- We fixed an issue in the modernized console panel where the scroll position lock was not reset when the runtime reconnected. -- We fixed an issue in the modernized Console Panel where auto-scroll always jumped to the bottom of the table when new logs were added, regardless of sort order. The table now scrolls to the latest log according to the current sort column and direction. -- On macOS, we improved table row selection after opening a context menu. Selecting a different row now requires fewer clicks and behaves more consistently, for example in the Modernized Console. -- We fixed an issue where pressing Escape to close a modal dialog would also close the sidebar. +* We fixed an issue where import and export mappings incorrectly showed consistency errors for microflows with unmapped optional parameters. Optional parameters now use their default values when not provided in the payload. Converter microflows must have exactly one required parameter which receives the value to be converted and may have additional optional parameters. (Ticket 250969) +* We fixed an issue in the **Select Elements** dialog of an XML import or export mapping where reopening the dialog with previously checked elements that contained inheritance or choice-type children caused a validation error "Element '…' cannot be checked without a checked child element." when clicking OK. This happened because those elements were not expanded, so their children were not loaded and could not be validated. Studio Pro now automatically expands such elements before clicking OK in the **Select Elements** dialog, ensuring all required child elements are properly loaded and resolved. (Ticket 268403) +* We fixed an issue with the client where passing an empty string as a parameter to a microflow triggered an error. For example, when filtering options of a **Combobox** with a microflow, clearing the search string triggered the error. This occurred for apps with the [new string behavior](/refguide/runtime-tab/#new-string-behavior) disabled. (Ticket 271819) +* We fixed an issue where **Import** and **Cancel** buttons are not visible for certain resolutions and scalings. (Ticket 274077) +* We fixed an issue when an older offline client (from a Mendix version before 11.9.0) failed to synchronize with a HTTP 560 (Invalid JSONRequest) error, preventing the offline app from loading. (Ticket 274811) +* We fixed an issue where projects located in a folder whose name contained special characters (for example an '&') failed to run locally. (Ticket 275109) +* We fixed an issue where deployment of an application resulted in a "System.ArgumentOutOfRangeException: StartIndex cannot be less than zero." error. (Tickets 276326, 277841) +* We added Microsoft-related MIME types. (Tickets 276471, 276598, 276604, 276958) +* We fixed running OQL statements using INSERT INTO SELECT where the SELECT returns an empty result. (Ticket 277749) +* We fixed an issue where consistency checks for blob documents did not trigger when a previously excluded document it depended on was re-included. +* We fixed an issue where an extension contained in an add-on module did not get reloaded when the module got replaced with another with the same name. +* We fixed an issue where DEV extensions were not being displayed in the Extensions Overview. +* We fixed an issue where passing the icon as data URL in the Notification API did not show the icon. +* We fixed an issue where the **Go to** and **Back** buttons were incorrectly enabled when refreshing the comparison pane. +* We fixed an issue where the Comparison pane incorrectly showed "This is not a version controlled app" for a versioned app. +* We fixed an issue where the comparison pane got stuck on a loading spinner when starting a comparison with a comparison that’s already selected. +* We fixed an issue where the Microsoft Defender exclusion utility failed to run. +* Maia: We fixed an issue where microflows created by Maia had entity access enabled by default. +* We fixed an issue where Maia generated multiple **Create Variable** actions with the same variable name. +* In the logic editors, we fixed an Oops dialog when java actions parameters were not configured correctly. We added a new consistency check for this. +* We fixed an inconsistency where annotation connection point indices were stored in a different order than those of other microflow objects. +* We fixed an issue where Maia overlapped elements when trying to change existing microflows. +* We fixed an issue where Maia removed an element and did not fix the layout of a microflow. +* We fixed an issue where the chat input area did not increase in size based on the prompt length. +* We fixed an issue where the Maia input field was not cleared when opening or switching to a different app in Studio Pro. +* We fixed an issue where the Maia chat input area did not resize back to its original size after submitting a message. +* We fixed an issue where the Maia chat input area did not resize back to its original size when switching to a different or new app. +* We fixed an issue where Maia could not continue conversations that exceed context window limits. +* We fixed an issue related to a security improvement where entities configured with the **Nothing** or **Never** synchronization modes had their upload synchronization incorrectly blocked. Only entities with the **Online** synchronization mode should block client uploads. Additionally, when **Compatibility Mode** is enabled for an entity, it now fully restores **All Objects** behavior for both upload and download as originally intended. +* We fixed a runtime exception in Published OData when publishing an association to an object that is inaccessible due to OData security constraints. +* We fixed a runtime error in OData search queries for a `varchar` attribute with a limited column length and a search string longer than that limit. +* Page-editing tools are now available in the MCP server. +* We improved conversation overflow handling to prevent large messages from breaking the conversation. +* MCP server now uses coding agent's native web fetch tools instead of the ones exposed in Studio Pro. +* We fixed an issue where Studio Pro hung when renaming an entity attribute. +* We fixed various issues with MCP client stability. +* We fixed an issue where OQL generation would freeze. +* We fixed an issue where right-clicking a node in the app explorer would select the node's text label on macOS. +* We fixed an issue in the modernized console panel where the **Start built in database viewer** button was not disabled when the database viewer is not available. +* We fixed an issue in the modernized console panel where the scroll position lock was not reset when the runtime reconnected. +* We fixed an issue in the modernized Console Panel where auto-scroll always jumped to the bottom of the table when new logs were added, regardless of sort order. The table now scrolls to the latest log according to the current sort column and direction. +* On macOS, we improved table row selection after opening a context menu. Selecting a different row now requires fewer clicks and behaves more consistently, for example in the Modernized Console. +* We fixed an issue where pressing Escape to close a modal dialog would also close the sidebar. ### Known Issues diff --git a/content/en/docs/releasenotes/studio-pro/9/9.24.md b/content/en/docs/releasenotes/studio-pro/9/9.24.md index 33ae81d4a44..fe70d8fda77 100644 --- a/content/en/docs/releasenotes/studio-pro/9/9.24.md +++ b/content/en/docs/releasenotes/studio-pro/9/9.24.md @@ -21,12 +21,12 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 9 release for a ### New Features -- We added a new runtime setting `FileStorage.S3.DisableChunkedEncoding` to allow disabling chunked encoding for S3 storage. (Tickets 274327, 272789) -- When Studio Pro is uninstalled, residual files created by Studio Pro are now also removed during the uninstall process. +* We added a new runtime setting `FileStorage.S3.DisableChunkedEncoding` to allow disabling chunked encoding for S3 storage. (Tickets 274327, 272789) +* When Studio Pro is uninstalled, residual files created by Studio Pro are now also removed during the uninstall process. ### Improvements -- We upgraded the BouncyCastle dependency to version 1.84. (Tickets 276629, 276631) +* We upgraded the BouncyCastle dependency to version 1.84. (Tickets 276629, 276631) #### Widget and Module Marketplace Metadata {#widget-module-metadata} @@ -34,14 +34,14 @@ We changed how Studio Pro stores Marketplace identity data for widgets. This dat ### Fixes -- We fixed an issue where tasks scheduled from a microflow would execute before the microflow ends. Activities that are meant to be executed in a taskqueue should always be picked up and executed after the microflow has fully completed. (Ticket 222845) -- We added Microsoft related MIME types. (Tickets 276471, 276598, 276604, 276958) +* We fixed an issue where tasks scheduled from a microflow would execute before the microflow ends. Activities that are meant to be executed in a taskqueue should always be picked up and executed after the microflow has fully completed. (Ticket 222845) +* We added Microsoft related MIME types. (Tickets 276471, 276598, 276604, 276958) ### Deprecations -- From July 6, 2026, we will drop support for the following database versions that are no longer supported by the vendors: - - PostgreSQL 13 - - MariaDB 10.6 +* From July 6, 2026, we will drop support for the following database versions that are no longer supported by the vendors: + * PostgreSQL 13 + * MariaDB 10.6 ## 9.24.42 diff --git a/content/en/docs/workstation/wks-installation.md b/content/en/docs/workstation/wks-installation.md index 22050bb4f2c..4bd84a58f8b 100644 --- a/content/en/docs/workstation/wks-installation.md +++ b/content/en/docs/workstation/wks-installation.md @@ -320,4 +320,4 @@ The administrator can choose to allow either one or a combination of the followi Simply add Bluetooth LE (BLE) devices that use the ATT protocol by entering the exact device name as displayed in your OS' device manager -Refer to [Message Syntax - Bluetooth](/mendix-workstation/device-syntax/#bluetooth) for a more in-depth explaination how to communicate with bluetooth devices. \ No newline at end of file +Refer to [Message Syntax - Bluetooth](/mendix-workstation/device-syntax/#bluetooth) for a more in-depth explaination how to communicate with bluetooth devices. diff --git a/content/en/docs/workstation/wks-message-syntax.md b/content/en/docs/workstation/wks-message-syntax.md index e562a594f07..8cfe5f42e00 100644 --- a/content/en/docs/workstation/wks-message-syntax.md +++ b/content/en/docs/workstation/wks-message-syntax.md @@ -37,7 +37,6 @@ Before sending messages to the File Device, review the following points: * Delimiter - The `#` character is used as a delimiter within messages. Paths and data may not contain the `#` character. * Case sensitivity - File and directory paths may be case-sensitive depending on the underlying operating system. For example, Linux paths are typically case-sensitive, while Windows paths are not.   - ### Message * `0#Path` - Initiate watching for changes in the specified `Path`. If `Path` is a directory, the device will watch for changes within that directory (creation, deletion, renaming, or modification of files/subdirectories). If `Path` is a file, the device will watch for changes to that specific file (modification, deletion, or renaming).