Merge branch 'development' of https://github.com/mendix/docs into development

Author: Yiyun333

content/en/docs/apidocs-mxsdk/apidocs/governance/user-identifiers-api.md

@@ -16,6 +16,10 @@ The User Identifiers API is available for Mendix Admins.
 
 The User Identifiers API allows Mendix admins to perform operations related to user identifiers within their company, such as obtaining the user UUIDs of specific email addresses.
 
+{{% alert color="info" %}}
+The User Identifiers API supports a maximum of 100 users per request/response.
+{{% /alert %}}
+
 ## Authentication{#authentication}
 
 Authentication for the User Identifiers API uses a personal access token (PAT).

content/en/docs/deployment/mendix-cloud-deploy/pipelines.md

@@ -332,6 +332,8 @@ To trigger pipelines based on Teamserver push (Git), Mendix automatically create
 
 Pipelines is in public beta and is undergoing optimizations. Initial stages may involve occasional slowness, leading to pipeline failures. Mendix is committed to resolving these issues swiftly and appreciates your understanding.
 
+Pipeline runs will not be picked up and executed if Pipelines is undergoing maintenance.
+
 It is not currently possible to add the same pipeline step more than once in a pipeline. This will be improved in the future.
 
 ## Read More

content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md

@@ -194,13 +194,13 @@ kind: OperatorConfiguration
 # omitted lines for brevity
 # ...
 spec:
