diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/element-selector-api.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/element-selector-api.md index 0cb8ecf5e01..7ac84f06295 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/element-selector-api.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/element-selector-api.md @@ -281,7 +281,6 @@ The optional query parameter allows you to filter selector results: | `name` | `string` | Filter by name | Documents, Entities | | `sdkName` | `string` | Filter by SDK name (for example, `Pages$Page`) | Documents only | - ## Preselecting Elements You can also pass an element ID as the `selectedElementId` property of the `Selector`. This ID can be either a Document, an Entity, or a Module. If a document or entity, the corresponding node on the selector form appears selected. If the ID belongs to a module, the corresponding node appears selected and expanded, and the `New` button is enabled so the user can immediately create a new document in that module. diff --git a/content/en/docs/control-center/apps/apps-overview.md b/content/en/docs/control-center/apps/apps-overview.md index 189eeacdc75..5578d0cad8b 100644 --- a/content/en/docs/control-center/apps/apps-overview.md +++ b/content/en/docs/control-center/apps/apps-overview.md @@ -64,9 +64,10 @@ When you select apps using the checkboxes in the table, a context menu appears a Clicking an app name in a tab or the search results opens its details page, which includes the following tabs: * **App Info** – Shows the **Description** and **App ID**, also found in your app's [Settings](/developerportal/general-settings/). -* **Members** – Lists the team members in the app development team. - * You can directly deactivate a team member from the app by clicking their name and selecting **Deactivate Member**. - * For other member management options, click **Manage Members**, which will open the [Team](/developerportal/general/team/#managing) page of the app. +* **Members** – Lists the team members in the project development team. + You can directly deactivate a team member from the project by clicking their name and selecting **Deactivate Member**. + For other member management options, click **Manage Members**, which will open the [Team](/developerportal/general/team/#managing) page of the project. + {{% alert color="info" %}}Mendix Admins cannot add or remove themselves from a project.{{% /alert %}} * **Environments** – Lists all Mendix Cloud environments. For the free Mendix Cloud environment, you can delete the environment on this tab. Once the free environment is deleted, all data will be removed. However, the app team members can still access the associated app repository in the Mendix Portal. If the app is not a licensed app, you can see the action menu ({{% icon name="three-dots-menu-horizontal" %}}) on the upper-right corner of the page. If the app is active, then you have the options to deactivate the app and delete the app; and if the app is deactivated, then you have the options to activate the app and delete the app. diff --git a/content/en/docs/control-center/company/mendix-admins.md b/content/en/docs/control-center/company/mendix-admins.md index a68e822d31f..acc40a04cbf 100644 --- a/content/en/docs/control-center/company/mendix-admins.md +++ b/content/en/docs/control-center/company/mendix-admins.md @@ -17,7 +17,7 @@ To remove an admin, hover over their name in the list, then click **Remove**. {{< figure src="/attachments/control-center/company/mendix-admins/mendix-admins.png" >}} {{% alert color="info" %}} -It is not possible to remove yourself as a Mendix Admin. +It is not possible to add or remove yourself as a Mendix Admin. {{% /alert %}} If the **Add Mendix Admin** button is not displayed, your company is using a user group in your IdP to assign Mendix Admins. For more information, refer to [IdP-managed Mendix Admins](/control-center/security-settings/#idp-managed-mendix-admins). diff --git a/content/en/docs/control-center/maia/maia-resources.md b/content/en/docs/control-center/maia/maia-resources.md index 1655ab2d0c8..a37486dd62a 100644 --- a/content/en/docs/control-center/maia/maia-resources.md +++ b/content/en/docs/control-center/maia/maia-resources.md @@ -97,4 +97,4 @@ To deprovision, select a plan of type **Provisioned** from your resources overvi {{% alert color="info" %}} Your subscription plan operates on a monthly bundle cycle. When you deprovision a resource, the deprovisioning takes effect at the end of the current subscription month. Until that date, you can still use the resource and status in the overview reads **Plan Deprovision Scheduled**. -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md b/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md index dd2c3cc09b8..b6c491990a0 100644 --- a/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md +++ b/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md @@ -29,7 +29,6 @@ Previous versions of the Operator did not manage `PodDisruptionBudgets`. Instead If you have manually created a `PodDisruptionBudget` for an app, delete it and instead specify the `PodDisruptionBudget` parameters [in the MendixApp CR](#pod-disruption-budget). {{% /alert %}} - {{% alert color="info" %}} Mendix Operator 2.28.0 specifies `unhealthyPodEvictionPolicy: AlwaysAllow` in the `PodDisruptionBudget`, allowing Kubernetes to evict crashlooping or unavailable pods without applying rules from the `PodDisruptionBudget`. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/advanced-audit-trail/_index.md b/content/en/docs/marketplace/platform-supported-content/modules/advanced-audit-trail/_index.md index f3623414112..13f7eb0c220 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/advanced-audit-trail/_index.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/advanced-audit-trail/_index.md @@ -250,4 +250,4 @@ The search functionality supports both exact matches and flexible filtering base * [Consuming Add-on Modules and Solutions](/refguide/consume-add-on-modules-and-solutions/) * [Audit Trail](/appstore/modules/audit-trail/) -* [Scheduled Events](/refguide/scheduled-events/) \ No newline at end of file +* [Scheduled Events](/refguide/scheduled-events/) diff --git a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-convui-bridge.md b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-convui-bridge.md index c7d8c193a05..dc8d8a4abe8 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-convui-bridge.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-convui-bridge.md @@ -70,4 +70,4 @@ To set up your own implementation, perform the following steps: 1. Create a new `CortexAgentDeployedModel` on the **CortexAgentDeployedModel_Overview** page by providing the required Agent configuration details. 2. Wire the created `CortexAgentDeployedModel` to the Conversational UI by using `CortexAgent_ProviderConfig_GetCreate` to create or retrieve the associated `ProviderConfig`. -The ProviderConfig is then used by the Conversational UI to drive the chat interface, routing messages through `ChatCompletions_CallCortexAgent` and maintaining conversation continuity through the `Conversation` entity. \ No newline at end of file +The ProviderConfig is then used by the Conversational UI to drive the chat interface, routing messages through `ChatCompletions_CallCortexAgent` and maintaining conversation continuity through the `Conversation` entity. diff --git a/content/en/docs/marketplace/platform-supported-content/services/event-broker.md b/content/en/docs/marketplace/platform-supported-content/services/event-broker.md index b6c65aa87b3..e550103b5f0 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/event-broker.md +++ b/content/en/docs/marketplace/platform-supported-content/services/event-broker.md @@ -159,7 +159,6 @@ Technical Contacts with a license to the Mendix Event Broker can manage this fea * For instructions on configuring AWS S3, see [Configuring a Bridge with AWS S3](#bridge-with-aws-s3). * For instructions on configuring Iceberg, see [Configuring a Bridge with Iceberg](#bridge-with-iceberg). - 4. After configuring the service and connecting events (as described in the bridge-specific sections above), click **Start** on the confirmation screen to deploy the bridge. {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/ebb_general_bridge_start.png" >}} @@ -553,7 +552,6 @@ To edit a bridge: **Iceberg** {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/edit-bridge/ebb_iceberg_edit_mode.png" class="no-border" >}} - 4. Once you have made your changes, you can: * Click **Apply** to save and apply the changes. A confirmation message will indicate if the changes were successful. Changes to the event configuration take effect when applied. After applying changes, the bridge status will change to **Reconfiguring** and will return to **Running** for HTTP, Azure Blob Storage, and AWS S3 bridges, or **Delivering** for Iceberg bridges, once the reconfiguration is complete. * Click **Cancel** to exit editing mode without saving any changes. @@ -683,4 +681,4 @@ The supported version of AsyncAPI is 2.0.0, in accordance with [AsyncAPI documen The file requirements are listed below: * Size: maximum file size is 1MB. -* Supported files: *.yml*, *.yaml*, *.json* \ No newline at end of file +* Supported files: *.yml*, *.yaml*, *.json* diff --git a/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md b/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md index 5c3f68611ac..4f439cf1cbb 100644 --- a/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md +++ b/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md @@ -342,5 +342,6 @@ Rich Text version 4 still has limitations that we will continue improving in the * Table caption Rich Text version 5 offers "class" styling to allow Rich Text to works in a strict CSP environment. This has limitations that we will continue to improve in the future. Current notable limitations are as follows: + * Resizing image, video, and tables does not work properly * Switching format from inline to class causes partial data loss on styling diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac04.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac04.md index 08b41ab9183..328b219344b 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac04.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac04.md @@ -236,6 +236,7 @@ Blob storage isolation is enforced through cloud IAM. The Infra. Operator is res | Azure Blob | Separate container, managed identity auth | For more information, see the following topics: + * [Published REST Services](/refguide/published-rest-services/) * [App Security](/refguide/security/) @@ -253,4 +254,4 @@ Each environment accesses its database through unique credentials scoped exclusi The following screenshot shows the database and file storage instance for each deployed app: -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-04-3.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-04-3.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0610.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0610.md index 7c550353c69..4a58b3d46a2 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0610.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0610.md @@ -53,4 +53,4 @@ For more information, refer to the following topics: As a Mendix application, Private Mendix Platform follows the principle of Least Privilege. In the Private Mendix Platform project's security settings, all user roles for the *User* and *Anonymous* roles are unchecked, preventing non-privileged users from gaining escalated access. -{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0610-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0610-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac11.md b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac11.md index 4df27246701..fff8a7e3f6c 100644 --- a/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac11.md +++ b/content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac11.md @@ -69,7 +69,7 @@ The following is a recommended implementation pattern and flow: 1. When absolute timeout is reached, block further interaction with protected pages. 2. Redirect users to the login flow or a dedicated re-authentication page, and require valid authentication before access is restored. - 3. Log session-expiration lock events (and optional warning acknowledgements) in application audit logs when required by policy. + 3. Log session-expiration lock events (and optional warning acknowledgements) in application audit logs when required by policy. {{< figure src="/attachments/private-platform/nist-ac/nist-ac-11-2.png" class="no-border" >}} @@ -95,4 +95,4 @@ To access the configuration page, in Private Mendix Platform, go to **Admin > Se The Private Mendix Platform session timeout configuration applies only to Private Mendix Platform sessions and does not control sessions inside customer-hosted Mendix applications. If customers require equivalent AC-11-compliant behavior in their own applications, they must implement the full session-expiration and re-authentication flow independently within the app, as discussed above. -For more details on how to properly configure and implement inactive session locks for individual Mendix applications, see [Session Management](/refguide/session-management/). \ No newline at end of file +For more details on how to properly configure and implement inactive session locks for individual Mendix applications, see [Session Management](/refguide/session-management/). 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 7e331dfab9c..65f4f688045 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 @@ -40,7 +40,7 @@ The following controls are related to this control: * [AC-20](/private-mendix-platform/nist-controls/ac-20/) * CA-03 * [CA-07](/private-mendix-platform/nist-controls/ca-07/) -* * CM-08 +* CM-08 * IA-02 * IA-03 * [IA-08](/private-mendix-platform/nist-controls/ia-08/) 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 7af3ccbd08c..7fd3f3b670b 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 @@ -35,7 +35,7 @@ The following controls are related to this control: * [AC-19](/private-mendix-platform/nist-controls/ac-19/) * CA-03 * [CA-07](/private-mendix-platform/nist-controls/ca-07/) -* * CM-08 +* CM-08 * IA-02 * IA-03 * [IA-08](/private-mendix-platform/nist-controls/ia-08/) diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au02.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au02.md index f3a72e5c329..38ff743d66a 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au02.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au02.md @@ -110,4 +110,4 @@ Private Mendix Platform displays logs with the time unit setting (for example, * When building Mendix applications, the App Implementer and Operator can generate and configure audit logging through the Mendix logging functionality. For more information, see the following documents: * [Logging](/refguide/logging/) -* [Log Message](/refguide/log-message/) \ No newline at end of file +* [Log Message](/refguide/log-message/) diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au12.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au12.md index 7477a09b861..b6d108607ca 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au12.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au12.md @@ -222,4 +222,4 @@ Private Mendix Platform's compliance with AU-12 currently has the following gaps Audit logging for customer-developed Mendix apps is the responsibility of the customer and app Implementer using the Mendix Audit Trail module or custom instrumentation. Private Mendix Platform does not provide or aggregate application-layer events. -The above evidence demonstrates that Private Mendix Platform satisfies a partial platform-scoped subset of AU-12 requirements. Full compliance requires coordinated implementation across Infra Implementer (infrastructure logs), and App Implementer along with the customer organization (application-level audit records). \ No newline at end of file +The above evidence demonstrates that Private Mendix Platform satisfies a partial platform-scoped subset of AU-12 requirements. Full compliance requires coordinated implementation across Infra Implementer (infrastructure logs), and App Implementer along with the customer organization (application-level audit records). diff --git a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au1201.md b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au1201.md index e7a24ebfe6e..0306883f8ce 100644 --- a/content/en/docs/private-platform/nist-controls/au/pmp-nist-au1201.md +++ b/content/en/docs/private-platform/nist-controls/au/pmp-nist-au1201.md @@ -164,4 +164,4 @@ Private Mendix Platform provides the platform-layer contribution to AU-12 (01) a * The Infra Implementer must produce and forward infrastructure logs. * The App Implementer and customer must generate and forward application-level audit logs. -With those integrations in place, IL4 AU-12 (01) can be met end-to-end across platform, infrastructure, and application components. \ No newline at end of file +With those integrations in place, IL4 AU-12 (01) can be met end-to-end across platform, infrastructure, and application components. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0306.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0306.md index df5596d1551..007a06f86fb 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0306.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0306.md @@ -154,4 +154,4 @@ Private Mendix Platform currently supports using AWS Secret Manager, Azure Key V ### Building Custom Mendix Applications -When the App Implementer needs to leverage custom encryption, they can do so in a compliant manner by using the [Mendix Encryption Module](/appstore/modules/encryption/). The module allows leveraging the configuration management processes, policies, and systems dictated by the customer. \ No newline at end of file +When the App Implementer needs to leverage custom encryption, they can do so in a compliant manner by using the [Mendix Encryption Module](/appstore/modules/encryption/). The module allows leveraging the configuration management processes, policies, and systems dictated by the customer. diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0501.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0501.md index be4c2edae39..6533757b6bc 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0501.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0501.md @@ -168,4 +168,4 @@ If a user tries to access pages or feature that they do no have access to, they Activities like deployments or using the admin tools are logged: -{{< figure src="/attachments/private-platform/nist-cm/nist-cm-0501-5.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-cm/nist-cm-0501-5.png" class="no-border" >}} 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 7bfda248d66..4f2b2a9bd9b 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 @@ -24,7 +24,7 @@ The information system prevents program execution in accordance with one or more The following controls are related to this control: -* * CM-08 +* CM-08 * PM-05 ## Responsibility diff --git a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm08.md b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm08.md index a97f943a346..35d6f2017e2 100644 --- a/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm08.md +++ b/content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm08.md @@ -19,6 +19,7 @@ This document describes how Private Mendix Platform fulfills the CM-08 control. ## Control The organization: + * Develops and documents an inventory of information system components that: * Accurately reflects the current information system. @@ -35,6 +36,7 @@ Organizations may choose to implement centralized information system component i Information deemed necessary for effective accountability of information system components includes, for example, hardware inventory specifications, software license information, software version numbers, component owners, and for networked components or devices, machine names and network addresses. Inventory specifications include, for example, manufacturer, device type, model, serial number, and physical location. The following controls are related to this control: + * CM-02 * [CM-06](/private-mendix-platform/nist-controls/cm-06/) * PM-05 @@ -156,4 +158,4 @@ For more information, refer to the following: * [Private Mendix Platform Release Notes](/releasenotes/private-platform/) * [SBOM Generation](/refguide/sbom-generation/) -{{< figure src="/attachments/private-platform/nist-cm/nist-cm-08-1.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/private-platform/nist-cm/nist-cm-08-1.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma06.md b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma06.md index 5ce64c6ef91..771851d77ab 100644 --- a/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma06.md +++ b/content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma06.md @@ -26,7 +26,7 @@ Organizations specify the information system components that result in increased The following controls are related to this control: -* * CM-08 +* CM-08 * [CP-02](/private-mendix-platform/nist-controls/cp-02/) * CP-07 * SA-14 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 16a8bfbb7c5..6dd7026e9ef 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 @@ -30,7 +30,7 @@ Clearly defined authorization boundaries are a prerequisite for effective securi The following controls are related to this control: -* * CM-08 +* CM-08 * [MP-04](/private-mendix-platform/nist-controls/mp-04/) * [RA-03](/private-mendix-platform/nist-controls/ra-03/) * SC-07 diff --git a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa08.md b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa08.md index 6f1c8186119..d07b44ea50f 100644 --- a/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa08.md +++ b/content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa08.md @@ -82,4 +82,4 @@ Mendix applies security engineering principles in the design and development of * [What is Amazon EC2 Auto Scaling? - Amazon EC2 Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html) * [Use an instance refresh to update instances in an Auto Scaling group - Amazon EC2 Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-instance-refresh.html) - * [Terraform Registry](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group) \ No newline at end of file + * [Terraform Registry](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group) 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 317c5bede9c..50c8e668e99 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 @@ -34,7 +34,7 @@ Organizations use the acquisition/procurement processes to require supply chain The following controls are related to this control: * AT-03 -* * CM-08 +* CM-08 * IR-04 * PE-16 * [PL-08](/private-mendix-platform/nist-controls/pl-08/) diff --git a/content/en/docs/private-platform/quickstart/_index.md b/content/en/docs/private-platform/quickstart/_index.md index 0068372dbf7..8c37c6f6de9 100644 --- a/content/en/docs/private-platform/quickstart/_index.md +++ b/content/en/docs/private-platform/quickstart/_index.md @@ -87,5 +87,3 @@ Before starting the installation process, make sure that you have all the necess * If you plan to use Azure Key Vault, see [Configuring a Secret Store with Azure Key Vault](/developerportal/deploy/secret-store-credentials/#azure-key-vault). ## Read More - - diff --git a/content/en/docs/private-platform/quickstart/pmp-quickstart-helm.md b/content/en/docs/private-platform/quickstart/pmp-quickstart-helm.md index 7d42a2fbedd..7b7137bd6c5 100644 --- a/content/en/docs/private-platform/quickstart/pmp-quickstart-helm.md +++ b/content/en/docs/private-platform/quickstart/pmp-quickstart-helm.md @@ -430,6 +430,7 @@ helmfile ... -l name=mx-privatecloud apply # Step 2: MANDATORY - sync mxplatform helmfile ... -l name=mxplatform apply ``` + {{% /alert %}} ### Other Commands @@ -1299,7 +1300,7 @@ The `mxplatform` component is used for Mendix application platform deployment. | --- | --- | --- | | `pclm.serviceUrl` | Yes | PCLM service endpoint | | `pclm.username` | Conditional | The PCLM username; not required when `secretProviderclass.enable` is set to `true` (for credentials injected from a secret manager) | -| `pclm.password ` | Conditional | The PCLM password; not required when `secretProviderclass.enable` is set to `true` (for credentials injected from a secret manager) | +| `pclm.password` | Conditional | The PCLM password; not required when `secretProviderclass.enable` is set to `true` (for credentials injected from a secret manager) | #### Spec Configuration @@ -1500,7 +1501,7 @@ The benefits of using Azure Container Registry with AKS include the following: * No secrets to manage * Automatic authentication -* Works across all namespaces +* Works across all namespaces * Production-ready ### AWS Elastic Container Registry (ECR) @@ -1907,7 +1908,7 @@ Workload Identity and Secret Provider Class are different approaches for databas * Workload Identity - Components use cloud identity to connect to databases (no passwords stored anywhere). * Secret Provider Class - Helm retrieves database passwords from a vault and injects them during installation. Passwords exist in vault as static secrets. -### Use Case 2: Mxplatform Database and Storage Authentication +### Use Case 2: Mxplatform Database and Storage Authentication For `mxplatform`, Workload Identity provides passwordless authentication for both database and storage at application runtime. @@ -1961,59 +1962,59 @@ To configure an Azure Storage Plan with Managed Identity, perform the following 1. Create the StoragePlans with Managed Identity. -```text -database: - postgres: - enabled: true - plans: - - planName: "azure-postgres-plan" - planType: "on-demand" - useAzureWIAuth: true - k8sServiceAccountName: "db-admin-sa" - host: "myserver.postgres.database.azure.com" - port: 5432 - database: "postgres" - user: "mendix-storage-admin" - password: "" # Empty when using Workload Identity - strictTLS: true -# Object Store Storage Plans -storage: - azure_blob: - enabled: true - plans: - - planName: "azure-blob-plan" - k8sServiceAccountName: "storage-admin-sa" - useAzureWIAuth: true - azureStorageAccount: "mystorageaccount" - azureResourceGroup: "my-resource-group" - azureAccountSubscriptionID: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" - azureContainerName: "" # Auto-created per environment - preventDataDeletion: false -``` + ```text + database: + postgres: + enabled: true + plans: + - planName: "azure-postgres-plan" + planType: "on-demand" + useAzureWIAuth: true + k8sServiceAccountName: "db-admin-sa" + host: "myserver.postgres.database.azure.com" + port: 5432 + database: "postgres" + user: "mendix-storage-admin" + password: "" # Empty when using Workload Identity + strictTLS: true + # Object Store Storage Plans + storage: + azure_blob: + enabled: true + plans: + - planName: "azure-blob-plan" + k8sServiceAccountName: "storage-admin-sa" + useAzureWIAuth: true + azureStorageAccount: "mystorageaccount" + azureResourceGroup: "my-resource-group" + azureAccountSubscriptionID: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" + azureContainerName: "" # Auto-created per environment + preventDataDeletion: false + ``` 2. Configure mxplatform in the Helmfile values. -```text -mxplatform: - enable: true - # REQUIRED: Let Operator create ServiceAccount - UseStoragePlanwithIRSA: true - pclm: - serviceUrl: "http://mx-privatecloud-license-manager" - username: "administrator" - password: "pclm-password" - spec: - appURL: "app.example.com" - sourceURL: "oci-image://myregistry.azurecr.io/app:1.0" - # Reference the Managed Identity-enabled plans - database: - servicePlan: "azure-postgres-plan" - storage: - servicePlan: "azure-blob-plan" - runtime: - applicationRootUrl: "https://app.example.com" - mxAdminPassword: "admin-password" -``` + ```text + mxplatform: + enable: true + # REQUIRED: Let Operator create ServiceAccount + UseStoragePlanwithIRSA: true + pclm: + serviceUrl: "http://mx-privatecloud-license-manager" + username: "administrator" + password: "pclm-password" + spec: + appURL: "app.example.com" + sourceURL: "oci-image://myregistry.azurecr.io/app:1.0" + # Reference the Managed Identity-enabled plans + database: + servicePlan: "azure-postgres-plan" + storage: + servicePlan: "azure-blob-plan" + runtime: + applicationRootUrl: "https://app.example.com" + mxAdminPassword: "admin-password" + ``` Mendix Operator creates the ServiceAccount with `azure.workload.identity/client-id annotation`, enabling passwordless Azure Database and Blob Storage access. diff --git a/content/en/docs/private-platform/quickstart/pmp-quickstart.md b/content/en/docs/private-platform/quickstart/pmp-quickstart.md index 17837bf0d6b..d929efb56e8 100644 --- a/content/en/docs/private-platform/quickstart/pmp-quickstart.md +++ b/content/en/docs/private-platform/quickstart/pmp-quickstart.md @@ -70,7 +70,7 @@ If your clusters can connect to a public registry with a passable network, skip 3. By default, mxpc-cli tools install the latest version of Mendix Operator. You can specify a different Mendix Operator version by using the following command: `./installer operator init -v="version number"` -## Installing the Mendix Operator {#install-operator} +## Installing the Mendix Operator {#install-operator} Install the Mendix Operator by doing the following steps: @@ -94,7 +94,7 @@ Configure the namespace by doing the following steps: 1. Click **Configure Namespace**. 2. Optional: If you want to run the Operator in Global mode, click **Global Operator**. -You must use a different namespace here than the Global namespace that you selected in step 4 above. Ensure that you do not use a namespace that is intended to be a managed namespace, that is, a namespace where you plan to deploy a Mendix app. The Global Operator namespace must be separate from managed namespaces, otherwise you may encounter unexpected results. + You must use a different namespace here than the Global namespace that you selected in step 4 above. Ensure that you do not use a namespace that is intended to be a managed namespace, that is, a namespace where you plan to deploy a Mendix app. The Global Operator namespace must be separate from managed namespaces, otherwise you may encounter unexpected results. 3. Optional: If you are not using the AWS Secret Manager, click **Database Plan** and fill out the required information. diff --git a/content/en/docs/refguide/modeling/app-explorer/modules/configure-add-on-and-solution-modules.md b/content/en/docs/refguide/modeling/app-explorer/modules/configure-add-on-and-solution-modules.md index bc23582b865..7c4c8c30031 100644 --- a/content/en/docs/refguide/modeling/app-explorer/modules/configure-add-on-and-solution-modules.md +++ b/content/en/docs/refguide/modeling/app-explorer/modules/configure-add-on-and-solution-modules.md @@ -44,7 +44,7 @@ You can see that documents/elements that are marked as usable have an eye icon ( Not all documents/elements can be marked as **Usable** in add-on and solution modules. Some can only be **Hidden**. -Below is the list of documents and elements that can be mark as **Usable**: +Below is the list of documents and elements that can be marked as **Usable**: * Domain model: * Entity and attributes (including external entities) diff --git a/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md b/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md index a268ac15dde..8878cab57d2 100644 --- a/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md +++ b/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md @@ -108,7 +108,6 @@ Key improvements are delivered through new module properties and a new `manifest The **Package** section on the **General** tab displays package identification information for the module. Studio Pro uses this information to track modules across versions, which is the foundation for more reliable module updates. - ### Module ID {#module-id} The module ID is a unique identifier for the module that remains the same across all versions. It determines whether two module packages represent the same module and is therefore the basis for module update compatibility. If two modules share the same module ID, Studio Pro can update one with the other. If the IDs differ, Studio Pro treats them as distinct modules. diff --git a/content/en/docs/refguide/modeling/menus/edit-menu/find-and-find-advanced.md b/content/en/docs/refguide/modeling/menus/edit-menu/find-and-find-advanced.md index be4d9071d05..4768ffc8519 100644 --- a/content/en/docs/refguide/modeling/menus/edit-menu/find-and-find-advanced.md +++ b/content/en/docs/refguide/modeling/menus/edit-menu/find-and-find-advanced.md @@ -108,8 +108,6 @@ Double-click an item in the **Find Results** pane to open the corresponding docu Click **Lock results** in the **Find Results** pane to keep the current results. The next time you click **Find Usages**, the results display in a second **Find Results** pane. This allows you to keep several search results. - - ## Read More * [Go to Option](/refguide/go-to-option/) 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 6d8d1b30d16..2537bdf8c17 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 @@ -11,7 +11,7 @@ description: "Native Template 17" ### Improvements -- We hardened the Android main screen against overlay and tapjacking attacks, and removed the unused `SYSTEM_ALERT_WINDOW` permission. +* We hardened the Android main screen against overlay and tapjacking attacks, and removed the unused `SYSTEM_ALERT_WINDOW` permission. ## 17.4.1 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 90f3070b2b4..da917daca16 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 @@ -11,7 +11,7 @@ description: "Native Template 19" ### Improvements -- We hardened the Android main screen against overlay and tapjacking attacks, and removed the unused `SYSTEM_ALERT_WINDOW` permission. +* We hardened the Android main screen against overlay and tapjacking attacks, and removed the unused `SYSTEM_ALERT_WINDOW` permission. ## 19.1.3 diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-20-rn.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-20-rn.md index adb5f6ec9e1..d11af754e79 100644 --- a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-20-rn.md +++ b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-20-rn.md @@ -11,7 +11,7 @@ description: "Release notes for Native Template 20." ### Improvements -- We hardened the Android main screen against overlay and tapjacking attacks, and removed the unused `SYSTEM_ALERT_WINDOW` permission. +* We hardened the Android main screen against overlay and tapjacking attacks, and removed the unused `SYSTEM_ALERT_WINDOW` permission. ## 20.0.0 diff --git a/content/en/docs/releasenotes/sdk/metamodel/metamodel-11/metamodel-11.14.md b/content/en/docs/releasenotes/sdk/metamodel/metamodel-11/metamodel-11.14.md index 59d4de1ce19..d4fe370a5eb 100644 --- a/content/en/docs/releasenotes/sdk/metamodel/metamodel-11/metamodel-11.14.md +++ b/content/en/docs/releasenotes/sdk/metamodel/metamodel-11/metamodel-11.14.md @@ -9,33 +9,42 @@ weight: 53 # Reduce weight by 1 to add this document to the top of the navigatio ### Microflows #### ClearFromClientAction (Element) + * We introduced the `clearType` property. * We introduced the `variableNames` property. ### BusinessEvents #### BusinessEventService (ModelUnit) + * We introduced this modelunit. #### BusinessEventDefinition (Element) + * We introduced this element. #### ServiceOperation (Element) + * We introduced this element. #### Channel (Element) + * We introduced this element. #### Message (Element) + * We introduced this element. #### MessageAttribute (Element) + * We introduced this element. #### AttributeEnumeration (Element) + * We introduced this element. #### AttributeEnumerationItem (Element) + * We introduced this element. This page has been generated automatically. diff --git a/content/en/docs/releasenotes/studio-pro/11/11.12.md b/content/en/docs/releasenotes/studio-pro/11/11.12.md index a6fbf1b1564..6f880065145 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.12.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.12.md @@ -50,11 +50,11 @@ weight: 88 ### Known Issues * The Maia Chat panel may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**. - * Workaround: Manually close the panel when it appears. + * Workaround: Manually close the panel when it appears. * When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning. - * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. + * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. * The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. - * Workaround: Click **New Chat** to make the **Skills** button appear without requiring a full restart. Note that **New Chat** is only available when the chat is not empty. + * Workaround: Click **New Chat** to make the **Skills** button appear without requiring a full restart. Note that **New Chat** is only available when the chat is not empty. * When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue. ## 11.12.3 {#11123} diff --git a/content/en/docs/releasenotes/studio-pro/11/11.14.md b/content/en/docs/releasenotes/studio-pro/11/11.14.md index b565fb7b256..1edddb56c28 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.14.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.14.md @@ -132,9 +132,9 @@ We recommend that apps and Marketplace modules upgrade to Java 25. ### Known Issues * The Maia Chat pane may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**. - * Workaround: Manually close the panel when it appears. + * Workaround: Manually close the panel when it appears. * When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning. - * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. + * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty. * The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat. - * Workaround: Click **New Chat** to make the **Skills** button appear without requiring a full restart. Note that **New Chat** is only available when the chat is not empty. + * Workaround: Click **New Chat** to make the **Skills** button appear without requiring a full restart. Note that **New Chat** is only available when the chat is not empty. * The `mx.exe module-import replace` and `mx.exe module-import update` commands will not rescue storage GUIDs after a module update, which will result in data loss. 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 5ea4d9f9bf5..75f9e323fd1 100644 --- a/content/en/docs/releasenotes/studio-pro/9/9.24.md +++ b/content/en/docs/releasenotes/studio-pro/9/9.24.md @@ -40,7 +40,6 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 9 release for a * We fixed an issue where publishing a microflow in a new a REST service allowed adding that service to read-only modules such as the System module. * We fixed an issue where local file storage does not use optimal directory structure. - ### Deprecations * We dropped support for the following database versions that are no longer supported by the vendors: diff --git a/static/attachments/appstore/platform-supported-content/modules/snowflake-ai-data-connector/cortex-agent-response-domain-model.png b/static/attachments/appstore/platform-supported-content/modules/snowflake-ai-data-connector/cortex-agent-response-domain-model.png deleted file mode 100644 index a0851c16294..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/modules/snowflake-ai-data-connector/cortex-agent-response-domain-model.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-create/chart-add-entity.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-create/chart-add-entity.png deleted file mode 100644 index b66e17dc961..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-create/chart-add-entity.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-create/charts-data-points.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-create/charts-data-points.png deleted file mode 100644 index b84c4a651f2..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-create/charts-data-points.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-create/charts-series.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-create/charts-series.png deleted file mode 100644 index fed294040bd..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-create/charts-series.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-rest/charts-rest-parameters.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-rest/charts-rest-parameters.png deleted file mode 100644 index 88e774be2ae..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-rest/charts-rest-parameters.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-rest/charts-rest-series.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-rest/charts-rest-series.png deleted file mode 100644 index 8c1bf8370c1..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-rest/charts-rest-series.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-rest/charts-rest-url.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-rest/charts-rest-url.png deleted file mode 100644 index 72100de1bf5..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-basic-rest/charts-rest-url.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-attributes.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-attributes.png deleted file mode 100644 index 7871122e105..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-attributes.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-data-entry.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-data-entry.png deleted file mode 100644 index 74f4ff01d93..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-data-entry.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-data-points.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-data-points.png deleted file mode 100644 index 70120500ce6..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-data-points.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-generate-pages.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-generate-pages.png deleted file mode 100644 index 3e820e559e1..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-generate-pages.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-model.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-model.png deleted file mode 100644 index bebb6785b2b..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-model.png and /dev/null differ diff --git a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-select.png b/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-select.png deleted file mode 100644 index d252e16735c..00000000000 Binary files a/static/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-dynamic-series/charts-dynamic-series-select.png and /dev/null differ diff --git a/static/attachments/private-platform/pmp-install-ni1.png b/static/attachments/private-platform/pmp-install-ni1.png deleted file mode 100644 index 9a2847bbaf5..00000000000 Binary files a/static/attachments/private-platform/pmp-install-ni1.png and /dev/null differ diff --git a/static/attachments/private-platform/pmp-install-ni2.png b/static/attachments/private-platform/pmp-install-ni2.png deleted file mode 100644 index d85544b0e3a..00000000000 Binary files a/static/attachments/private-platform/pmp-install-ni2.png and /dev/null differ