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

Author: MariaShaposhnikova

content/en/docs/apidocs-mxsdk/apidocs/frontend/client-api.md

@@ -9,9 +9,15 @@ weight: 30
 
 Enrich the user interface of your applications by building on top of our web client APIs. Use standard web technology in combination with our powerful APIs to build any widget you want.
 
-## Client APIs
+## Client API
+
+The client API is compatible with both the React and the Dojo client.
+
+* [Mendix 10 Client API](https://apidocs.rnd.mendix.com/10/client-mx-api/index.html)
+
+## Legacy Client APIs
 
 * [Mendix 10 React Client API](https://apidocs.rnd.mendix.com/10/client-react/index.html)
-* [Mendix 10 Client API](https://apidocs.rnd.mendix.com/10/client/index.html)
-* [Mendix 9 Client API](https://apidocs.rnd.mendix.com/9/client/index.html)
-* [Mendix 8 Client API](https://apidocs.rnd.mendix.com/8/client/index.html)
+* [Mendix 10 Dojo Client API](https://apidocs.rnd.mendix.com/10/client/index.html)
+* [Mendix 9 Dojo Client API](https://apidocs.rnd.mendix.com/9/client/index.html)
+* [Mendix 8 Dojo Client API](https://apidocs.rnd.mendix.com/8/client/index.html)

content/en/docs/appstore/use-content/platform-supported-content/modules/database-connector-mx10.md

@@ -55,9 +55,9 @@ This connector supports the following statements:
 
 ### Limitations 
 
-* `SELECT` queries and `Stored Procedure` can be saved only if they are successfully executed and a response structure is created
+* `SELECT` queries and `Stored Procedure` can be saved only if they are successfully executed and a response structure is created (this is no longer a limitation as of Studio Pro 10.20)
 * The connector supports columns and stored procedure parameters with primitive data types only
-* If column names contain special characters, use an alias for the column name
+* If column names contain special characters, use an alias for the column name (this is no longer a limitation as of Studio Pro 10.20)
 * Parameters are only supported for filter values (prepared statements)
 * Certificate-based authentication for PostgreSQL is not supported on macOS
 
@@ -123,6 +123,18 @@ Then, use the parameter in the query:
 
 `select * from customers where contactFirstName like {paramFirstName}`
 
+{{% alert color="info" %}}
+If you need to pass a list of values to a parameter, you can use the following approach:
+
+`WITH empids AS (
+SELECT empid FROM json_table( {EmpIdList}, '$[*]' columns ( empid number path '$' )) 
+)
+SELECT *
+FROM emp WHERE empno IN (SELECT empid FROM empids);`
+
+where parameter `EmpIdList` is of type String with the value `[1,7946,3,4,7942,7943,7945]`.
+ {{% /alert %}}
+
 ### Using Query Response {#use-query-response}
 
 After [querying the database](#query-database), you can view the response in the **Response** screen. 
@@ -166,6 +178,14 @@ You can now use the microflow in your app. Below is an example of a configured m
 See the [Integration Activities](/refguide/integration-activities/) section of the *Studio Pro Guide* for further explanation of the properties in this activity.
 See the [Call Stored Procedure](/howto/integration/use-the-external-database-connector/) section of *Use the External Database Connector* for more information on how to call a stored procedure.
 
+### Saving Intermediate Queries
+
+As of Studio Pro 10.20, it is possible to save queries at intermediate stages.
+
+Studio Pro's standard save behavior is implemented, including the dot indicator in the tab to signify unsaved changes.
+
+Press <kbd>Ctrl</kbd> + <kbd>S</kbd> to store changes when switching to a different query or performing another action. Make sure to not to use queries that are saved intermediately in the [Query External Database](/refguide/query-external-database/) activity of a microflow, as it might lead to runtime exception.
+
 ## Use Certificate-Based Authentication for PostgreSQL Connections {#postgres-ssl}
 
 ### Prerequisites 

content/en/docs/appstore/use-content/platform-supported-content/modules/snowflake/mendix-data-loader.md

@@ -139,6 +139,55 @@ For example, for a data source with the ID *40FJYP9D*, the resulting statement w
 CALL MENDIX_DATA_LOADER.MX_FUNCTIONS.RUN_INGESTION_JOB('40FJYP9D','');
 ```
 
+## Setting Up Mail Notifications on Failed Task Execution
+
+Snowflake provides a built-in functionality for alerts and notifications. This `ALERT` object lets you specify a conditional expression to check if tasks have failed and send notifications if required. 
+
+To use this functionality, perform the following steps:
+
+1. Create a [notifcation integration email](https://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-email).
+2. Create an [ALERT](https://docs.snowflake.com/en/sql-reference/commands-alert) using the notification integration and the ["SYSTEM$SEND_EMAIL"](https://docs.snowflake.com/en/sql-reference/stored-procedures/system_send_email) system function.
+
+For more information about using external integrations for sending all types of notifications, see [Introduction to Snowflake's data pipeline alerts & notifications](https://medium.com/snowflake/introduction-to-snowflakes-data-pipeline-alerts-notifications-9beac8d127cc).
+
+### Sample SQL to Set up a Mail Notification
+
+The following is a sample SQL template which you can customize with your data and execute in a worksheet:
+
+```sql
+CREATE DATABASE IF NOT EXISTS <db name>;
+
+CREATE SCHEMA IF NOT <schema name>;
+
+USE SCHEMA <schema name>;
+
+CREATE OR REPLACE NOTIFICATION INTEGRATION <NOTIFICATION INTEGRATION name>
+  TYPE = EMAIL
+  ENABLED = TRUE
+  ALLOWED_RECIPIENTS = ('<mail1@company.com>', '<mail2@company.com>', ...);
+
+CREATE OR REPLACE ALERT <ALERT name>
+  WAREHOUSE = <warehouse name>
+  SCHEDULE = '<integer> MINUTE' -- Or use CRON e.g. 15 * * * * UTC
+  IF (
+    EXISTS (
+      SELECT 1
+      FROM SNOWFLAKE.ACCOUNT_USAGE.TASK_HISTORY
+      WHERE (STATE = 'FAILED' OR STATE = 'FAILED_AND_AUTO_SUSPENDED') AND NAME = '<task name>'
+        AND SCHEDULED_TIME >= CONVERT_TIMEZONE('UTC',DATEADD(MINUTE, -<integer>, CURRENT_TIMESTAMP()))
+    )
+  )
+  THEN CALL SYSTEM$SEND_EMAIL(
+    '<NOTIFICATION INTEGRATION name>',
+    ('<mail1@company.com>', '<mail5@company.com>', ...) --Subset of ALLOWED_RECIPIENTS in NOTIFICATION INTEGRATION. 
+    '<Mail subject>',
+    '<Mail Body>.'
+  );
+
+ALTER ALERT <ALERT name> RESUME; -- The ALERT has STATE Suspended when created and is started by this statement
+
+SHOW ALERTS;
+```
 ## Verifying the Access Token
 
 When using OAuth authentication with the Mendix Data Loader, it is crucial to verify the access token received by your Mendix application. This verification process ensures the token's authenticity and integrity, protecting your application from unauthorized access attempts.

content/en/docs/appstore/use-content/platform-supported-content/services/oidc-provider.md

@@ -184,7 +184,7 @@ Every end-user that is known in Admin module also needs to be known in the OIDC
     | Accounts | Open page 'OpenIDConnectProvider.AccountDetail_Overview' | Administrator |
     | Active Sessions | Open page 'Administration.ActiveSessions' | Administrator |
     | Scheduled Events | Open page 'Administration.ScheduledEvents' | Administrator |
-    | Runtime Instances | Open page 'Administration.RunteimInstances' | Administrator |
+    | Runtime Instances | Open page 'Administration.RuntimeInstances' | Administrator |
     | My Account | Call microflow 'Administration.ManageMyAccount' | User |
     | OpenID Connect | Open page 'OpenIDConnectProvider.OpenIDConnect_Dashboard' | Administrator |
     | Mx Objects | Open page 'MxModelReflection.MxObjects_Overview' | Administrator |

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

@@ -92,7 +92,7 @@ Click **Copy ID** ({{% icon name="copy" %}}) on a pipeline design to copy the de
 
 Click **More Options** ({{% icon name="three-dots-menu-horizontal-filled" %}}) > **Edit** on a pipeline design to go to its **Details** page. From there, you can view and edit the pipeline details, as described in the [Editing a Pipeline](#edit-pipeline) section below.
 
-Click **More Options** ({{% icon name="three-dots-menu-horizontal-filled" %}}) > **Delete** to delete a pipeline design.
+Click **More Options** ({{% icon name="three-dots-menu-horizontal-filled" %}}) > **Delete** to delete a pipeline design. You cannot delete a pipeline design if it is used in any currently running pipelines. Instead, you must wait for the run to finish before you delete the design.
 
 {{% alert color="warning" %}}
 If you delete a pipeline design in the **Designs** tab, any run history associated with that pipeline design is deleted from the **Runs** tab.
@@ -121,6 +121,8 @@ From your pipeline design's **Details** page, you can add, remove, and configure
 {{< figure src="/attachments/deployment/mendix-cloud-deploy/pipelines/pipeline-design.png" alt="" >}}
 
 {{% alert color="info" %}}
+For pipelines that are currently running, the page shows the current state of the steps (finished, running, or not started).
+
 Active pipelines cannot be edited; if you want to edit an existing pipeline, make sure it is deactivated.
 {{% /alert %}}
 
@@ -140,6 +142,8 @@ This is a mandatory step for each pipeline; you cannot delete this step. This st
 
 {{% alert color="info" %}}
 The Teamserver push (Git) command requires a Git repository. Customers using an SVN repository for their Mendix app cannot use this trigger.
+
+Ensure that you only create one pipeline per app with the Teamserver push (Git) trigger and the same [branch expression](#branch-expression). If you create multiple pipelines with the Teamserver push (Git) trigger and the same expression, only the pipeline that you created first is executed.
 {{% /alert %}}
 
 ##### Checkout

content/en/docs/deployment/mx-azure/_index.md

@@ -0,0 +1,93 @@
+---
+title: "Mendix on Azure"
+url: /developerportal/deploy/mendix-on-azure/
+description: "Presents documentation on deploying your Mendix app on Microsoft Azure."
+weight: 42
+no_list: false 
+description_list: true
+---
+
+{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Success Manager. {{% /alert %}}
+
+## Introduction
+
+Mendix on Azure provides a simplified, integrated way to deploy Mendix applications to a Microsoft Azure environment. With this solution, users are empowered to deploy their Mendix applications in Azure environments without the need for intricate infrastructure setup in cloud services. They can also seamlessly manage infrastructure services through an intuitive user interface. No matter their IT skills, users can realize their project value quickly and securely with Azure.
+
+## Benefits of Mendix on Azure
+
+By eliminating manual setup and maintenance, Mendix on Azure allows your teams to:
+
+* Focus on developing business value instead of configuring infrastructure.
+* Avoid delays caused by cross-team dependencies or architectural discussions.
+* Accelerate time-to-market for critical applications.
+* Address deployment and operational bottlenecks by automating the setup and management of Mendix applications on Azure. 
+* Eliminate the need for specialized cloud engineers and reduce setup time to under 30 minutes. 
+* Focus on innovation and deliver value faster, reduces labor costs, and ensure consistency, security, and compliance.
+
+## Mendix on Azure and Mendix for Private Cloud
+
+Mendix on Azure is a new deployment option that makes use of some of the features of Mendix for Private Cloud, but does so in an opinionated way. 
+
+Mendix for Private Cloud offers its users flexibility coupled with the ability to keep their deployment within their enterprise firewall, but requires more effort to configure and more time to value than deployments on Mendix Cloud. 
+
+Mendix on Azure builds on that by providing an automated, preconfigured solution with access to private customer networks, which can be deployed in 30 minutes by a user without IT skills at no extra operational costs. The architecture, its maintenance, updates, and security hardening are all fully managed by Mendix. This helps prevent issues with setting up the infrastructure, which can sometimes be very technical and complicated for citizen developers.
+
+## Architecture
+
+Mendix on Azure provides a managed service to host Mendix apps in an Azure subscription you own. The Mendix on Azure service is composed of several underlying Azure services combined with the following Mendix-specific components:
+
+* [Mendix Runtime](/refguide/runtime/)
+* [Mendix Operator](/developerportal/deploy/private-cloud-cluster/)
+* [Mendix Agent](/developerportal/deploy/private-cloud-cluster/)
+
+Mendix operates all services and components within the scope of the Mendix on Azure service for you. The service leverages several underlying Azure services that are preconfigured to optimally host your Mendix apps.
+
+### Components
+
+Mendix deploys, operates and is responsible for overall service functionality of the following components as part of Mendix on Azure:
+
+* Azure Kubernetes Service with Managed NGINX Ingress Controller (app routing add-on)
+* Azure PostgreSQL Flexible Server
+* Azure Container Registry
+* Azure Blob Storage
+* Azure Managed Grafana
+* Azure Managed Prometheus
+* Azure Virtual Network with private endpoints and private DNS zones
+* Mendix Runtime
+* Mendix Operator
+* Mendix Agent
+
+You cannot alter these managed components yourself beyond what is offered in the Mendix on Azure and Mendix Private Cloud self-service portals. Mendix limits customization to ensure a consistent, predictable, and scalable customer experience.
+
+### Diagram
+
+The diagram in this section presents the high-level architecture of the Mendix for Azure solution.
+
+{{< figure src="/attachments/deployment/mx-azure/architecture.png" class="no-border" >}}
+
+The architecture is assessed against the [Azure well-architected framework](https://learn.microsoft.com/en-us/azure/well-architected/) to ensure its reliability, accessibility, and performance.
+
+## Security
+
+Mendix accesses customer environments in a secure, auditable way:
+
+* We use [cross-tenant access](https://learn.microsoft.com/en-us/entra/external-id/cross-tenant-access-overview), which is native to Azure and complies with Microsoft best practices.
+* Most access is performed programmatically, that is, by the system rather than manually by normal users. There is usually no human intervention into the customer environments.
+* In rare cases where human intervention is required, for example, because of a support request that requires access to the customer environment to resolve, the access is automated, auditable, and governed by Mendix support processes. The Mendix employee working on the support request receives temporary access which is then revoked.
+* The network connectivity is done using a private Azure link service, not through the public internet.
+
+### SOC 2 Type 2 Compliance Exceptions
+
+The Azure Policy add-on is not enabled inside Mendix Azure clusters, because Mendix can control which workloads can access the cluster. Because of that, the following exceptions to the SOC 2 Type 2 policy are considered acceptable:
+
+* Azure Container Registry:
+    * [Container registries should be encrypted with a customer-managed key](https://www.azadvertizer.net/azpolicyadvertizer/5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580.html) - The standard Microsoft key is used instead.
+* AKS - cluster resource:
+    * [Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters](https://www.azadvertizer.net/azpolicyadvertizer/0a15ec92-a229-4763-bb14-0ea34a568f8d.html) - The cluster is deployed and managed by Mendix, so the policy is not needed.
+    * [Azure Kubernetes Service clusters should have Defender profile enabled](https://www.azadvertizer.net/azpolicyadvertizer/a1840de2-8088-4ea8-b153-b4c723e9cb01.html) - This is not automated for cost-saving reasons.
+* AKS - cluster VNET:
+    * [All Internet traffic should be routed via your deployed Azure Firewall](https://www.azadvertizer.net/azpolicyadvertizer/fc5e4038-4584-4632-8c85-c0448d374b2c.html) - This is not automated, but the customer can deploy their own Firewall if required.
+* Storage Account:
+    * [Storage accounts should use customer-managed key for encryption](https://www.azadvertizer.net/azpolicyadvertizer/6fac406b-40ca-413b-bf8e-0bf964659c25.html) - The cluster is deployed and managed by Mendix, so this is not needed.
+
+## Read More

content/en/docs/deployment/mx-azure/mx-azure-getting-started.md

@@ -0,0 +1,60 @@
+---
+title: "Getting Started with Mendix on Azure"
+url: /developerportal/deploy/mendix-on-azure/quickstart/
+description: "Documents the pre-implementation tasks for Mendix on Azure."
+weight: 10
+---
+
+{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Success Manager. {{% /alert %}}
+
+## Introduction
+
+Before you can deploy your Mendix app on Azure, you must plan and complete a number of pre-implementation tasks.
+
+## Prerequisites
+
+To adopt Mendix on Azure, you need to have the following:
+
+* A Mendix account; Mendix Studio Pro 10.10 or newer is required
+* As an optional best practice, add multiple cluster manager to your clusters
+* An Azure account with the following permissions:
+    * Permission to grant admin consent on the Mendix on Azure portal app registration
+    * Owner or Contributor role assigned on the target subscription level
+
+{{% alert color="info" %}} To comply with the principle of least privilege, you can also create a custom role for the Mendix Operator instead of assigning the Owner or Contributor role. For the required permissions, see below:
+
+```text
+{
+    "properties": {
+        "roleName": "Mendix on Azure Operator",
+        "description": "",
+        "assignableScopes": [
+            "/subscriptions/<yoursubscriptionid>"
+    ],
+    "permissions": [
+        {
+            "actions": [
+            "*/register/action",
+            "Microsoft.Solutions/applications/*",
+            "Microsoft.Solutions/locations/operationstatuses/*",
+            "Microsoft.Resources/subscriptions/resourceGroups/*",
+            "Microsoft.Resources/deployments/*",
+            "Microsoft.Monitor/accounts/*",
+            "Microsoft.Authorization/roleAssignments/write",
+            "Microsoft.Authorization/roleAssignments/read"
+        ],
+        "notActions": [],
+        "dataActions": [],
+        "notDataActions": []
+        }
+    ]
+     }
+}
+```
+{{% /alert %}}
+
+## Licensing
+
+Mendix on Azure is available for purchase from the the [Azure Marketplace](https://azuremarketplace.microsoft.com/). Connecting to Azure services may also include additional cost. For more information, refer to Azure documentation.
+
+For production environments, you also need a runtime license for your Mendix app. For more information, refer to [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/). The Operator license is applied automatically when using Mendix on Azure.