Merge pull request #9984 from mendix/qt-review

Review Resources docs

Author: quinntracy

content/en/docs/refguide/modeling/resources/_index.md

@@ -18,7 +18,7 @@ To add a resource document, do the following:
 
 1. In the [App Explorer](/refguide/app-explorer/), right-click the module or a folder you want to add a resource to and select **Add other**:
 
-    {{< figure src="/attachments/refguide/modeling/resources/app-explorer-resources.png" class="no-border" >}}
+    {{< figure src="/attachments/refguide/modeling/resources/add-resources.png" class="no-border" >}}
 
 2. In the **Resources** category, select the document you would like to add to your app.
 
@@ -28,18 +28,19 @@ The **Resources** category contain various document types that can be used in di
 
 | Element            | Is used in                      | Description                                                  |
 | ------------------ | -------------------------------------- | ------------------------------------------------------------ |
+| [Dataset](/refguide/data-sets/) | Pages                                  | Datasets define the data shown in reports widgets.        |
 | [Java action](/refguide/java-actions/) | Microflows                             | Java actions can extend the functionality of your application. They can be called from microflows. |
 | [JavaScript action](/refguide/javascript-actions/) | Nanoflow                               | JavaScript actions can extend the functionality of your application. They can be called from nanoflows. |
+| [Task queue](/refguide/task-queue/) |  Microflows and Java actions                                 | A Task queue allows you to run microflows or Java actions asynchronously while controlling the number of tasks that are active.   |
 | [Rule](/refguide/rules/)      | Microflows                             | Rules contain the application logic that should result in an enumeration or a Boolean. They are used in decisions in microflows. |
 | [Enumeration](/refguide/enumerations/) | Domain model                           | Enumerations are used to define attributes of an enumeration type. |
-| [Dataset](/refguide/data-sets/) | Pages                                  | Datasets define the data shown in reports widgets.        |
 | [Constant](/refguide/constants/) | Microflow expressions and Consumed web services | Constants are used to define configuration values.           |
 | [Regular expression](/refguide/regular-expressions/) | Domain model                           | Regular expressions are used in validation rules to define criteria that a string should match to pass the validation. They cannot be used in other places which require regular expressions (for example, the *isMatch()* function). |
 | [Scheduled event](/refguide/scheduled-events/) | Microflows                     | Scheduled events let the runtime execute a microflow at a specific moment in time. |
-| [Document template](/refguide/document-templates/) | Microflows                             | Document template is used to format the document in a client and to download or print it. |
+| [Document template](/refguide/document-templates/)(deprecated) | Microflows                             | Document template is used to format the document in a client and to download or print it. |
 
 ## Read More
 
 * [Microflows](/refguide/microflows/)
-* [Domain Model]
+* [Data in the Domain Model](/refguide/domain-model/)
 * [Pages](/refguide/pages/)

content/en/docs/refguide/modeling/resources/constants.md

@@ -1,17 +1,17 @@
 ---
 title: "Constants"
 url: /refguide/constants/
-weight: 60
+weight: 70
 #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.
 ---
 
 ## Introduction
 
 Constants are used to define configuration values. These can differ per environment.
 
