Merge branch 'development' into ctl-prop-pane-updates

Author: ConnorLand

content/en/docs/appstore/connectors/aws/aws-textract.md

@@ -87,7 +87,7 @@ If you have installed Chrome in a custom location, configure the path to the Chr
 
 ##### 3.1.2 Chromium
 
-If you use Chromium, only use stable releases. The currently supported stable release is [104.0.5109.0](https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/1011831). 
+If you use Chromium, only use stable releases. The currently supported stable release is [104.0.5109.0](https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/1011831/). 
 
 Download the *chrome-win.zip* package and extract the archive to a location of your choosing. 
 

content/en/docs/appstore/modules/document-generation.md

@@ -61,7 +61,7 @@ You can also consider running your Mendix app using your own AWS account, and ha
 There are certain limits and behaviors which apply to your app when running in the Mendix Cloud. Here are a few considerations to bear in mind:
 
 * The Amazon RDS maintenance window is not aligned with the Mendix Developer Portal maintenance window for an application
-* It is not possible to deploy a model (*.mda*) larger than 4 GB when uncompressed or a model that contains approximately 64,000 or more files
+* It is not possible to deploy a model (*.mda*) larger than 1 GB when uncompressed or a model that contains approximately 64,000 or more files
 * You can't upload files bigger than 1 GB to your app
 * You can't download files bigger than 1 GB from your app
 * To use the debugger, you need to scale down to one instance

content/en/docs/developerportal/deploy/mendix-cloud-deploy/mxcloudv4/_index.md

