Merge branch 'mendix:development' into gemini

Author: Karuna-Mendix

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

@@ -41,7 +41,7 @@ You can also open the application directory containing the application `.mpr` fi
 
 To accelerate your extension development, Mendix provides an extension generator that creates a customizable sample extension.
 
-To use the generator, navigate to your desired source code directory and run the command `npm create @mendix/extension`. You may be prompted by `npm` to grant permission to install the generator. After installation, you will be guided through a series of questions to help configure your extension.
+To use the generator, navigate to your desired source code directory and run the command `npm create @mendix/extension@latest`. You may be prompted by `npm` to grant permission to install the generator. After installation, you will be guided through a series of questions to help configure your extension.
 
 You will be asked the following:
 

content/en/docs/control-center/security/private-connectivity/configure-private-connectivity.md

@@ -447,17 +447,19 @@ Once a connection is requested, it must be approved before the app environment c
 
 To approve a connection, follow these steps:
 
-1. On the **Connections** tab, find the connection you want to enable.
-2. Click **Approve**.
+1. In **Control Center**, access the **Entitlements** section, then go to the **Approval Requests** page.
+2. On the **Active Requests** tab, identify the connection you want to approve.
+3. Click **Approve**.
 
 {{% alert color="warning" %}}
-If this is the first connection that is approved for an app environment, the Technical Contact must [redeploy](/developerportal/deploy/mendix-cloud-deploy/deploying-an-app/) the environment to be able to use the connection. 
+Approval of a connection does not automatically activate it. For every approved connection, the Technical Contact must [redeploy the environment](/developerportal/deploy/mendix-cloud-deploy/deploying-an-app/) for it to become active and usable. 
 {{% /alert %}}
 
 To disable a connection, follow these steps:
 
-1. On the **Connections** tab, find the connection you want to disable.
-2. Click **Reject**.
+1. In **Control Center**, access the **Entitlements** section, then go to the **Approval Requests** page.
+2. On the **Active Requests** tab, identify the connection you want to reject.
+3. Click **Reject**.
 
 <!-- ## Activities
 

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

@@ -138,6 +138,10 @@ You can install and run the Mendix Operator in either Global or Standard mode. I
 * [Running the Mendix Operator in Global Mode](/developerportal/deploy/global-operator/)
 * [Running the Mendix Operator in Standard Mode](/developerportal/deploy/standard-operator/)
 
+{{% alert color="info" %}}
+For Mendix version 11.5.0 and above, you will need to install Mendix Operator version 2.24 or above.
+{{% /alert %}}
+
 ### Licensing the Application with Private Cloud License Manager
 
 You can license the Operator and Runtime of your application by configuring the Operator configuration with License Manager details. In order to start using Private Cloud License Manager, you need to first download the PCLM executable available in the Installation page. For more information, see [Private Cloud License Manager](/developerportal/deploy/private-cloud/private-cloud-license-manager/). The PCLM executable is available for download from this page.

content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md

@@ -15,6 +15,10 @@ It is essential to ensure that each namespace is exclusively managed by a single
 
 Global Operator installation is supported officially from Operator version v2.20.0 and above.
 
+{{% alert color="info" %}}
+For Mendix version 11.5.0 and above, you will need to install Mendix Operator version 2.24 or above.
+{{% /alert %}}
+
 ## Installing the Global Operator
 
 While installing the Mendix Operator in Global mode, you must first deploy the Mendix Operator and Agent within the *Global Operator namespace*. A Global Operator namespace comprises the Operator itself, the Agent, and the configuration that instructs the Operator on the namespaces it should oversee.

content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-standard-operator.md

@@ -13,6 +13,10 @@ When running the Mendix Operator in Standard mode, you must install it separatel
 It is essential to ensure that each namespace is exclusively managed by a single Operator. The deployment of two Operators, particularly with distinct versions, to manage the same namespace, may lead to conflicts, resulting in the cancellation and rollback of each operator's modifications.
 {{% /alert %}}
 
+{{% alert color="info" %}}
+For Mendix version 11.5.0 and above, you will need to install Mendix Operator version 2.24 or above.
+{{% /alert %}}
+
 ## Downloading the Configuration Tool {#download-configuration-tool}
 
 Before you can use the Mendix Operator in your namespace you need to install it and configure the services your app will use. Mendix provides you with a **Configuration Tool** which guides you through the process.