-When running the application on a licensed Mendix Cloud environment, SAP BTP, or Mendix on Kubernetes you can configure the constant values for each environment separately using the [Model Options](/developerportal/deploy/environments-details/#model-options) tab of the **Environment Details** page to set your constants.
+When running the application on a licensed Mendix Cloud environment, SAP BTP, or Mendix on Kubernetes, you can configure the constant values for each environment separately using the [Model Options](/developerportal/deploy/environments-details/#model-options) tab of the **Environment Details** page to set your constants.
 
-For other cloud environments – for example, Siemens [Insights Hub](/partners/siemens/mindsphere/) – the constants can be accessed as **Environment Variables** in, for instance, Cloud Foundry. The constant is exposed with the name **module** + **.** + **constant** (for example, `mymodule.myconstant`).
+For other cloud environments (for example, Siemens [Insights Hub](/partners/siemens/mindsphere/)), the constants can be accessed as **Environment Variables** in, for instance, Cloud Foundry. The constant is exposed with the name *module* + *.* + *constant* (for example, `mymodule.myconstant`).
 
 When running the application locally or in a Free App environment, the values defined in Studio Pro are used.
 
@@ -47,7 +47,7 @@ This property is only available for add-on and solution modules. For more inform
 
 ### Documentation
 
-This field is for documentation purposes only: end-users will never see it, and it does not influence the behavior of your application
+This field is for documentation purposes only. End-users will never see it, and it does not influence the behavior of your application.
 
 ## Type Properties
 
@@ -71,7 +71,7 @@ This property defines whether the constant is accessible from client-side expres
 | No *(default)* | The constant will not be sent to the client and will be only accessible from [microflow](/refguide/microflows/) expressions |
 
 {{% alert color="warning" %}}
-When a constant is exposed to the client, Mendix Runtime sends its value to the client so that in addition to microflow expressions, it will also be accessible from nanoflows and page expressions. This means that you should not use sensitive data or secrets such as passwords when a constant is exposed to the client.
+When a constant is exposed to the client, the Mendix Runtime sends its value to the client so that in addition to microflow expressions, it will also be accessible from nanoflows and page expressions. This means you should not use sensitive data or secrets such as passwords when a constant is exposed to the client.
 
 For a web app, changes to a constant's values are reflected when the end-user refreshes the browser or restarts the app. For an offline-first PWA or native application, the app stores the constants' values for offline use. The app updates the constant's values in the following cases:
 

content/en/docs/refguide/modeling/resources/document-templates.md

@@ -1,7 +1,7 @@
 ---
-title: "Document Templates"
+title: "Document Templates (Deprecated)"
 url: /refguide/document-templates/
-weight: 90
+weight: 100
 aliases:
     - /refguide/Document+Templates.html
     - /refguide/Document+Templates
@@ -55,4 +55,4 @@ Generating Microsoft Word documents is no longer supported by Mendix. However, t
 
 ### Other Formats
 
-Other formats, including Rich Text Format (.rtf) and OpenDocument Text (.odt), are no longer supported by Mendix and do not have official alternatives. We understand this may impact certain use cases, and we recommend exploring whether supported formats like PDF or HTML can meet your current needs.
+Other formats, including Rich Text Format (*.rtf*) and OpenDocument Text (*.odt*), are no longer supported by Mendix and do not have official alternatives. We understand this may impact certain use cases and recommend exploring whether supported formats like PDF or HTML can meet your current needs.

content/en/docs/refguide/modeling/resources/enumerations.md

@@ -1,7 +1,7 @@
 ---
 title: "Enumerations"
 url: /refguide/enumerations/
-weight: 40
+weight: 60
 aliases:
     - /refguide/enumeration-values.html
     - /refguide/enumeration-values
@@ -13,49 +13,47 @@ aliases:
 
 An enumeration defines a list of predefined values. Enumerations are used for the enumeration attribute type. For example, the status of an order can be *Open*, *Closed*, or *In Progress*. So, the enumeration for the order status will consist of three values: *Open*, *Closed*, and *In_Progress*. 
 
-An enumeration consists of one or more [enumeration values](/refguide/enumerations/#enum-properties). Each value represents one option. An attribute of the enumeration type can also represent an uninitialized state: for example, if you do not assign any status to an order, the order status will be *empty*. 
+An enumeration consists of one or more [enumeration values](/refguide/enumerations/#enum-properties). Each value represents one option. An attribute of the enumeration type can also represent an uninitialized state. For example, if you do not assign any status to an order, the order status will be *empty*. 
 
 ## Enumeration Properties {#enum-properties}
 
 An enumeration has the following properties:
 
-* **Name** – The name of the enumeration.
-* **Documentation** - This can be used to explain to other developers about the enumeration. End-users cannot see this documentation.
-* **Export level** – Allows you to define access level to this document on the consumer (customer) side when developing an add-on module or a solution. 
+* **Name** – the name of the enumeration
+* **Documentation** - can be used to share information about the enumeration to other developers; end-users cannot see this documentation
+* **Export level** – allows you to define access level to this document on the consumer (customer) side when developing an add-on module or a solution
 
     {{% alert color="info" %}}This property is only available for add-on and solution modules. For more information on types of modules, see the [Module Types](/refguide/modules/#module-types) section in *Modules*.{{% /alert %}}
 
     **Export level** has the following values:   
 
-    * **Hidden** *(default)* – The document/element content is hidden from a consumer. 
-    * **Usable** – Consumers can use the enumeration in their apps. 
+    * **Hidden** *(default)* – the document/element content is hidden from a consumer
+    * **Usable** – consumers can use the enumeration in their apps
 
 * **Enumeration values** – An enumeration has one or more enumeration values. Each value represents one of the options. For more information on enumeration values and their properties, see the [Enumeration Value Properties](#enum-value-properties) section.
 
 The following properties are only available when the enumeration is an external enumeration that is part of a [consumed Odata service](/refguide/consumed-odata-service/):
 
-* **From service** - This property shows the source of the enumeration and allows you to **Detach** the enumeration from the source if the source has been deleted. 
-* **Original name** - The original name of the enumeration from the source.
+* **From service** - shows the source of the enumeration and allows you to detach the enumeration from the source if the source has been deleted 
+* **Original name** - the original name of the enumeration from the source
 
 ### Enumeration Value Properties {#enum-value-properties}
 
-Enumeration value properties are described below:
-
 #### Caption 
 
-This is the caption of an enumeration value is the text that the end-user sees for this enumeration value.
+The caption of an enumeration value is the text the end-user sees for this enumeration value.
 
 The caption can be changed and can contain any character. For example, *In Progress* is a valid caption even though it contains a space.  
 
 This is a translatable text. For more information, see [Language Menu](/refguide/translatable-texts/). 
 
 #### Name {#name}
 
-This is the name of an enumeration value. It is a technical name of the value which is used to refer to the enumeration value in your app.
+This is the name of an enumeration value. It is a technical name of the value that is used to refer to the enumeration value in your app.
 
 The name of an enumeration value must be a technical name, starting with a letter and only containing letters, digits, and underscores.
 
-<details><summary>It cannot be a reserved word (click to see a list of reserved words)</summary>
+<details><summary>The name cannot be a reserved word (click to see a list of reserved words)</summary>
 
 * `_`
 * `abstract`
@@ -137,26 +135,26 @@ The name of an enumeration value is also used for storing the enumeration value
 
 This is an image selected for an enumeration value to be displayed in a data grid column.
 
-To use the image in a data grid, set the enumeration format of the column to *Image*. For more information on data grid columns, see [Grid Columns](/refguide/columns/).
+To use the image in a data grid, set the enumeration format of the column to **Image**. For more information on data grid columns, see [Grid Columns](/refguide/columns/).
 
 ## Creating an Enumeration  
 
 To create a new enumeration, do the following: 
 
-1. In the [App Explorer](/refguide/app-explorer/), right-click the module or a folder you want to add enumeration to and in the list of actions, select **Add other** > **Enumeration**.
-2. In the **Add Enumeration** dialog box, fill out the name of the enumeration.
+1. In the [App Explorer](/refguide/app-explorer/), right-click the module or a folder you want to add enumeration to and select **Add other** > **Enumeration**.
+2. In the **Add Enumeration** dialog box, add the name of the enumeration.
 3. In the **Enumeration** dialog box, click **New** to create enumeration values:
 
-    1. Fill out **Name** and **Caption** for an enumeration value. You can set **Image** for it if necessary. For more information on enumeration properties, see the [Enumeration Properties](#enum-properties) section. <br />
+    1. Add **Name** and **Caption** for the enumeration value. You can set **Image** for it, if necessary.
 
         {{< figure src="/attachments/refguide/modeling/resources/enumerations/add-enum-value.png" class="no-border" >}}
 
-    1. Click **OK** to save the enumeration value.
+    2. Click **OK** to save the enumeration value.
 
 4. Repeat step 3 for every enumeration value that you want to create.
 5. Click **OK** to save the enumeration. 
 
-You have added a new enumeration to your app. You can use the same enumeration for different attributes of the enumeration type in your app. 
+You can use the same enumeration for different attributes of the enumeration type in your app. 
 
 ## Read More
 

content/en/docs/refguide/modeling/resources/java-actions.md

@@ -1,14 +1,14 @@
 ---
 title: "Java Actions"
 url: /refguide/java-actions/
-weight: 10
+weight: 20
 description: "Describes using Java Actions to extend the functionality of your Mendix app."
 #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.
 ---
 
 ## Introduction
 
-With Java actions you can extend the functionality of your application in situations where it would be hard to implement this functionality in microflows. You can call a Java action from a microflow using the [Call Java action](/refguide/call-java-action/).
+With Java actions you can extend the functionality of your application in situations where it would be hard to implement this functionality in microflows. You can call a Java action from a microflow using the [Call Java action](/refguide/call-java-action/) activity.
 
 {{% alert color="info" %}}
 Each Java action defined in Studio Pro corresponds to a file *{name of Java action}.java* in the subdirectory *javasource/{module name}/actions* of the app directory.

content/en/docs/refguide/modeling/resources/javascript-actions.md

@@ -1,7 +1,7 @@
 ---
 title: "JavaScript Actions"
 url: /refguide/javascript-actions/
-weight: 20
+weight: 30
 description: "This reference guide details the ways JavaScript Actions can extend the functionality of your Mendix app."
 #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.
 ---
@@ -26,7 +26,7 @@ To learn how to create, configure, and use a JavaScript action, see these [Build
 
 ## General Settings
 
-After double-clicking a JavaScript action in your **App Explorer** you will see the JavaScript action's settings: 
+Double-click the JavaScript action in your **App Explorer** to open the action's settings: 
 
 {{< figure src="/attachments/refguide/modeling/resources/javascript-actions/javascript-action-settings-no-para.png" alt="javascript settings" width="600"  class="no-border" >}}
 

content/en/docs/refguide/modeling/resources/regular-expressions.md

@@ -1,7 +1,7 @@
 ---
 title: "Regular Expressions"
 url: /refguide/regular-expressions/
-weight: 70
+weight: 80
 #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.
 ---
 
@@ -33,9 +33,9 @@ Here are two post code examples: **3072AP** and **7500 AH**.
 These are the criteria:
 
 * The first character is a digit in the range 1 to 9
-* The second, third and fourth characters are digits in the range 0 to 9
+* The second, third, and fourth characters are digits in the range 0 to 9
 * The last two characters are letters, as expressed by the last two subexpression [A-Za-z], which indicate that the last two characters should be in the range A-Z or the range a-z
-* Between the digits and the letters there can be a space, as expressed by the subexpression which consists of a space and a question mark; the question mark indicates that the space is optional
+* There can be a space between the digits and the letters, as expressed by the subexpression which consists of a space and a question mark; the question mark indicates that the space is optional
 {{% /alert %}}
 
 The following sections give a summary of regular expressions that can be used in Mendix. This description also applies to regular expression strings used in functions such as *isMatch()*.
@@ -52,7 +52,7 @@ A regular expression can contain the following types of subexpressions:
 
     {{% alert color="info" %}}These forms can be mixed: `[abcx-z]` matches "*a*", "*b*", "*c*", "*x*", "*y*", or "*z*", and is equivalent to `[a-cx-z]`. The `-` character is treated as a literal character if it is the last or the first character within the brackets, or if it is escaped with a backslash.{{% /alert %}}
 
-* `[^ ]` – matches a single character that is NOT contained within the brackets, for example:
+* `[^ ]` – matches a single character that is not contained within the brackets, for example:
     * `[^abc]` matches any character other than "a", "b", or "c"
     * `[^a-z]` matches any single character that is not a lowercase letter from "a" to "z"
 
@@ -68,10 +68,10 @@ A regular expression can contain the following types of subexpressions:
 * A literal character – this is a character that does not have a special meaning in the regular expression language and it matches itself; this is effectively any character except `\[](){}^-$?*+|.`, for example:
     * The *`space`* in the Dutch post code example is a literal character that just matches itself
 
-    {{% alert color="info" %}}If you need to match one of the characters which is not a literal, prefix it with a backslash.{{% /alert %}}
+    {{% alert color="info" %}}If you need to match one of the characters that is not a literal, prefix it with a backslash.{{% /alert %}}
 
 * `\w` – a word: a letter, digit, or underscore; `\w` is an abbreviation for `[A-Za-z0-9_]`
-* `\d` – a digit" an abbreviation for `[0-9]`
+* `\d` – a digit; an abbreviation for `[0-9]`
 
 ### Quantifiers
 
@@ -81,10 +81,10 @@ The following quantifiers can be used:
 
 | Quantifier | Description  |
 | --- | --- |
-| ? | The preceding sub-expression should occur not or once. |
-| * | The preceding sub-expression occurs any number of times. |
-| + | The preceding sub-expression should occur once or more. |
-|   | No quantifier means that the preceding sub-expression should occur exactly once. |
+| ? | The preceding subexpression should occur not or once. |
+| * | The preceding subexpression occurs any number of times. |
+| + | The preceding subexpression should occur once or more. |
+|   | No quantifier means that the preceding subexpression should occur exactly once. |
 
 ## Read More