Merge branch 'development' into qt-movehowtodocs

Author: quinntracy

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/genai/reference-guide/external-platforms/_index.md

@@ -11,4 +11,4 @@ no_list: false
 
 The Mendix platform provides seamless integration with various external platforms through specialized connectors. These connectors enable you to extend the functionality of your applications by leveraging external services and data sources. This section introduces the connectors available for [Snowflake Cortex](/appstore/modules/genai/snowflake-cortex/), [OpenAI](/appstore/modules/genai/openai/), [Amazon Bedrock](/appstore/modules/genai/bedrock/), and [PGVector Knowledge Base](/appstore/modules/genai/pgvector/), providing a high-level overview of their capabilities.
 
-## Connectors
+## Connectors

content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/external-platforms/snowflake-cortex.md

@@ -56,7 +56,6 @@ The [Snowflake showcase app](https://marketplace.mendix.com/link/component/22584
     3. Cortex LLM Functions
     4. Cortex Analyst
 
-
 3. To see how a Snowflake Cortex Analyst action is called, use the **Explorer** search box to find and open the *EXAMPLE_CortexAnalyst_GenerateResponseMessage** microflow.
 
    {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-rest-sql/CortexAnalystRequestExample.png" >}}

…ence-guide/genai-for-mendix.md/_index.md …ference-guide/genai-for-mendix/_index.mdcontent/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix.md/_index.md renamed to content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix/_index.md content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix.md/_index.md renamed to content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix/_index.md

@@ -871,4 +871,4 @@ To check your JDK version and update it if necessary, follow these steps:
     1. You might get an error saying `FAILURE: Build failed with an exception. The supplied javaHome seems to be invalid. I cannot find the java executable.` In this case, verify that you have selected the correct JDK directory containing the updated JDK version.
     2. You may also need to update Gradle. To do this, go to **Edit** > **Preferences** > **Deployment** > **Gradle directory**. Click **Browse** and select the appropriate Gradle version from the Mendix folder. For Mendix 10.10 and above, use Gradle 8.5. For Mendix 10 versions below 10.10, use Gradle 7.6.3. Then save your settings by clicking **OK**.
     3. Rerun the project.
-    
+    

…genai-for-mendix.md/conversational-ui.md …de/genai-for-mendix/conversational-ui.mdcontent/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix.md/conversational-ui.md renamed to content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix/conversational-ui.md content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix.md/conversational-ui.md renamed to content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix/conversational-ui.md

@@ -137,7 +137,7 @@ If LDAP is enabled for this connection (**LDAP enabled** is checked), you must f
 * **LDAP type** – Set the type of action that should be done for this LDAP connection. Depending on this type, you will need to add further information as described in [LDAP Type Configurations](#ldap-type-configurations), below. The LDAP type can be one of the following:
 
     * **Import users** – Import and synchronize the end-users specified the configuration. This will make the end-user information available in your Mendix app.
-    * **Only authenticate users** – This will only authenticate existing Mendix end-users against the LDAP server, but it will not synchronize any information. If an end-user is not known in Mendix, they cannot sign in.
+    * **Only authenticate users** – This will only authenticate existing Mendix end-users against the LDAP server, but it will not synchronize any information. If an end-user is not known in Mendix, they cannot sign in. In the **General** tab, when the **LDAP Type** is set to **Only authenticate users based on the LDAP credentials**, the **Custom User Provisioning** toggle button appears. Enabling this option automatically triggers the `Ldap.customLoginLogic` microflow.
     * **Authenticate and create** – This will not synchronize end-users. However, if an end-user that is unknown in Mendix signs in using valid LDAP authentication, a Mendix end-user will be created, and the end-user info will be copied from the LDAP server at that moment.
 
 * **Map users to** – This specifies which entity type objects should be created when creating new end-users. You can choose from all the specializations of **System.User**. For example, you may want to use the `Administration.Account` entity if you are using the Administration module.

…ide/genai-for-mendix.md/genai-commons.md …-guide/genai-for-mendix/genai-commons.mdcontent/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix.md/genai-commons.md renamed to content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix/genai-commons.md content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix.md/genai-commons.md renamed to content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix/genai-commons.md

@@ -61,6 +61,9 @@ To use BAPI Connector for SAP Solutions in your Mendix application to call the B
 
 1. Set up the developer environment as described in [Setting Up the Developer Environment](#setup-environment).
 2. Test the connection to the SAP Backend [using the microflow `TestConnection`](#test-connection).
+
+    {{% alert color="info" %}}The `TestConnection` action works only when connection details are configured using [Direct Connections to the SAP Backend System](#sap-connection-details).{{% /alert %}}
+
 3. Add the microflow `Create_BAPIExplorer` to the navigation of your app to allow you to search for the BAPIs you need.
 
     {{% alert color="info" %}}Searching for BAPIs is provided as a microflow rather than a separate app so that you can set up the JCo destination securely. You should not give access to this microflow to any end-users of an app you build using the Mendix BAPI Connector.{{% /alert %}}