content/en/docs/developerportal/app-insights/feedback.md

@@ -169,6 +169,15 @@ The following options are available:
 * **Group Team Comments** – Displays all the comments left by your team for this group. You can leave comments here and add attachments to each comment.         
   Comments submitted here are only visible to your team members.
 
+## Organizing Feedback with Maia
+
+You can use Maia to organize unsorted feedback. To do that, click {{% icon name="sparkles" %}} (**Ask Maia**), then select one of these options:
+
+* **Suggest Groups** – Maia analyzes ungrouped feedback, and defines new groups for similar items. 
+* **Add Feedback to Group** – Maia analyzes ungrouped feedback, and suggests existing groups where it can be added.     
+
+In both cases, you can accept Maia's suggestion, or ask it to broaden or tighten the results it provides.
+
 ## Archive {#archive}
 
 On the **Archive** tab, everyone in your team can view all the archived feedback.

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

@@ -88,7 +88,7 @@ Often, you can use prompt engineering, RAG, and ReAct to build your use case and
 
 ## Prompt Engineering {#prompt-engineering}
 
-Prompt engineering is the activity of designing the input text that will be send to the LLM. This typically contains input from the end-user, enriched with instructions from the developer / administrator. A prompt typically contains:
+Prompt engineering is the activity of designing the input text that will be sent to the LLM. This typically contains input from the end-user, enriched with instructions from the developer / administrator. A prompt typically contains:
 
 * instructions on what the model should do
 * context and information that the model needs to follow the instructions