@@ -310,6 +310,32 @@ Use microflow [error handling](/howto7/logic-business-rules/set-up-error-handlin
 
 Complex processes and important business logic (like workflow processing or validations) must include debug and trace [logging](/refguide7/logging/). Logging actions must write the current state and progress of the process and must include a request ID or other identifying information. The log node should be the name of the module. This will greatly assist error analysis.
 
+#### 4.2.6 Validating Inputs in Microflows
+
+When microflows are invoked from the client side, it is important to validate the inputs. By having validations, you prevent incorrect, inappropriate, or potentially harmful data from being used in your microflows. This protects your application against security vulnerabilities. The following presents the best practices regarding the integrity and validation of inputs in your microflows.
+
+##### 4.2.6.1 Implementing Validation Checks
+
+Adding validation checks is vital for ensuring that input data conforms to the expected data type, format, range, or other application-specific constraints. For instance, if a numeric input is expected within a defined range, validation checks should confirm that the input is indeed numeric and falls within the specified range.
+
+##### 4.2.6.2 Managing Unexpected Values
+
+When building microflows, it is important to account for the potential occurrence of unexpected values. These could be empty values, or values outside the expected range or format. It is also important to ensure that read-only attributes only contain expected values.
+
+{{% alert color="warning" %}}
+We strongly recommend adding validation checks to all microflows inputs, including read-only attributes. 
+
+We also recommend avoiding storing intermediary values in attributes (such as, *TotalPrice*). Instead, calculate these values when needed to ensure you have the correct values.
+{{% /alert %}}
+
+Microflows should incorporate mechanisms to detect unexpected values and respond suitably – this might involve returning an error message to the end-user or executing a fallback operation. 
+
+##### 4.2.6.3 Updating Validation Logic Regularly
+
+As the application evolves, the validation logic within microflows should be updated accordingly to reflect changes in business logic or data models. This regular review and update of validation checks ensures that microflows remain secure and function correctly over time.
+
+By prioritizing the validation of inputs in microflows, you not only enhance the security of your application, but also ensure a more predictable and stable user experience. This practice underscores the development of reliable and robust applications.
+
 ### 4.3 Warnings and Modeler Feedback
 
 No warnings should be visible in the Modeler, unless explicitly documented with a reason. Warnings can indicate many issues, including maintainability and security risks, which must be resolved.

content/en/docs/howto7/general/dev-best-practices.md

@@ -1,9 +1,11 @@
 ---
 title: "Test Web Services Using SoapUI"
-url: /howto7/testing/testing-web-services-using-soapui/
+url: /howto7/integration/testing-web-services-using-soapui/
 category: "Testing"
 weight: 30
 tags: ["test", "testing", "web service", "soapui"]
+aliases: 
+    - /howto7/testing/testing-web-services-using-soapui/
 ---
 
 ## 1 Introduction

…ing/testing-web-services-using-soapui.md …ion/testing-web-services-using-soapui.mdcontent/en/docs/howto7/testing/testing-web-services-using-soapui.md renamed to content/en/docs/howto7/integration/testing-web-services-using-soapui.md content/en/docs/howto7/testing/testing-web-services-using-soapui.md renamed to content/en/docs/howto7/integration/testing-web-services-using-soapui.md

@@ -24,7 +24,7 @@ For a deep-dive look into styling with Calypso, check out this video:
 
 ## 2 Prerequisites
 
-* Download Calypso [here](https://www.dropbox.com/sh/r1vx2kig86v5wa6/AABQC8MJfNi8Ff9skinrIf7Ea?dl=0)
+* Download Calypso [here](https://github.com/mendix/Atlas-UI-Framework/releases/download/calypso-v1/Calypso.Setup.1.0.0.exe)
 
 ## 3 Setting Up Calypso
 

content/en/docs/howto8/front-end/customize-styling/calypso.md

@@ -329,6 +329,32 @@ Use microflow [error handling](/howto8/logic-business-rules/set-up-error-handlin
 
 Complex processes and important business logic (like workflow processing or validations) must include debug and trace [logging](/refguide8/logging/). Logging actions must write the current state and progress of the process and must include a request ID or other identifying information. The log node should be the name of the module. This will greatly assist error analysis.
 
+#### 4.2.6 Validating Inputs in Microflows
+
+When microflows are invoked from the client side, it is important to validate the inputs. By having validations, you prevent incorrect, inappropriate, or potentially harmful data from being used in your microflows. This protects your application against security vulnerabilities. The following presents the best practices regarding the integrity and validation of inputs in your microflows.
+
+##### 4.2.6.1 Implementing Validation Checks
+
+Adding validation checks is vital for ensuring that input data conforms to the expected data type, format, range, or other application-specific constraints. For instance, if a numeric input is expected within a defined range, validation checks should confirm that the input is indeed numeric and falls within the specified range.
+
+##### 4.2.6.2 Managing Unexpected Values
+
+When building microflows, it is important to account for the potential occurrence of unexpected values. These could be empty values, or values outside the expected range or format. It is also important to ensure that read-only attributes only contain expected values.
+
+{{% alert color="warning" %}}
+We strongly recommend adding validation checks to all microflows inputs, including read-only attributes. 
+
+We also recommend avoiding storing intermediary values in attributes (such as, *TotalPrice*). Instead, calculate these values when needed to ensure you have the correct values.
+{{% /alert %}}
+
+Microflows should incorporate mechanisms to detect unexpected values and respond suitably – this might involve returning an error message to the end-user or executing a fallback operation. 
+
+##### 4.2.6.3 Updating Validation Logic Regularly
+
+As the application evolves, the validation logic within microflows should be updated accordingly to reflect changes in business logic or data models. This regular review and update of validation checks ensures that microflows remain secure and function correctly over time.
+
+By prioritizing the validation of inputs in microflows, you not only enhance the security of your application, but also ensure a more predictable and stable user experience. This practice underscores the development of reliable and robust applications.
+
 ### 4.3 Warnings and Studio Pro Feedback
 
 No warnings should be visible in Studio Pro, unless explicitly documented with a reason. Warnings can indicate many issues, including maintainability and security risks, which must be resolved.

content/en/docs/howto8/general/dev-best-practices.md

@@ -1,9 +1,11 @@
 ---
 title: "Test Web Services Using SoapUI"
-url: /howto8/testing/testing-web-services-using-soapui/
+url: /howto8/integration/testing-web-services-using-soapui/
 category: "Testing"
 weight: 30
 tags: ["test", "testing", "web service", "soapui"]
+aliases: 
+    - /howto8/integration/testing-web-services-using-soapui/
 ---
 
 ## 1 Introduction
@@ -41,11 +43,11 @@ In the how-to [Exposing a web service](/howto8/integration/expose-a-web-service/
 2. Open the project you created in the how-to [Exposing a web service](/howto8/integration/expose-a-web-service/).
 3. Create a **Microflow** that creates a customer and returns a Boolean. 
 
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/model1.jpg" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/model1.jpg" >}}
 
 4. Create a **Microflow** that deletes a customer and returns a Boolean.
 
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/model2.jpg" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/model2.jpg" >}}
 
 5. Publish both microflows as web service operation of the **CustomerWebservice** as described in chapter 4 of the how-to [Exposing a web service](/howto8/integration/expose-a-web-service/).
 
@@ -55,39 +57,39 @@ In this chapter you will create a new SOAP project.
 
 1. Open **SoapUI**.
 2. Press **CTRL+N** to create a new SOAP project.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580339.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580339.png" >}}
 3. Run the project locally in Studio Pro.
 4. Go to `http://localhost:8080/ws-doc/`.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580314.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580314.png" >}}
 5. Enter the URL of the WSDL schema in the **Initial WSDL** field in SoapUI.
     The Project Name field will automatically be filled with the name of the webservice following by *?wsdl*.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580334.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580334.png" >}}
 6. Click**OK**. This will create a new SOAP project in SoapUI.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580313.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580313.png" >}}
 
 ## 5 Building a TestSuite, TestCase, and TestStep
 
 In this chapter you will build a testsuite. A testsuite contains one or more testcases. Every testcase contains one ore more teststeps. 
 
 1. In SoapUI, press **CTRL+T** to create a new TestSuite.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580332.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580332.png" >}}
 2. Click **OK**.
 3. Select TestSuite 1 and press **CTRL+N** to create a new TestCase.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580331.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580331.png" >}}
 4. Click **OK**.
 5. Expand TestSuite 1 and TestCase 1.
 6. Right-click **Test Steps(0)** and select **SOAP Request**.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580312.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580312.png" >}}
 7. Enter *Retrieve Customers* in the name field.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580329.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580329.png" >}}
 8. Click **OK**.
 9. Select **CustomerWebserviceSoap -> GetCustomers**.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580328.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580328.png" >}}
 10. Click **OK**.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580327.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580327.png" >}}
 11. Click **OK**.
 12. Open SOAP request **Retrieve Customers**.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580326.png" >}} 
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580326.png" >}} 
 13. Change the follow value:
 
     ```java
@@ -142,15 +144,15 @@ In this chapter you will build a testsuite. A testsuite contains one or more tes
 Assertions are used to validate the message received by a TestStep during execution, usually by comparing parts of the message (or the entire message) to some expected value. In this chapter you will create an assertion that validates the number of customers.
 
 1. Click **Assertions (1)**.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580307.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580307.png" >}}
     In chapter 3 step 9 the *Add SOAP Response Assertion* checkbox was checked. That is the first assertion you see in the list, *SOAP Response - VALID*.
 2. Click the add assertion icon.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580324.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580324.png" >}}
 3. Click **Property Content**.
 4. Click **XPath Match**.
 5. Enter *count(//Customer)* in the XPath Expression field.
 6. In step 1.4 of the previous how-to you have added some data. Enter the number of created customers in the **Expected Result** field. In this example four customers were created.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580323.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580323.png" >}}
 7. Click **Save**.
 
 ## 7 Extending Your Test Case
@@ -181,13 +183,13 @@ In this chapter you will extend your test case with multiple test steps and asse
     ```
 
 3. Add a **Contains Assertion** and enter *true* in the content field.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580322.png" >}} 
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580322.png" >}} 
 4. Right-click test step **Retrieve Customers**.
 
 5. Select **Clone TestStep**.
 
 6. Change **TestStep Name** to *Retrieve Customers 2*.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580320.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580320.png" >}}
 7. Click **OK**.
 8. Open teststep **Retrieve Customers 2**.
 9. Click **Assertions (2)**.
@@ -216,17 +218,17 @@ In this chapter you will extend your test case with multiple test steps and asse
 In this chapter you will learn how to run the testcase you created in previous chapters.
 
 1. Open testcase **TestCase 1**.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580310.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580310.png" >}}
 2. Click the run this testcase icon.
-    {{< figure src="/attachments/howto8/testing/testing-web-services-using-soapui/18580309.png" >}}
+    {{< figure src="/attachments/howto8/integration/testing-web-services-using-soapui/18580309.png" >}}
 
 Congratulations! You have just created your first automated test with SoapUI.
 
 ## 9 Read More
 
 * [Finding the Root Cause of Runtime Errors](/howto8/monitoring-troubleshooting/finding-the-root-cause-of-runtime-errors/)
 * [Clearing Warning Messages in Mendix](/howto8/monitoring-troubleshooting/clear-warning-messages/)
-* [Testing web services using SoapUI](/howto8/testing/testing-web-services-using-soapui/)
+* [Testing web services using SoapUI](/howto8/integration/testing-web-services-using-soapui/)
 * [Monitoring Mendix using JMX](/howto8/monitoring-troubleshooting/monitoring-mendix-using-jmx/)
 * [Debugging Java actions remotely](/howto8/monitoring-troubleshooting/debug-java-actions-remotely/)
 * [Log Levels](/howto8/monitoring-troubleshooting/log-levels/)

…ing/testing-web-services-using-soapui.md …ion/testing-web-services-using-soapui.mdcontent/en/docs/howto8/testing/testing-web-services-using-soapui.md renamed to content/en/docs/howto8/integration/testing-web-services-using-soapui.md content/en/docs/howto8/testing/testing-web-services-using-soapui.md renamed to content/en/docs/howto8/integration/testing-web-services-using-soapui.md

@@ -25,7 +25,7 @@ Before starting this how-to, make sure you have completed the following prerequi
 * For information on device requirements, see [System Requirements](/refguide8/system-requirements/)
 * If you wish to use an emulator for Android mobile testing, install a product such as [Bluestacks](https://www.bluestacks.com/nl/index.html) or [Genymotion](https://www.genymotion.com/) (your emulator must have Google Play services supported)
 
-## 3 Creating a New App Based on the Quickstart App {#quickstartapp}
+## 3 Creating a New App Based on the Quickstarter App {#quickstartapp}
 
 For details on making a Mendix app using the Blank Native Mobile App template, download the Make It Native 8 app on either the [Google Play store](https://play.google.com/store/apps/details?id=com.mendix.developerapp) or the [Apple App Store](https://apps.apple.com/us/app/make-it-native/id1334081181). This app template includes the latest version of Atlas UI, as well as the [Native Mobile Resources](/appstore/modules/native-mobile-resources/) module containing widgets and nanoflow actions for native mobile apps. For more information on building native mobile apps, see the [Build a Native Mobile Inspection App](https://academy.mendix.com/link/path/66) learning path (you must be signed in to the Mendix Platform to see this learning path). Using the Make It Native app to view the changes to your Mendix app, see the sections below.
 

content/en/docs/howto8/mobile/native-mobile/getting-started-with-native-mobile.md

@@ -14,10 +14,10 @@ With Mendix 8, you have the capacity to alter design properties with Mendix Stud
 ## 2 Prerequisites 
 
 * Install an integrated development environment (IDE) of your choice (Mendix recommends [Microsoft Visual Studio Code](https://code.visualstudio.com/))
-* Create a Mendix app based on the Blank Native Mobile App template by following the [Creating a New App Based on the Quickstart App](/howto8/mobile/getting-started-with-native-mobile/#quickstartapp) section of *Get Started with Native Mobile*
+* Create a Mendix app based on the Blank Native Mobile App template by following the [Creating a New App Based on the Quickstarter App](/howto8/mobile/getting-started-with-native-mobile/#quickstartapp) section of *Get Started with Native Mobile*
 * Download the Make It Native 8 app on your mobile device via either the [Google Play](https://play.google.com/store/apps/details?id=com.mendix.developerapp) store or the [Apple App Store](https://apps.apple.com/us/app/make-it-native/id1334081181) so you can text your app and see your styling changes
 
-### 3 Customizing the Quickstart App
+### 3 Customizing the Quickstarter App
 
 The [Blank Native Mobile App](https://marketplace.mendix.com/link/component/109511/) is styled using an Atlas UI resources package. This package consists of: