Merge branch 'development' into lz-company-apps-overview

Author: Luyao-Zhang-1

content/en/docs/appstore/creating-content/connector-guide-build/_index.md

@@ -35,7 +35,7 @@ Connectors can be used in your app to simplify connecting to existing third-part
 
 ### Connecting to Other Systems
 
-Connectors are implemented as Mendix modules with a focus on connecting to other systems. Connectors can make use of any of the platform-supported protocols like [SOAP](/refguide/consumed-web-services/#soap), [REST](/refguide/consumed-rest-services/#rest), [OData](/refguide/consumed-odata-services/#external-entities), or [Catalog](/catalog/). 
+Connectors are implemented as Mendix modules with a focus on connecting to other systems. Connectors can make use of any of the platform-supported protocols like [SOAP](/refguide/consumed-web-services/#soap), [REST](/refguide/integration/rest-services/), [OData](/refguide/consumed-odata-services/#external-entities), or [Catalog](/catalog/). 
 
 They can also be used to package a Java library provided by the other system to make the connection. These Java library functions can be exposed via Java actions as custom microflow activities (see [How to Build Microflow Actions with Java](/howto/extensibility/howto-connector-kit/)). This makes it simpler for Mendix developers without in-depth knowledge about third-party integrations to use these connectors in their business logic.
 
@@ -59,7 +59,7 @@ This chart shows the available solutions for when you want to connect Mendix app
 | Unsupported protocols   | Build a module to connect either via alternative protocols, or by encapsulating one of the platform supported protocols. |
 
 {{% alert color="info" %}}
-The [Catalog](/catalog/) is a hub for shared registered assets made available in your organization. At the moment, it only supports OData.
+The [Catalog](/catalog/) is a hub for shared registered assets made available in your organization. At the moment, it supports OData, REST, and Business Events.
 {{% /alert %}}
 
 ### Getting Mendix Connectors

content/en/docs/appstore/platform-supported-content/modules/any-chart.md

@@ -7,7 +7,7 @@ description: "Describes the configuration and usage of the Any Chart module, whi
 
 ## Introduction
 
-The [Any Chart](https://marketplace.mendix.com/link/component/106517/) module contains chart types supported in [plotly.js version 1.47.4](https://www.npmjs.com/package/plotly.js/v/1.47.4).
+The [Any Chart](https://marketplace.mendix.com/link/component/106517/) module contains chart types supported in [plotly.js version 2.35.2](https://www.npmjs.com/package/plotly.js/v/2.35.2).
 
 Further documentation on usage can be found in the following pages locations:
 

content/en/docs/appstore/platform-supported-content/modules/excel-exporter.md

@@ -13,9 +13,9 @@ The Excel Exporter is compatible with the [Excel Importer](/appstore/modules/exc
 
 ## Prerequisites
 
-* [Install Mx Model Reflection](/howto/integration/using-the-excel-exporter/#download-modules) version 6.1.1 or higher
-* [Add MxReflection page and Excel Exporter page to the navigation](/howto/integration/using-the-excel-exporter/#add-navigation-items)
-* [Configure Mx Model Reflection](/howto/integration/using-the-excel-exporter/#configure-mx-model-reflection)
+* [Install Mx Model Reflection](/refguide/using-the-excel-exporter/#download-modules) version 6.1.1 or higher
+* [Add MxReflection page and Excel Exporter page to the navigation](/refguide/using-the-excel-exporter/#add-navigation-items)
+* [Configure Mx Model Reflection](/refguide/using-the-excel-exporter/#configure-mx-model-reflection)
 
 ## Configuration
 

content/en/docs/appstore/platform-supported-content/modules/genai/_index.md

@@ -84,5 +84,5 @@ The available showcase applications offer implementation inspiration for many of
 In addition to the models listed above, you can also connect to other models by implementing one of the following options:
 
 * To connect to other [foundation models](https://docs.aws.amazon.com/bedrock/latest/userguide/models-features.html) and implement them in your app, use the [Amazon Bedrock connector](/appstore/modules/aws/amazon-bedrock/).
-* To connect to [Snowflake Cortex LLM](https://docs.snowflake.com/en/sql-reference/functions/complete-snowflake-cortex) functions, use the [Snowflake connectors](/appstore/snowflake-modules/).
+* To connect to [Snowflake Cortex LLM](https://docs.snowflake.com/en/sql-reference/functions/complete-snowflake-cortex) functions, [configure the Snowflake REST SQL connector for Snowflake Cortex Analyst](/appstore/connectors/snowflake/snowflake-rest-sql/#cortex-analyst).
 * To implement your own connector compatible with the other components, use the [GenAI Commons](/appstore/modules/genai/commons/) interface.

content/en/docs/appstore/platform-supported-content/modules/snowflake/snowflake-rest-sql.md

@@ -1,7 +1,7 @@
 ---
 title: "Snowflake REST SQL Connector"
 url: /appstore/connectors/snowflake/snowflake-rest-sql/
-description: "Describes the configuration and usage of the Mendix-Snowflake REST SQL connector from the Mendix Marketplace."
+description: "Describes the configuration and usage of the Mendix-Snowflake REST SQL connector from the Mendix Marketplace." 
 weight: 20
 #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details. 
 ---
@@ -18,12 +18,15 @@ The Snowflake REST SQL connector provides a way to first setup key-pair authenti
 * Write data to Snowflake
 * Trigger [Snowflake Cortex ML functions](https://docs.snowflake.com/en/guides-overview-ml-functions)
 * Use [Snowflake Cortex LLM functions](https://docs.snowflake.com/en/user-guide/snowflake-cortex/llm-functions)
+* Use [Snowflake Cortex Analyst](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst)
 
-The current version of the connector supports the following actions:
+The current version of the connector supports the following:
 
 * Authentication with an RSA key pair according to PKCS #8 standard
+* Authentication with OAUTH through an OIDC provider
 * Execution of single SQL statements
 * Synchronous execution of calls
+* Execution of a Cortex Analyst query
 
 ### Prerequisites {#prerequisites}
 
@@ -33,6 +36,7 @@ To use the Snowflake REST SQL connector, you must also install and configure the
 
 * [Community Commons](https://marketplace.mendix.com/link/component/170) - This module is a required dependency for the Snowflake REST SQL connector.
 * [Encryption](https://marketplace.mendix.com/link/component/1011) - This module is a required dependency for the Snowflake REST SQL connector. The EncryptionKey constant must be set up in your application settings.
+* [GenAI Commons](https://marketplace.mendix.com/link/component/227933)- This module is a required dependency for the Snowflake Cortex Analyst.
 
 ### Licensing and Cost
 
@@ -96,6 +100,7 @@ After you configure the authentication for Snowflake, you can implement the func
 
 {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-rest-sql/example_implementation.png" >}}
 
+
 ## Technical Reference
 
 To help you work with the Snowflake REST SQL connector, the following sections of this document list the available entities, enumerations, and activities that you can use in your application.
@@ -205,3 +210,45 @@ FROM your_table
 ```
 
 This statement returns data from a Snowflake table with the columns named as specified with the `as **NewColumnName**" part` of each line. If the attribute names, datatypes and their order match, the `TransformResponsesToMxObjects` activity automatically converts the retrieved data into Mendix objects.
+
+## Configuring Snowflake Cortex Analyst {#cortex-analyst}
+
+Cortex Analyst is a fully-managed, LLM-powered Snowflake Cortex feature that helps you create applications capable of reliably answering business questions based on your structured data in Snowflake.
+
+{{% alert color="info" %}}
+Snowflake Cortex Analyst is currently in open preview. For more information, refer to the [Snowflake Cortex Analyst documentation](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst).
+{{% /alert %}}
+
+### Prerequisites
+
+* Make sure that you have access to Cortex Analyst. For more information, refer to the [Snowflake Cortex Analyst documentation](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst).
+* Create the semantic model for Cortex Analyst. For more information, refer to [Creating Semantic Models for Snowflake Cortex Analyst](https://developers.snowflake.com/solution/creating-semantic-models-for-snowflakes-cortex-analyst/) in the Snowflake Cortex Analyst documentation.
+* Set up one of the following supported authentication methods for Cortex Analyst:
+    * OAUTH
+    * WT-Keypair
+
+### Configuration 
+
+To configure your Mendix app for Snowflake Cortex Analyst, perform the following steps:
+
+1. Create a microflow and add the **Cortex Analyst: Create Cortex Analyst Connection** action from the **Toolbox**.
+2. Provide the following mandatory information:
+    * **Token** - The authentication token created from the OIDC provider, or the JWT Token
+    * **AccountURL** - The URL of the Snowflake account that has access to Snowflake Cortex Analyst
+    * **Authentication Type**
+3. Add the **Cortex Analyst: Create Request** action from the **Toolbox**, and then configure the **Request** to contain the path to the Snowflake semantic model file.
+3. Add the **Chat: Add Message to Request** action from the Toolbox and provide the following information:
+    * **Request** - The request that you configured for the **Cortex Analyst: Create Request** action
+    * **ENUM_MessageRole** - The role of the entity that creates the message; in the current version, the role must be set to **user**
+    * **ContentString** - The text of the question for Cortex Analyst
+4. Add the **Snowflake Cortex Analyst** action from the Toolbox and provide the following information:
+    * **Connection** - The Cortex Analyst connection that you configured for the **Cortex Analyst: Create Cortex Analyst Connection** action
+    * **Request** - The request that you configured for the **Cortex Analyst: Create Request** action
+5. To get the response message from the response, add the **Response: Get Cortex Analyst Response Message** action from the Toolbox, and then add the **Response** entity as a parameter. The message contains the following information:
+    * **Content** - This is the content of the response message. It includes the text and the SQL, or the suggestions if no SQL is returned
+    * **Cortex Role** - The entity that produced the message; possible values are *user* or *analyst*
+    * **SQLText** - The returned SQL suggestion
+6. To get the Cortex Analyst Response entity, add the **Response: Get Cortex Analyst Response** action from the Toolbox, and then add the **Response** entity as a parameter. The response contains the following information:
+    * **Request_ID** - The returned *RequestId*
+   
+ {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-rest-sql/CortexAnalystRequestExample.png" >}}    

content/en/docs/catalog/_index.md

@@ -24,7 +24,7 @@ The [Catalog](https://catalog.mendix.com) is a development tool provided in Mend
 
 {{< figure src="/attachments/catalog/catalog-home.png" class="no-border" >}}
 
-REST services provided by Mendix Apps running in Mendix Cloud (published [OData](/refguide/published-odata-services/) and OpenAPI REST Services) are automatically registered in your organization's Catalog upon deployment. This provides you with an up-to-date view of all the OData and OpenAPI REST APIs published and consumed by your Mendix apps. These assets can be [curated](/catalog/manage/curate/) in the Catalog to ensure that they are exposed to the relevant users and can be found easily. 
+REST services provided by Mendix Apps running in Mendix Cloud (published [OData](/refguide/published-odata-services/) and OpenAPI REST Services) and Business Events are automatically registered in your organization's Catalog upon deployment. This provides you with an up-to-date view of all the OData, OpenAPI, and Business Event endpoints published and consumed by your Mendix apps. These assets can be [curated](/catalog/manage/curate/) in the Catalog to ensure that they are exposed to the relevant users and can be found easily. 
 
 Learn about updates and improvements in the [Catalog](/releasenotes/data-hub/) release notes.
 

content/en/docs/catalog/get-started.md

@@ -31,7 +31,7 @@ You can use the Catalog with any deployment method, though there are differences
 
 | Deployment Method | How are Data Sources Registered? | 
 | --- | --- |
-| [Mendix Cloud](/developerportal/deploy/mendix-cloud-deploy/) | Published OData services in a deployed app are [registered automatically](/catalog/register/register-data/#mendix-cloud) as data sources in the Catalog <br> [Register sources using the Registration API](/catalog/register/register-data/#register-services) |
+| [Mendix Cloud](/developerportal/deploy/mendix-cloud-deploy/) | Published OData/REST services and Business Events services in a deployed app are [registered automatically](/catalog/register/register-data/#mendix-cloud) as data sources in the Catalog <br> [Register sources using the Registration API](/catalog/register/register-data/#register-services) |
 | [Private Cloud](/developerportal/deploy/private-cloud/) | Using the [Registration API](/catalog/register/register-data/#register-services) |
 | [On-Premises](/developerportal/deploy/on-premises-design/) | Using the [Registration API](/catalog/register/register-data/#register-services) |
 

content/en/docs/catalog/register/register-data.md

@@ -16,11 +16,11 @@ aliases:
 
 ## Introduction
 
-There are three ways to register published services in the Catalog. Mendix supports all OData versions.
+There are three ways to register published services in the Catalog. Mendix supports all OData versions, REST, and Business Events
 
 This how-to teaches you how to register a service in the following ways:
 
-* [Through Mendix Cloud](#mendix-cloud), where registration occurs automatically when you deploy a [published OData service](/refguide/published-odata-services/) to Mendix Cloud
+* [Through Mendix Cloud](#mendix-cloud), where registration occurs automatically when you deploy a [published OData](/refguide/published-odata-services/)/REST service, or Business Event to Mendix Cloud
 * [Through the Catalog Registration API](#registration-api)
 * [Through the Catalog UI form](#registration-form)
 
@@ -30,7 +30,7 @@ Before starting this how-to, make sure you have completed the following prerequi
 
 * You have Studio Pro [8.14.0 or above](https://marketplace.mendix.com/link/studiopro/) installed
 * You have a Mendix account
-* You have an exposed OData service that you are ready to register (for instructions on how to create an exposed OData service, refer to the sections on creating an app and exposing an entity in [Share Data Between Apps](/howto/integration/share-data/)
+* You have an exposed OData/REST service or Business Event that you are ready to register (for instructions on how to create an exposed OData service, refer to the sections on creating an app and exposing an entity in [Share Data Between Apps](/howto/integration/share-data/)
 
 ## Registering a Service Through Mendix Cloud {#mendix-cloud}