@@ -122,7 +122,7 @@ For example, Amazon Bedrock has the concept of [knowledge bases for Amazon Bedro
 
 ### PgVector Knowledge Base {#pgvectorknowledgebase}
 
-If your chosen architecture doesn't have fully-integrated RAG capabilities, or if you want tighter control of the RAG process, you can create and use your own knowledge base.
+If your chosen architecture does not have fully-integrated RAG capabilities, or if you want tighter control of the RAG process, you can create and use your own knowledge base.
 
 In this case you will have to index and store your knowledge yourself, and index your input data in order to retrieve the information with which you want to augment your prompt. For this you can use the [PgVector Knowledge Base module](/appstore/modules/genai/pgvector/) in combination with an embeddings model, to maintain and use your knowledge base. 
 

content/en/docs/mendix-portal/maia-portal.md

@@ -31,6 +31,8 @@ These are the tasks you can achieve with Maia in Mendix Portal:
     * On the [Board](/developerportal/project-management/epics/board/) page
     * On the [Planning](/developerportal/project-management/epics/planning/) page
 
+* **Maia for Feedback** – An AI-assisted tools that help you organize unsorted feedback into groups and themes. This is available on the [Feedback](/developerportal/app-insights/feedback/#organizing-feedback-with-maia) page.
+
 ## Maia Chat {#maia-chat}
 
 {{% alert color="info" %}}

content/en/docs/private-platform/pmp-quickstart.md

@@ -394,9 +394,77 @@ Install the Private Mendix Platform by doing the following steps:
 
 {{< figure src="/attachments/private-platform/pmp-install10.png" class="no-border" >}}
 
-### Adding Additional Components After Installing the Private Mendix Platform
+### Installing Maia for the Private Mendix Platform
 
-To ensure that components such as svix and PCLM work correctly, you should install them before you install the Private Mendix Platform itself. If you want to add a component after the Platform installation (for example, if you want to install svix because you decided to enable webhooks), you must perform the following steps:
+[Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/) refers to Mendix Platform capabilities that leverage [artificial intelligence (AI)](https://www.mendix.com/glossary/artificial-intelligence-ai/) and [machine learning (ML)](https://www.mendix.com/glossary/machine-learning/) to assist developers in application development. Private Mendix Platform currently offers support for Maia-assisted app creation. Other Maia capabilities, such as Maia Chat, will be made available in future releases.
+
+{{% alert color="info" %}}
+This feature is available as a beta release, available to selected customers. For more information about beta releases, see [Release Status](/releasenotes/release-status/).
+{{% /alert %}}
+
+To enable Maia for Private Mendix Platform, perform the following steps:
+
+1. Ensure that you fulfill the following prerequisites:
+
+    * Prepare the Amazon Bedrock LLM API key.
+    * Make sure that you can expose the Maia service. The installer currently only support the Ingress method. If you are using other methods (for example, Openshift route, HAPROXY, or others), contact the Private Mendix Platform team for assistance.
+    * Make sure that you know the Private Mendix Platform URL.
+
+2. Download the *maia-appgen-pmp.zip* file from your Private Mendix Platform download portal.
+3. Unzip the *maia-appgen-pmp.zip* file.
+4. Copy the *maia-appgen-pmp* directory the *images* sub-directory of the installer by running the following command: `cp -r maia-appgen-pmp <your installer>/pmp-binary-linux/images`
+5. Upload the Maia directory to your private registry by using the `installer init` command.
+6. Run the following command:  `./installer component -n=<Private Mendix Platform namespace>`. Maia must be installed at the same namespace as Private Mendix Platform.
+7. In the **Components at PMP ns** section, select **Maia**.
+8. Configure the following settings:
+
+    * **Image Prefix** - The registry and namespace (if it exists) where the *maia-appgen-pmp* image is located
+    * **Image Name** - The image name, for example, *maia-appgen-pmp* 
+    * **Image Tag** - The image tag of the AppGen image
+    * **Enable Ingress** - Enable or disable Nginx ingress
+    * **MXASSIST_COPILOT_AWS_SERVICE_REGION** - The Copilot AWS service region
+    * **MXASSIST_COPILOT_AWS_BEDROCK_REGION** - The Copilot AWS Bedrock region
+    * **Amazon_Bedrock_API_KEY** - An AWS Bedrock API key
+    * **MXASSIST_COPILOT_MXID3_URL** - The OIDC URL of Private Mendix Platform, in the following format: `<your Private Mendix Platform URL>/oidc/`
+
+9. After installing Maia, perform the following steps to connect to it from Studio Pro:
+
+    1. Download the patch file for Studio Pro 11.6 from the Private Mendix Platform download portal.
+    2. Manually set the `MaiaAppGenServiceBaseUrlP` key to the exposed URL of your *maia-appgen-pmp*.
+
+#### Uninstalling Maia
+
+If you want to uninstall Maia, you must do it manually, by running the following command: `helm unstall maia-appgen  -n=< maia namespace>`.
+
+### Installing PDF Document Generation for the Private Mendix Platform
+
+The PDF Document Generation module allows you to generate pixel-perfect PDF documents based on regular pages in your app.
+
+To enable PDF Document Generation for Private Mendix Platform, perform the following steps:
+
+1. Download the *document-generation-service.zip* file from your Private Mendix Platform download portal.
+2. Unzip the *document-generation-service.zip* file.
+3. Copy the *document-generation-service.zip* directory the *images* sub-directory of the installer by running the following command: `cp -r maia-appgen-pmp <your installer>/pmp-binary-linux/images`
+4. Upload the directory to your private registry by using the `installer init` command.
+5. Run the following command:  `./installer component -n=<Private Mendix Platform namespace>`. PDF Document Generation can be installed at the same namespace as Private Mendix Platform, or at any other namespace.
+6. In the **Components at PMP ns** section, select **PDF Gen**.
+7. Configure the following settings:
+
+    * **Namespace** - The namespace where PDF Document Generation will installed
+    * **Image Prefix** - The registry and namespace (if it exists) where the *document-generation-service* image is located
+    * **Image Name** - The image name, for example, *document-generation-service* 
+    * **Image Tag** - The image tag of the AppGen image, for example, *1.0.2*
+
+#### Uninstalling PDF Document Generation
+
+If you want to uninstall PDF Document Generation, perform the following steps:
+
+1. Unstall PDF Document Generation from its namespace by running the following command: `helm uninstall mx-private-document-generation  -n=<PDF Document Generation namespace>`.
+2. Remove the PDF data from the `pmp-component-config` configmap in your Private Mendix Platform namespace by running the following command: `kubectl edit configmap/pmp-component-config -n=<Private Mendix Platform namespace>`.
+
+### Adding the Svix and PCLM Components After Installing the Private Mendix Platform
+
+To ensure that the svix and PCLM components work correctly, you should install them before you install the Private Mendix Platform itself. If you want to add a component after the Platform installation (for example, if you want to install svix because you decided to enable webhooks), you must perform the following steps:
 
 1. Install the component as described in [Installing Private Cloud License Manager](#install-pclm) and [Installing the Svix Component](#install-svix).
 2. Run the command `./installer platform -n=<namespace name>`, where `-n` is the same namespace as the one where you installed Svix and PCLM.
@@ -428,7 +496,7 @@ If you have installed Private Mendix Platform before, you can upgrade it by doin
     {{< figure src="/attachments/private-platform/pmp-upgrade2.png" class="no-border" >}}
 
 {{% alert color="info" %}}
-To upgrade the PCLM component, select the option **Upgrade PCLM** in the upgrade wizard. For the Svix component, you can use the Svix panel to upgrade directly.
+To upgrade the PCLM or Maia components, select the relevant option in the upgrade wizard. For the Svix component, you can use the Svix panel to upgrade directly.
 {{% /alert %}}
 
 ## Running the Private Platform Configuration Wizard {#wizard}

content/en/docs/refguide/general/mxbuild.md

@@ -15,19 +15,16 @@ The table below can help you find the correct MxBuild. Copy a URL from the corre
 
 | Operating System | Mendix Version               | URL                                                          |
 | ---------------- | ---------------------------- | ------------------------------------------------------------ |
-| Linux (x64)      | All versions                 | `https://cdn.mendix.com/runtime/mxbuild-{mxversion}.tar.gz`  |
-| Windows (x64)    | All version of Studio Pro 11 | `https://cdn.mendix.com/runtime/win-mxbuild-{mxversion}.tar.gz` |
+| Linux (x64)      | All                          | `https://cdn.mendix.com/runtime/mxbuild-{mxversion}.tar.gz`  |
+| Windows (x64)    | 11                           | `https://cdn.mendix.com/runtime/win-mxbuild-{mxversion}.tar.gz` |
 
 {{% alert color="info" %}}
+In Mendix version 11.5.0 and above, `{mxversion}` follows a SemVer pattern `major.minor.patch` with the occasional pre-release suffix (for example, `11.5.0` or `11.6.0-beta.1` for planned pre-releases).
 
-A build number is included in the version, which has to be included in the link path mentioned above (for example, `11.0.0.9976` is the 9976 build of the 11.0.0 Studio Pro release).
-
-You can find the build number in path of your Mendix installation (for example, if your installation looks like this `C:\Program Files\Mendix\11.0.0.9976`, use this URL to get your files: [https://cdn.mendix.com/runtime/mxbuild-11.0.0.9976.tar.gz](https://cdn.mendix.com/runtime/mxbuild-11.0.0.9976.tar.gz)).
+In Mendix versions below 11.5.0, a build number is included in the version, which has to be included in `{mxversion}` in the link path mentioned above (for example, `11.0.0.73100` is the 73100 build of the 11.0.0 Studio Pro release). You can find the build number in the path of your Mendix installation (for example, if your installation looks like this `C:\Program Files\Mendix\11.0.0.73100`, use this URL to get your files: [https://cdn.mendix.com/runtime/mxbuild-11.0.0.73100.tar.gz](https://cdn.mendix.com/runtime/mxbuild-11.0.0.73100.tar.gz)).
 
 Any public version of Studio Pro in this [Studio Pro Releases List](https://marketplace.mendix.com/link/studiopro/) will allow you to download MxBuild files. If you experience trouble downloading files, make sure your build is listed there.
 
-As of Studio Pro 11.5.0, Mendix introduced a change in the versioning schema by dropping the fourth element, known as the build number. Versions now follow a SemVer pattern `major.minor.patch` with the occasional pre-release suffix (for example, `11.5.0` or `11.6.0-beta.1` for planned pre-releases).
-
 {{% /alert %}}
 
 You can extract the files using an archival tool, such as [7-Zip](https://www.7-zip.org/).