-  baseOSImageTagTemplate: 'ubi8-1-jre{{.JavaVersion}}-entrypoint'
+  baseOSImageTagTemplate: 'ubi9-1-jre{{.JavaVersion}}-entrypoint'
 ```
 
 At the moment, the `baseOSImageTagTemplate` can be set to one of the following values:
 
-* `ubi8-1-jre{{.JavaVersion}}-entrypoint` - to use Red Hat UBI 8 Micro images; this is the default option.
-* `ubi9-1-jre{{.JavaVersion}}-entrypoint` - to use Red Hat UBI 9 Micro images; this option can be used to use a newer OS and improve security scores.
+* `ubi8-1-jre{{.JavaVersion}}-entrypoint` - to use Red Hat UBI 8 Micro images; this option can be used for some cases where backward compatibility is needed.
+* `ubi9-1-jre{{.JavaVersion}}-entrypoint` - to use Red Hat UBI 9 Micro images; this is the default option.
 
 {{% alert color="info" %}}
 
@@ -964,6 +964,10 @@ In addition to internal Mendix Runtime paths, `/tmp` is mounted for any temporar
 If your app works without issues when read-only root filesystem is enabled, it is best to enable it wherever possible. We recommend using a non-production environment to validate that your app keeps working correctly with a read-only RootFS.
 {{% /alert %}}
 
+{{% alert color="warning" %}}
+Enabling the `runtimeReadOnlyRootFilesystem` option causes the `model/resources` directory to be empty. If your app (or a Marketplace module such as SAML) uses the `model/resources` directory for resources such as configuration data, consider moving those resources to another location (for example, `model/userlib`) or loading them from FileDocument entities.
+{{% /alert %}}
+
 ### GKE Autopilot Workarounds {#gke-autopilot-workarounds}
 
 In GKE Autopilot, one of the key features is its ability to automatically adjust resource settings based on the observed resource utilization of the containers. GKE Autopilot verifies the resource allocations and limits for all containers, and makes adjustments to deployments when the resources are not as per its requirements.

content/en/docs/refguide/general/mx-command-line-tool/analyze-mpr.md

@@ -36,6 +36,8 @@ The `OPTIONS` are described in the table below:
 
 To identify which types of documents (pages, microflows, etc.) have the largest contribution to the MPR file size, you can focus on the **Size by unit type** section, where the number of occurrences and file size contribution are displayed in percentage.
 
+You can use the MPR Tool to get more details. You can find it at *C:\Program Files\Mendix\<version>\modeler\MprTool.exe* (where <version> should be replaced with your installed Mendix version). After opening the *.mpr* file for your app, use **Search** > **Find unit by ID** to find the name and module for a particular unit.
+
 ### Examples
 
 Valid examples are given below:

content/en/docs/refguide/modeling/domain-model/oql/_index.md

@@ -10,6 +10,10 @@ The Mendix Object Query Language (OQL) is a relational query language inspired b
 
 In addition, OQL can use predefined relations (associations) to easily join objects without having to calculate which columns should be coupled. Despite these differences, many SQL keywords also work in OQL.
 
+{{% alert color="info" %}}
+OQL can only be used on persistable and view entities and the associations between them. It cannot be used with non-persistable or external [entities](/refguide/entities/). 
+{{% /alert %}}
+
 Some examples of OQL queries are:
 
 * `SELECT LastName FROM Sales.Customer` – retrieves the family names of all customers

content/en/docs/refguide/modeling/menus/version-control-menu/commit-dialog.md

@@ -8,16 +8,14 @@ weight: 20
 
 The commit dialog is used for committing changes to the Team Server. You can enter a message and, if applicable, select related stories.
 
-{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/commit-dialog/commit-dialog-stories.png" alt="Version Control Menu" class="no-border" width="400" >}}
-
 ## Branch
 
 At the top of the dialog box you will see the branch which you are committing. This will be one of the following:
 
 | Branch Description | Notes |
 | --- | --- |
-| {{< figure src="/attachments/refguide/modeling/menus/version-control-menu/commit-dialog/commit-main.png" alt="Version Control Menu" class="no-border" >}} |  you are committing the main line |
-| {{< figure src="/attachments/refguide/modeling/menus/version-control-menu/commit-dialog/commit-branch.png" alt="Version Control Menu" class="no-border" >}} |  you are committing the specified branch |
+| {{< figure src="/attachments/refguide/modeling/menus/version-control-menu/commit-dialog/commit-main.png" alt="Main line icon" class="no-border" >}} |  you are committing the main line |
+| {{< figure src="/attachments/refguide/modeling/menus/version-control-menu/commit-dialog/commit-branch.png" alt="Commit branch icon" class="no-border" >}} |  you are committing the specified branch |
 
 ## Message
 
@@ -27,20 +25,44 @@ Enter a message describing the changes you have made. This message may contain m
 
 ### Related Stories {#stories}
 
-{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/commit-dialog/commit-dialog-stories.png" alt="Version Control Menu" class="no-border" width="400" >}}
-
 Tick the boxes next to the stories that are related to your commit. Mendix recommends committing a small number of changes at a time, so there is usually just one related story.
 
 ### Changes in Model
 
-{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/commit-dialog/commit-dialog-model-changes.png" alt="Version Control Menu" class="no-border" width="400" >}}
-
 If there are changes in the model this tab shows a summary of those changes. For more information on how changes are reported in Studio Pro, see [Changes Pane](/refguide/changes-pane/).
 
-### Changes on Disk
+There are several scenarios and options that you can choose when committing. Two of these options are represented in the image below:
+
+{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/commit-dialog/commit-options.jpg" alt="Several options when committing" >}}
+
+#### Commit and Push
+
+{{% alert color="info" %}}
+
+**Commit and Push** is the recommended flow to stay in-sync with your team and avoid conflicts.
+
+{{% /alert %}}
+
+Your changes are committed and pushed to the server.
 
-{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/commit-dialog/commit-dialog-disk-changes.png" alt="Version Control Menu" class="no-border" width="400" >}}
+#### Commit Locally
+
+Changes are committed to your local working copy and are not pushed to the sever.
+
+#### Commit and Combine {#combine}
+
+If someone else committed a change since the last time you pulled your branch, you will have to pull and merge their changes before you can push to the server. This process is called **Commit and Combine** in the [Commit](/refguide/commit-dialog/) dialog box. **Commit and Combine** will first create a local commit and then automatically do a pull. After resolving any conflicts, you can push the combined version to the server.
+
+{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/commit-dialog/commit-and-combine.jpg" alt="Commit and combine changes" >}}
+
+{{% alert color="warning" %}}
+
+After you reviewed the changes, you will need to push your changes, as **Commit and Combine** only updates your local copy and does not push your changes to the server. 
+
+{{% /alert %}}
+
+### Changes on Disk
 
-If there are changes on disk this page shows a summary of those changes. Click **Open containing folder** to open the folder containing the selected file in Windows Explorer.
+If there are changes on disk this tab shows a summary of those changes. Click **Open containing folder** to open the folder containing the selected file in Windows Explorer.
 
 The tab page is hidden if there are no disk changes. Often, there are model changes but the only change on disk is the app file (*.mpr*) reflecting these model changes. In this case, it is also hidden, because it does not add useful information.

content/en/docs/refguide/version-control/on-premises-git.md

@@ -34,7 +34,11 @@ Make sure you have completed the following prerequisites:
 
 ## Supported Authentication Mechanisms
 
-Currently, Mendix only supports HTTP Basic authentication for Git service providers. With most providers, this takes the form of using of personal access tokens (PATs).
+Currently, Mendix only supports [HTTP Basic authentication](#http) and [Windows Authentication](#windows) for Git service providers. 
+
+### HTTP Basic Authentication {#http}
+
+With most providers, HTTP basic authentication takes the form of using of personal access tokens (PATs).
 
 To use PAT (or another equivalent), you need to specify it in the **Password** field when Studio Pro requests credentials for the version control server:
 
@@ -45,6 +49,13 @@ Currently Mendix keeps PAT using operating system supported solutions:
 * For Windows, Mendix uses a credential locker mechanism, accessible to users by using Credential Manager.
 * For MacOs, Mendix uses keychains, accessible to users by using Keychain Access.
 
+### Windows Authentication {#windows}
+
+Studio Pro can use Windows Authentication for Git service providers that support it. When you use Windows Authentication, you do not need to provide a password. 
+
+You can enable Windows Authentication in [Git Preferences settings](/refguide/preferences-dialog/#enable-windows-authentication).
+
+
 ## Setting Up the Environment
 
 This section describes how to configure a Git versioned app in Studio Pro. You need a Git server and an initially unversioned Mendix app.

content/en/docs/refguide/version-control/using-version-control-in-studio-pro/_index.md

@@ -143,7 +143,7 @@ A tool you can consider using is TortoiseGitMerge, shipped as part of [TortoiseG
 Comparing files on disk with the original is currently not supported on macOS.
 {{% /alert %}}
 
-Committing is only allowed if your working copy is up to date with the repository. If someone else committed a change since the last time you pulled, you will have to pull first. This is because the revision you create with the commit should incorporate both your changes and the changes by the other person. Updating will combine the latest changes in the repository with your changes. After reviewing the result and fixing any conflicts, you can commit again.
+Committing is only allowed if your working copy is up to date with the repository. If someone else committed a change since the last time you pulled, you will have to pull first (this process is called **Commit and Combine** in the [Commit](/refguide/commit-dialog/#combine) dialog box). This is because the revision you create with the commit should incorporate both your changes and the changes by the other person. Updating will combine the latest changes in the repository with your changes. After reviewing the result and fixing any conflicts, you can commit again. 
 
 ### Pushing {#pushing}
 

content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md

@@ -12,6 +12,19 @@ For information on the current status of deployment to Mendix for Private Cloud
 
 ## 2025
 
+### March 10, 2025
+
+#### License Manage CLI v0.10.1
+
+* We have updated this component to use the latest dependency versions in order to improve security score ratings for container images. This update will allow us to address CVE-2024-45337 and CVE-2024-45338.
+
+#### Mendix Operator v2.21.1 {#2.21.1}
+
+* We have updated components to use the latest dependency versions in order to improve security score ratings for container images.
+* For new installations, the Operator now uses ubi9 as the base image for Mendix apps. Existing installations will keep their configuration and stay on ubi8. For more information on base image versions, see the [Runtime Base Image](/developerportal/deploy/private-cloud-cluster/#runtime-base-image) section.
+* We have fixed a regression that caused the `model/resources` directory to appear empty and caused problems with some Marketplace modules, such as SAML (Ticket 242648).
+* Upgrading to Mendix Operator v2.21.0 from a previous version now restarts environments managed by that version of the Operator. Environments with 2 or more replicas and a **PreferRolling** update strategy are restarted without downtime.
+
 ### March 6, 2025
 
 #### Portal Improvements
@@ -40,6 +53,12 @@ For information on the current status of deployment to Mendix for Private Cloud
 
 With the introduction of ephemeral storage requests and limits, building an app requires at least 2 GB of ephemeral storage available on the Kubernetes node. If your nodes do not have enough temporary storage, the build pods cannot start and their status remains **Pending**. To resolve this issue, you can lower the values for `ephemeral-storage` in the [buildResources](/developerportal/deploy/private-cloud-cluster/#resource-definition-ocm) configuration.
 
+#### Known Issue
+
+This issue has been fixed in Mendix Operator [version 2.21.1](#2.21.1).
+
+* The `model/resources` directory is empty when starting the app, causing issues with some Marketplace modules (such as SAML) that use that location to store configuration data and other resources.
+
 ### February 12, 2025
 
 #### Documentation Updates