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

Author: Yiyun333

content/en/docs/appstore/use-content/platform-supported-content/modules/aws/aws-create-new.md

@@ -136,7 +136,7 @@ After you create a microflow that connects to an AWS service, expose it as a mic
 4. In the **Category** field, enter the name of the AWS service.
 5. In the **Icon** section, select the official AWS icon.
 
-For more information, see [Microflow Properties: Expose as Microflow Action](/refguide/microflow/#expose-as-microflow).
+For more information, see [Microflow Properties: Expose as Microflow Action](/refguide/microflow/#expose-as-microflow-action).
 
 ## Best Practices
 

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

@@ -285,7 +285,7 @@ By default, autocommit is set to false for design time queries.
 
 When using JDK versions 17 or 21 (or any version above 16), you may encounter compatibility issues if database you are connecting to has a dependency on Apache Arrow.
 
-#### To resolve Apache Arrow dependency issue in Snowflake:
+#### Resolving Apache Arrow Dependency Issues in Snowflake
 
 The Snowflake JDBC Driver uses Arrow as the default result format for query execution to improve performance. However, you can override this default setting by switching the result format to JSON.
 
@@ -296,9 +296,9 @@ To set the result format at the Snowflake session or user level, use the followi
 ```
 
 This approach ensures compatibility with JDK 16+.
-[For more details](https://community.snowflake.com/s/article/Getting-java-lang-NoClassDefFoundError-for-class-RootAllocator).
+For more information, see [Getting Java Lang NoClassDefFoundError](https://community.snowflake.com/s/article/Getting-java-lang-NoClassDefFoundError-for-class-RootAllocator) in Snowflake documentation.
 
-#### To resolve Apache Arrow dependency issue in Databricks:
+#### Resolve Apache Arrow Dependency Issues in Databricks {#apache-arrow-databricks}
 
 The Databricks JDBC Driver uses Arrow for serialization as it improves performance.
 
@@ -307,4 +307,7 @@ To override this setting add below parameter to JDBC URL
 ```sql
 EnableArrow=0
 ```
-[For more details](https://community.databricks.com/t5/data-engineering/java-21-support-with-databricks-jdbc-driver/td-p/49297)
+For more information, see:
+
+* [Java 21 Support with Databricks](https://community.databricks.com/t5/data-engineering/java-21-support-with-databricks-jdbc-driver/td-p/49297) in Databricks documentation
+* [Configure the External Database Connector for Databricks](/appstore/modules/databricks/external-database-connector/)

content/en/docs/appstore/use-content/platform-supported-content/modules/databricks-edc.md

@@ -121,3 +121,7 @@ After you have created a table with some entries, you can now be query from your
     {{< figure src="/attachments/appstore/platform-supported-content/modules/databricks/JA_Query.png" >}}
 
 7. Link the microflow to a microflow button and use the Debugger to test if the objects are properly returned.
+
+## Read More
+
+* [External Database Connector: Resolving Apache Arrow dependency issue in Databricks](/appstore/modules/external-database-connector/#apache-arrow-databricks)

content/en/docs/appstore/use-content/platform-supported-content/modules/unit-testing.md

@@ -165,7 +165,7 @@ Evaluate results of the [Maia Best Practice Recommender](/refguide/best-practice
 * Import the [Unit Testing](https://marketplace.mendix.com/link/component/390) module into your Mendix application from the Marketplace.
 * The environment in which Unit Testing needs to happen should be in a running state.
 
-Since a remote API password is required to trigger Unit Tests and it is not advisable to have sensitive credential information in the pipeline definition, use variables within pipelines. These variables can then be easily referenced in the pipeline design. For more information, see the [Running Unit Tests Through the Remote API](/appstore/modules/unit-testing/#running-unit-tests-through-the-remote-api) section of *Unit Testing*.
+Since a remote API password is required to trigger Unit Tests and it is not advisable to have sensitive credential information in the pipeline definition, use variables within pipelines. These variables can then be easily referenced in the pipeline design. For more information, see the [Running Unit Tests Through the Remote API](/appstore/modules/unit-testing/#using-the-remote-api) section of *Unit Testing*.
 
 Using **Timeout (in seconds)** field, users can restrict the execution time of unit tests. If the tests exceed the predefined duration or timeout, the test step fails. It helps to avoid unnecessary waiting if tests are stuck in a loop.
 

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

@@ -75,18 +75,43 @@ Update-MxApp $appName -LiteralPath $literalPath
 Start-MxApp $appName -SynchronizeDatabase
 ```
 
-{{% alert color="info" %}}
+{{% alert color="warning" %}}
+Stopping your app before you update it is a necessary part of the process. Do not attempt to extract the deployment package into your app while the app is running.
+{{% /alert %}}
+
+You can find the parameters for `Start-MxApp` cmdlet in the sections below:
+
+#### `NoService`
+
 To start your app as a local process instead of a service, add a `-NoService` argument to the `Start-MxApp` cmdlet, as in the following example:
 
 ```
 Start-MxApp $appName -NoService -SynchronizeDatabase 
 ```
 
-{{% /alert %}}
+#### `EnableDebugger`
 
-{{% alert color="warning" %}}
-Stopping your app before you update it is a necessary part of the process. Do not attempt to extract the deployment package into your app while the app is running.
-{{% /alert %}}
+`EnableDebugger` allows Studio Pro to connect to a Mendix app for debugging.
+
+```
+Start-MxApp $appName -EnableDebugger "Abcd@1234"
+```
+
+#### `LicenseKey`
+
+The `LicenseKey` parameter to the `Start-MxApp` cmdlet allows you to activate a license for a Mendix app.
+
+```
+Start-MxApp $appName -LicenseKey "Abcd@1234"
+```
+
+#### `AdminPassword`
+
+the `AdminPassword` parameter to the Start-MxApp cmdlet sets the administrator password for a Mendix app.
+
+```
+Start-MxApp $appName -AdminPassword "Abcd@1234"
+```
 
 ### Sample Script - Determine the Mendix Runtime Version
 
@@ -144,6 +169,17 @@ $level = 'Log level which needs to be assigned'
 Set-MxLogLevel $appName -SubscriberName $subscriberName -Level $level
 ```
 
+### Sample Script - Create a Windows Service for Mendix app
+
+The following script example demonstrates how to create a Windows service for a Mendix app.
+
+```text
+$appName = 'Name of Mendix app'
+
+# Create new Windows service
+Install-MxService $appName
+```
+
 ## Troubleshooting
 
 If you encounter any issues while automating Mendix deployment on Windows using cmdlets, use the following troubleshooting tips to help you solve them.

content/en/docs/deployment/on-premises-design/ms-windows/automate-mendix-deployment-on-microsoft-windows.md

@@ -12,7 +12,7 @@ aliases:
 
 An annotation is an element that can be used to put comments to a flow.
 
-In the example below, you use a **Show message** activity to warn end-users about unpaid orders with a pop-up message in the client. Later you want to extend this warning with an email message send to the user. You can use an annotation as a reminder and put it above the current activity.
+In the example below, you use a **Show message** activity to warn end-users about unpaid orders with a pop-up message in the client. Later you want to extend this warning with an email message sent to the user. You can use an annotation as a reminder and put it above the current activity.
 
 {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/annotation/anotation.png" class="no-border" >}}
 

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/annotation.md

@@ -8,13 +8,13 @@ description: "Presents an overview of all the elements that can be used in a mic
 
 ## Introduction
 
-Microflows allow you to express the logic of your application. A microflow can perform actions such as creating and updating objects, showing pages and making choices. It is a visual way of expressing what traditionally ends up in textual program code.
+Microflows allow you to express the logic of your application. A microflow can perform actions such as creating and updating objects, showing pages, and making choices. It is a visual way of expressing what traditionally ends up in textual program code.
 
 Microflows run in the runtime server and can therefore not be used in offline apps. For application logic within offline apps, see [Nanoflows](/refguide/nanoflows/). For information on how nanoflows and microflows differ, see the [Differences between Microflows and Nanoflows](/refguide/microflows-and-nanoflows/#differences) section in *Microflows and Nanoflows*.
 
 This page is a summary of the elements which make up a microflow, together with their visual representation within the microflow. It also covers [keyboard support](#keyboard) when editing microflows.
 
-For the properties of the microflow itself, see [Microflow Properties](/refguide/microflow/). For more best practice details, see [Microflow Naming Conventions](/refguide/dev-best-practices/#microflow-naming-conventions), [Microflow General Best Practices](/refguide/dev-best-practices/#microflow-dev-best-practices), and [Microflow Best Practices from the Community](/refguide/community-best-practices-for-app-performance/#microflow-community-best-practices).
+For the properties of the microflow itself, see [Microflow Properties](/refguide/microflow/). For microflow best practices, see [Microflow Naming Conventions](/refguide/dev-best-practices/#microflow-naming-conventions), [Microflow General Best Practices](/refguide/dev-best-practices/#microflow-dev-best-practices), and [Microflow Best Practices from the Community](/refguide/community-best-practices-for-app-performance/#microflow-community-best-practices).
 
 For information on using microflows as data sources, see [Microflow Source](/refguide/microflow-source/).
 
@@ -32,38 +32,38 @@ A microflow is composed of elements. Below is a categorized overview of all elem
 * [Parameter](#parameter) is data that serves as input for the microflow.
 * [Annotation](#annotation) is an element that can be used to put comments in a microflow.
 
-### Events{#events}
+### Events {#events}
 
 Events represent start and endpoints of a microflow and special operations in a loop.
 
 | Graphic | Name | Description |
 | --- | --- | --- |
-| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/start-event.png" link="/refguide/start-event/" class="no-border" >}} | [Start Event](/refguide/start-event/) | A start event is the starting point of the microflow. A microflow can only have one start event. |
-| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/end-event.png" link="/refguide/end-event/" class="no-border" >}} | [End Event](/refguide/end-event/) | An end event defines the location where the microflow will stop. Depending on the return type of the microflow in some cases a value must be specified. There can be more than one end event. |
-| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/error-event.png" link="/refguide/error-event/" class="no-border" >}} | [Error Event](/refguide/error-event/) | An error event defines a location where the microflow will stop and throw an error that occurred earlier. If you call a microflow, you may want to know whether any errors occurred within the microflow or not. |
+| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/start-event.png" link="/refguide/start-event/" class="no-border" >}} | [Start Event](/refguide/start-event/) | A start event is the starting point of a microflow. A microflow can only have one start event. |
+| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/end-event.png" link="/refguide/end-event/" class="no-border" >}} | [End Event](/refguide/end-event/) | An end event defines the location where a microflow stops.Depending on the return type of the microflow, in some cases a value must be specified. There can be more than one end event. |
+| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/error-event.png" link="/refguide/error-event/" class="no-border" >}} | [Error Event](/refguide/error-event/) | An error event defines a location where a microflow stops and throws an error that occurred earlier. If you call a microflow, you may want to know whether any errors occurred within the microflow or not. |
 | {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/continue-event.png" link="/refguide/continue-event/" class="no-border" >}} | [Continue Event](/refguide/continue-event/) | A continue event is used to stop the current iteration of a loop and continue with the next iteration. Continue events can only be used inside a [Loop](/refguide/loop/). |
-| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/break-event.png" link="/refguide/break-event/" class="no-border" >}} | [Break Event](/refguide/break-event/) | A break event is used to stop iterating over the list of objects and continue with the rest of the flow after the loop. Break events can only be used inside a [Loop](/refguide/loop/). |
+| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/break-event.png" link="/refguide/break-event/" class="no-border" >}} | [Break Event](/refguide/break-event/) | A break event is used to stop iterating over a list of objects and continue with the rest of the flow after the loop. Break events can only be used inside a [Loop](/refguide/loop/). |
 
-### Flows{#flows}
+### Flows {#flows}
 
 Flows form the connection between elements.
 
 | Graphic | Name | Description |
 | --- | --- | --- |
 | {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/sequence-flow.png" link="/refguide/sequence-flow/" class="no-border" >}} | [Sequence Flow](/refguide/sequence-flow/) | A sequence flow is an arrow that links events, activities, decisions, and merges with each other. Together they define the order of execution within a microflow. |
-| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/annotation-flow.png" link="/refguide/annotation/#annotation-flow" class="no-border" >}} | [Annotation flow](/refguide/annotation/#annotation-flow) | An association is a connection that can be used to connect an annotation to another element. |
+| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/annotation-flow.png" link="/refguide/annotation/#annotation-flow" class="no-border" >}} | [Annotation flow](/refguide/annotation/#annotation-flow) | An annotation flow is a dashed line that is used to connect an [annotation](#annotation) to another element. |
 
 ### Decisions {#decisions}
 
 Decisions deal with making choices and merging different paths again.
 
-| Graphic                                                      | Name                                         | Description                                                  |
-| ------------------------------------------------------------ | -------------------------------------------- | ------------------------------------------------------------ |
-| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/decision.png" link="/refguide/decision/" class="no-border" >}} | [Decision](/refguide/decision/)                         | A decision makes a decision based on a condition and follows one and only one of the outgoing flows. There is no parallel execution in microflows. |
-| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/object-type-decision.png" link="/refguide/object-type-decision/" class="no-border" >}} | [Object Type Decision](/refguide/object-type-decision/) | An object type decision is an element that makes a choice based on the [specialization](/refguide/entities/) of the selected object. You can give the specialized object a name using a [cast object](/refguide/cast-object/) action. |
-| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/merge.png" link="/refguide/merge/" class="no-border" >}} | [Merge](/refguide/merge/)                               | A merge can be used to combine multiple sequence flows into one. If a choice is made in a microflow and afterwards some common work needs to be done, you can combine the two (or more) paths using a merge. |
+| Graphic | Name | Description |
+| --- | --- | --- |
+| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/decision.png" link="/refguide/decision/" class="no-border" >}} | [Decision](/refguide/decision/) | A decision makes a decision based on a condition and follows one and only one of the outgoing flows. There is no parallel execution in microflows. |
+| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/object-type-decision.png" link="/refguide/object-type-decision/" class="no-border" >}} | [Object Type Decision](/refguide/object-type-decision/) | An object type decision is an element that makes a choice based on the [specialization](/refguide/entities/) of the selected object. You can give the specialized object a name using a [cast object](/refguide/cast-object/) activity. |
+| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/merge.png" link="/refguide/merge/" class="no-border" >}} | [Merge](/refguide/merge/) | A merge is used to combine multiple sequence flows into one. If a choice is made in a microflow and afterwards some common work needs to be done, you can combine the two (or more) paths using a merge. |
 
-### Activities{#activities}
+### Activities {#activities}
 
 [Activities](/refguide/activities/) are the actions that are executed in a microflow:
 
@@ -75,11 +75,11 @@ A [loop](/refguide/loop/) is used to iterate over a list of objects:
 
 {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/loop.png" alt="Loop" class="no-border" >}}
 
-For every object the flow inside the loop is executed. A loop activity can contain all elements used in microflows, with the exception of start and end events. 
+For every object, the flow inside the loop is executed. A loop activity can contain all elements used in microflows, with the exception of start and end events. 
 
 ### Parameter {#parameter}
 
-A [parameter](/refguide/parameter/) is data that serves as input for the microflow. 
+A [parameter](/refguide/parameter/) is data that serves as input for a microflow. 
 
 {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/parameter.png" alt="Parameter" class="no-border" >}}