From b10793d05447801f353cd469d6d2d113dc738108 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sun, 1 Mar 2026 20:19:37 +0000 Subject: [PATCH] Run markdownlint-cli2 on docs to find (and correct) linting errors. --- .../security/certificate-management.md | 2 +- .../backups/create-backup.md | 1 - .../certificates/central-certificates.md | 2 +- .../monitoring-with-apm/dynatrace-metrics.md | 2 +- .../deployment/mx-azure/mx-azure-backups.md | 1 - .../private-cloud-cluster/_index.md | 6 +- .../modules/data-widgets/_index.md | 16 +- .../data-widgets/data-grid-2-properties.md | 4 +- .../modules/data-widgets/data-grid-2.md | 160 +++++++++--------- .../modules/data-widgets/gallery.md | 70 ++++---- .../modules/data-widgets/selection-helper.md | 24 +-- .../modules/snowflake/mendix-data-loader.md | 2 +- .../services/business-events/_index.md | 2 +- .../business-events-configuration.md | 2 +- .../business-events-deployment.md | 2 +- .../services/event-broker.md | 2 +- content/en/docs/private-platform/pmp-maia.md | 16 +- .../private-platform/pmp-prerequisites.md | 16 +- .../docs/private-platform/pmp-quickstart.md | 2 +- .../app/app-settings/certificates-tab.md | 2 +- .../app/app-settings/dependencies-tab.md | 2 +- .../app/app-settings/languages-tab.md | 2 +- .../app/app-settings/runtime-tab.md | 2 +- .../app/app-settings/theme-tab.md | 2 +- .../app/app-settings/workflow-tab.md | 2 +- .../microflow-element-common-properties.md | 14 +- .../dev-best-practices/app-setup.md | 2 +- .../dev-best-practices/naming-conventions.md | 2 +- .../runtime/date-and-time-handling/_index.md | 2 +- .../app-explorer/app/app-settings/_index.md | 1 - .../runtime/date-and-time-handling/_index.md | 4 +- .../runtime/date-and-time-handling/_index.md | 4 +- content/en/docs/releasenotes/catalog/2021.md | 2 +- content/en/docs/releasenotes/catalog/2022.md | 2 +- content/en/docs/releasenotes/catalog/2023.md | 2 +- content/en/docs/releasenotes/catalog/2024.md | 2 +- content/en/docs/releasenotes/catalog/2025.md | 2 +- content/en/docs/releasenotes/catalog/2026.md | 2 +- .../en/docs/releasenotes/catalog/_index.md | 2 +- .../nt-studio-pro-10-parent/nt-14-rn.md | 6 +- .../docs/releasenotes/studio-pro/10/10.24.md | 28 +-- .../docs/releasenotes/studio-pro/11/11.3.md | 1 - .../workstation/wks-batch-registration.md | 3 +- .../en/docs/workstation/wks-message-syntax.md | 1 + 44 files changed, 211 insertions(+), 215 deletions(-) diff --git a/content/en/docs/control-center/security/certificate-management.md b/content/en/docs/control-center/security/certificate-management.md index 00954bc82f7..a475433f0e0 100644 --- a/content/en/docs/control-center/security/certificate-management.md +++ b/content/en/docs/control-center/security/certificate-management.md @@ -63,4 +63,4 @@ For detailed information about how Mendix Admins can use the **Certificate Manag * [Certificates](/developerportal/deploy/certificates/) * [Application-Level Certificates](/developerportal/deploy/application-level-certificates/) -* [Custom Domains](/developerportal/deploy/custom-domains/) \ No newline at end of file +* [Custom Domains](/developerportal/deploy/custom-domains/) diff --git a/content/en/docs/deployment/mendix-cloud-deploy/backups/create-backup.md b/content/en/docs/deployment/mendix-cloud-deploy/backups/create-backup.md index a386cd8ef79..8d4d660b0b5 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/backups/create-backup.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/backups/create-backup.md @@ -34,7 +34,6 @@ To create a backup archive of a licensed app, follow these steps: {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/create-backup/backup-rds-window-failure.png" >}} - Once you have created a backup archive, you can download it by clicking **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) then selecting **Download**. For more information, see [Downloading a Backup](/developerportal/operate/download-backup/). {{% alert color="info" %}} diff --git a/content/en/docs/deployment/mendix-cloud-deploy/certificates/central-certificates.md b/content/en/docs/deployment/mendix-cloud-deploy/certificates/central-certificates.md index bf1902e6b2e..74c68153927 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/certificates/central-certificates.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/certificates/central-certificates.md @@ -117,4 +117,4 @@ Every hostname covered by the existing certificate must be included in the Subje * [Certificates](/developerportal/deploy/certificates/) * [Certificate Management](/control-center/certificate-management/) -* [Custom Domains](/developerportal/deploy/custom-domains/) \ No newline at end of file +* [Custom Domains](/developerportal/deploy/custom-domains/) diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md b/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md index e364c1d43f0..f7883cb5d5c 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md @@ -39,7 +39,7 @@ To start sending your Mendix app's metrics to Dynatrace, you need to set some en | Variable | Required? | Description | Details | |--------------------------|-----------|------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `DT_SAAS_URL` | Yes | The URL of Dynatrace environment | The format when using the Dynatrace SaaS environment is similar to `https://.live.dynatrace.com`. If you are using a Dynatrace managed environment, just provide the full URL of the Dynatrace domain, like `https://`. | - | `DT_TENANT` | Yes | The Dynatrace Environment ID | For more information, see the [Environment ID](https://docs.dynatrace.com/docs/discover-dynatrace/get-started/monitoring-environment#environment-id) section of _Dynatrace_. | + | `DT_TENANT` | Yes | The Dynatrace Environment ID | For more information, see the [Environment ID](https://docs.dynatrace.com/docs/discover-dynatrace/get-started/monitoring-environment#environment-id) section of *Dynatrace*. | | `DT_PAAS_TOKEN` | Yes | The access token for integrating your Mendix app with Dynatrace | Create this on the Dynatrace environment. For more information, see [Generate an Access Token](https://www.dynatrace.com/support/help/get-started/access-tokens#create-api-token). The token must include the `PaaS integration - Installer download` and `Ingest metrics` scopes. For logging integration, `Ingest logs` scope is also required. | | `DT_ENABLE_LOGS` | No | Set this to `true` to enable logging | Only supported for Dynatrace SaaS. `Ingest logs` scope is required to be included in the access token. | | `DT_IS_MANAGED` | No | Set this to `true` if you are using Dynatrace Managed. The default is assumed to be Dynatrace SaaS and set to `false`. | This variable is only needed for custom application metrics ingestion. | diff --git a/content/en/docs/deployment/mx-azure/mx-azure-backups.md b/content/en/docs/deployment/mx-azure/mx-azure-backups.md index 61353b5e3b6..209080e1b4a 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-backups.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-backups.md @@ -150,4 +150,3 @@ As a workaround, you can restore a backup across clusters by performing the foll 1. Download the backup snapshot from your source environment to your local machine. 2. Upload the downloaded backup snapshot from your local machine to the target environment. 3. Begin the restore process within the target environment using the newly uploaded backup snapshot. - diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md index 3074a51df6f..5f8b3c3bc00 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md @@ -1369,7 +1369,7 @@ You can invite additional members to the namespace, and configure their role dep {{% alert color="info" %}}The **Automatically accept invites** option is applicable only when the invited users have the same email domain as yours.{{% /alert %}} -5. Give them the rights they need. This can be: +1. Give them the rights they need. This can be: 1. **Developer** – a standard set of rights needed by a developer, these are listed on the screen 2. **Administrator** – a standard set of rights needed by an administrator, these are listed on the screen @@ -1384,11 +1384,11 @@ If an application is in the Stopped state, the scaling does not come into effect Along with this, we have also decoupled the permission for modifying the MxAdmin password and managing environments. {{% /alert %}} -6. Click **Send Invite** to send an invite to this person. +1. Click **Send Invite** to send an invite to this person. {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/AutoAcceptInvite.png" class="no-border" >}} -7. If you have not enabled the **Automatically accept invites** option, the user will receive an email and will be required to follow a link to confirm that they want to join this namespace. They will need to be logged in to Mendix when they follow the confirmation link. +2. If you have not enabled the **Automatically accept invites** option, the user will receive an email and will be required to follow a link to confirm that they want to join this namespace. They will need to be logged in to Mendix when they follow the confirmation link. ##### Editing and Removing Members diff --git a/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/_index.md b/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/_index.md index 9a92e57262a..602821fa088 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/_index.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/_index.md @@ -11,18 +11,18 @@ description: "Describes the configuration and usage of the Data Widgets module, This module contains the following widgets: -- [Data Grid 2](/appstore/modules/data-grid-2/) -- [Data Grid 2 Properties](/appstore/modules/data-grid-2-properties/) -- [Drop-Down Sort](/appstore/modules/gallery/#dropdown) -- [Filters](/appstore/modules/data-grid-2/#filters) -- [Gallery](/appstore/modules/gallery/) -- [Selection helper](/appstore/modules/selection-helper/) -- [Tree node](/appstore/modules/tree-node/) +* [Data Grid 2](/appstore/modules/data-grid-2/) +* [Data Grid 2 Properties](/appstore/modules/data-grid-2-properties/) +* [Drop-Down Sort](/appstore/modules/gallery/#dropdown) +* [Filters](/appstore/modules/data-grid-2/#filters) +* [Gallery](/appstore/modules/gallery/) +* [Selection helper](/appstore/modules/selection-helper/) +* [Tree node](/appstore/modules/tree-node/) ## Migration If you were previously using the Data Grid 2 module, you must follow these steps before updating it to the new [Data Widgets](https://marketplace.mendix.com/link/component/116540) module: -1. Rename the current **DataGrid** module (under **Marketplace** modules) to _DataWidgets_ in Studio Pro. +1. Rename the current **DataGrid** module (under **Marketplace** modules) to *DataWidgets* in Studio Pro. 1. Open the Marketplace and search for **Data Widgets**. 1. Download and replace the current (renamed) DataWidgets module. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/data-grid-2-properties.md b/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/data-grid-2-properties.md index c94f6fbd3e6..2f73fc175c9 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/data-grid-2-properties.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/data-grid-2-properties.md @@ -27,8 +27,8 @@ The time (in seconds) the grid waits between refreshing the data. Auto-refreshin This property controls row selection capabilities. Selection is turned off by default, but can be enabled by choosing ether **Single** or **Multi**: -- The **Single** selection is selection type where only one row can be selected at the time -- The **Multi** type support selecting several rows at the time +* The **Single** selection is selection type where only one row can be selected at the time +* The **Multi** type support selecting several rows at the time {{% alert color="info" %}} Data grid currently supports in-memory selection. When the **Keep Selection** property is disabled, selection is limited to visible rows and will be cleared when you change a data grid page or reload the browser window. When **Keep Selection** is enabled, selections persist across page navigation, data refreshes, filter operations, and sorting changes. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/data-grid-2.md b/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/data-grid-2.md index d76067a9bcb..513dc4123e2 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/data-grid-2.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/data-grid-2.md @@ -21,15 +21,15 @@ Here is an example of a data grid using filters: You can enable these advanced options to customize your data grid: -- Pagination type and positioning -- Row count display -- Loading state indicators -- Empty list option -- Dynamic row and cell class -- Column capabilities -- Filter personalization settings -- Custom configuration -- Modular filtering with dedicated filter widgets +* Pagination type and positioning +* Row count display +* Loading state indicators +* Empty list option +* Dynamic row and cell class +* Column capabilities +* Filter personalization settings +* Custom configuration +* Modular filtering with dedicated filter widgets ## Capabilities @@ -39,9 +39,9 @@ In the new data grid, you are able to choose how users can iterate within the gr **Sorting** enables the header to be clickable. When clicked it will switch between ascending, descending, and no sorting. This functionality can be discerned according to the arrows on the right side: -- Arrow up: ascending sorting applied -- Arrow down: descending sorting applied -- Double-sided arrow: no sorting is applied +* Arrow up: ascending sorting applied +* Arrow down: descending sorting applied +* Double-sided arrow: no sorting is applied {{< figure src="/attachments/appstore/platform-supported-content/modules/data-widgets/data-grid-2/sorting-asc.png" alt="Ascending sort" class="no-border" >}} {{< figure src="/attachments/appstore/platform-supported-content/modules/data-widgets/data-grid-2/sorting-desc.png" alt="Descending sort" class="no-border" >}} @@ -109,8 +109,8 @@ The **Paging Buttons** option will render the default buttons as the previous da You can configure pagination based on the following properties: -- **Position** — The **Position of paging button** options allow you to position paging buttons above or below the data grid. -- **Visibility** — The **Show paging buttons** options allow you to always show paging, or to automatically show and hide paging based on the amount of available data compared to the display limit per page. +* **Position** — The **Position of paging button** options allow you to position paging buttons above or below the data grid. +* **Visibility** — The **Show paging buttons** options allow you to always show paging, or to automatically show and hide paging based on the amount of available data compared to the display limit per page. ### Virtual Scrolling @@ -158,9 +158,9 @@ You can define how each cell will be rendered in the data grid. We offer three c {{< figure src="/attachments/appstore/platform-supported-content/modules/data-widgets/data-grid-2/column-width.png" alt="Settings for column width for each column item" class="no-border" >}} -- **Auto-fill** — With this option it will auto define the width of your column, if all columns are using auto-fill, it will divide evenly the same width, if another column is configured with auto-fit or manual, it will fill the available space. -- **Auto-fit** — Content With this option it will calculate the width of your column based on the content of each row. -- **Manual** — With this option you will manually define the size of your column based of flexbox grow values, for more information, please [check here](https://www.w3.org/TR/css-flexbox-1/). +* **Auto-fill** — With this option it will auto define the width of your column, if all columns are using auto-fill, it will divide evenly the same width, if another column is configured with auto-fit or manual, it will fill the available space. +* **Auto-fit** — Content With this option it will calculate the width of your column based on the content of each row. +* **Manual** — With this option you will manually define the size of your column based of flexbox grow values, for more information, please [check here](https://www.w3.org/TR/css-flexbox-1/). ### Alignment @@ -208,10 +208,10 @@ Association filtering configuration has been moved from column properties to the The dropdown filter widget supports association filtering when configured in custom mode: -- **Entity (Association)** — defines the association that will be used for filtering -- **Selectable objects** — defines data source for filter options, returning list of all possible entities that could be associated -- **Use lazy load** — controls when filter options are loaded. When set to **No** (recommended), data is fetched immediately providing better personalization support. When set to **Yes**, data is fetched only when the filter is opened, improving initial load times but limiting personalization capabilities -- **Option caption** — expression used as caption for each option in the dropdown +* **Entity (Association)** — defines the association that will be used for filtering +* **Selectable objects** — defines data source for filter options, returning list of all possible entities that could be associated +* **Use lazy load** — controls when filter options are loaded. When set to **No** (recommended), data is fetched immediately providing better personalization support. When set to **Yes**, data is fetched only when the filter is opened, improving initial load times but limiting personalization capabilities +* **Option caption** — expression used as caption for each option in the dropdown ### Visible {#visible-filter} @@ -251,8 +251,8 @@ Triggers an action (such as a nanoflow, microflow, or Show page action) when the Data Grid 2 uses a modular filtering system with dedicated filter widgets that can be placed in two locations: -- **Column Headers**: Individual filters can be placed in column headers by enabling **Show column filters**. When this option is selected, a drop zone appears in each column header where you can place the appropriate filter widget. -- **Filters Placeholder**: Grid-wide filters can be placed in the [filters placeholder](/appstore/modules/data-grid-2-properties/#filters-placeholder). This allows for filtering across multiple attributes and more complex filtering scenarios. +* **Column Headers**: Individual filters can be placed in column headers by enabling **Show column filters**. When this option is selected, a drop zone appears in each column header where you can place the appropriate filter widget. +* **Filters Placeholder**: Grid-wide filters can be placed in the [filters placeholder](/appstore/modules/data-grid-2-properties/#filters-placeholder). This allows for filtering across multiple attributes and more complex filtering scenarios. {{% alert color="warning" %}} The type of your selected attribute should match the filter type. For example, a **Text filter** should be used for a string attribute. @@ -264,8 +264,8 @@ Also the desired attribute must be filterable. For example, not a value which is All filter widgets support two configuration modes: -- **Auto Mode**: automatically detects filterable attributes from the parent grid (works when placed in grid columns) -- **Custom Mode**: allows manual specification of target data source and attributes for more flexible filtering scenarios +* **Auto Mode**: automatically detects filterable attributes from the parent grid (works when placed in grid columns) +* **Custom Mode**: allows manual specification of target data source and attributes for more flexible filtering scenarios {{< figure src="/attachments/appstore/platform-supported-content/modules/data-widgets/data-grid-2/settings-show-column-filters.png" alt="Settings for data grid 2" class="no-border" >}} @@ -279,13 +279,13 @@ Here is an example of dropzones for filters in **Structure mode**: **Date filter** allows users to match date attributes based on these predefined criteria: -- Between -- Greater than -- Greater than or equal -- Equal -- Not equal -- Smaller than -- Smaller than or equal +* Between +* Greater than +* Greater than or equal +* Equal +* Not equal +* Smaller than +* Smaller than or equal Here is an example of **Date filter** as **Between**: @@ -319,7 +319,7 @@ When **Default filter** is defined as **Between** these fields will appear to de In this section you can select a **Saved attribute** in order to save the current value of the filter. However, the value is not automatically applied to the widget. To restore the previously saved value of the filter, you must configure the same attribute as the **Default value** of the widget. The attribute available in this section must be this type: -- Date & Time +* Date & Time #### Events @@ -335,11 +335,11 @@ In custom mode, you can manually configure the data source and attributes, while For association filtering, you can configure: -- **Filter by Association**: sets the filter to operate on entity associations -- **Entity**: selects the target association for filtering -- **Selectable objects**: configures the data source that provides available filter options -- **Use lazy load**: controls when options are loaded (immediate vs on-demand) -- **Option caption**: defines how each option is displayed to users +* **Filter by Association**: sets the filter to operate on entity associations +* **Entity**: selects the target association for filtering +* **Selectable objects**: configures the data source that provides available filter options +* **Use lazy load**: controls when options are loaded (immediate vs on-demand) +* **Option caption**: defines how each option is displayed to users The filter also supports enhanced features like multi-select, filterable options (combobox-style), and various selection methods (checkbox or row click). @@ -355,8 +355,8 @@ When a drop-down filter is used in conjunction with an [Association Filter](#ass When adding a new option, the following properties are required: -- **Caption** — The text being rendered for each option in the drop-down. -- **Value** — The corresponding value that will be compared, if a value is being compared with an enumeration, it should match exactly the enumeration value. This property allows the usage of expression (you can use conditionals to apply dynamic values). +* **Caption** — The text being rendered for each option in the drop-down. +* **Value** — The corresponding value that will be compared, if a value is being compared with an enumeration, it should match exactly the enumeration value. This property allows the usage of expression (you can use conditionals to apply dynamic values). {{< figure src="/attachments/appstore/platform-supported-content/modules/data-widgets/data-grid-2/dropdown-filter-item.png" alt="Example of settings for new option" class="no-border" >}} @@ -370,7 +370,7 @@ You can also define the empty option caption, which will be rendered as the firs In this section you can select a **Saved attribute** in order to save the current value of the filter. However, the value is not automatically applied to the widget. To restore the previously saved value of the filter, you must configure the same attribute as the **Default value** of the widget. The attribute available in this section must be this type: -- String +* String {{% alert color="warning" %}} If **Multiselect** is enabled you must select a String attribute containing `Unlimited` in its size. @@ -386,12 +386,12 @@ In this section you can select an action to be executed **On change** by the fil The **Number filter** allows users to match decimal, integer, and long attributes based on these predefined criteria: -- Greater than -- Greater than or equal -- Equal -- Not equal -- Smaller than -- Smaller than or equal +* Greater than +* Greater than or equal +* Equal +* Not equal +* Smaller than +* Smaller than or equal You can select your filter criteria in the **Number Filter** settings: @@ -415,10 +415,10 @@ To have better control of when the filter will be applied, we offer a **Apply af In this section you can select a **Saved attribute** in order to save the current value of the filter. However, the value is not automatically applied to the widget. To restore the previously saved value of the filter, you must configure the same attribute as the **Default value** of the widget. The attribute available in this section must be one of the following types: -- Autonumber -- Decimal -- Integer -- Long +* Autonumber +* Decimal +* Integer +* Long #### Events @@ -430,15 +430,15 @@ In this section you can select an action to be executed **On change** by the fil **Text filter** allows users to match string attributes based on these predefined criteria: -- Contains -- Starts with -- Ends with -- Greater than -- Greater than or equal -- Equal -- Not equal -- Smaller than -- Smaller than or equal +* Contains +* Starts with +* Ends with +* Greater than +* Greater than or equal +* Equal +* Not equal +* Smaller than +* Smaller than or equal You can select your filter criteria in the **Text filter** settings: @@ -462,8 +462,8 @@ To have better control of when the filter will be applied, we offer a **Apply af In this section you can select a **Saved attribute** in order to save the current value of the filter. However, the value is not automatically applied to the widget. To restore the previously saved value of the filter, you must configure the same attribute as the **Default value** of the widget. The attribute available in this section must be one of the following types: -- Hashed string -- String +* Hashed string +* String #### Events @@ -473,15 +473,15 @@ In this section you can select an action to be executed **On change** by the fil In order to enable filtering within the data grid header (outside the columns) you need to enable `Grid wide filters` and select the desired attributes to be filtered in the **Filtering** tab. You can select attributes of the following types: -- Autonumber -- Boolean -- Date & time -- Decimal -- Enumeration -- Hashed string -- Integer -- Long -- String +* Autonumber +* Boolean +* Date & time +* Decimal +* Enumeration +* Hashed string +* Integer +* Long +* String The attributes selected here will be used for the matching filter placed inside the composable region. Only the first keyword in the filter will be considered when filtering multiple attributes in grid wide filtering @@ -501,11 +501,11 @@ The Data Grid 2 widget ships with built-in functionality to export data from the To export data from the data grid, create a new nanoflow that calls **Export_To_Excel**. The **Export_To_Excel** action has a set of inputs: -- **Datagrid name**: the name of the data grid from which data should be exported (the name can be found and copied from the data grid's settings (**Properties** > **Common** > **Name**)) -- **File name**: the file name to use for the exported document (does not require an appended file extension) -- **Sheet name**: the name to use for the Excel sheet of the exported document. -- **Include column names**: a Boolean expression that, if true, tells the action to include column captions as the first row in the exported document -- **Chunk size**: the number of rows fetched from the backend to the browser at a time. +* **Datagrid name**: the name of the data grid from which data should be exported (the name can be found and copied from the data grid's settings (**Properties** > **Common** > **Name**)) +* **File name**: the file name to use for the exported document (does not require an appended file extension) +* **Sheet name**: the name to use for the Excel sheet of the exported document. +* **Include column names**: a Boolean expression that, if true, tells the action to include column captions as the first row in the exported document +* **Chunk size**: the number of rows fetched from the backend to the browser at a time. {{% alert color="info" %}} The recommended value for **Chunk Size** is 200. However, because each data grid has a unique set of columns and varying amounts of data per row, a different chunk size might result in better performance. @@ -634,7 +634,7 @@ The name of the filter or data grid can be found at **Properties** > **Common** > "The filter widget must be placed inside the column or header of the Data Grid 2.0 or inside header of the Gallery widget." -- Widget placement is incorrect. +* Widget placement is incorrect. **Solution**: Place widget inside Gallery header, Data Grid 2 header, or Data Grid 2 column. @@ -643,7 +643,7 @@ Place widget inside Gallery header, Data Grid 2 header, or Data Grid 2 column. > "Unable to get filter store. Check parent widget configuration." -- This error indicates that there is issue with widget settings. Most of the time this error happens when widget is placed in the header of Data Grid 2 or Gallery, but the **Filter attributes** setting is still set to **Auto**. +* This error indicates that there is issue with widget settings. Most of the time this error happens when widget is placed in the header of Data Grid 2 or Gallery, but the **Filter attributes** setting is still set to **Auto**. **Solution**: Switch widget attributes setting to **Custom** and configure the attribute for filtering. @@ -652,12 +652,12 @@ Switch widget attributes setting to **Custom** and configure the attribute for f > "The [filter] is not compatible with [datatype] data type." -- This error indicates that attribute configured in the Data Grid 2 for column is not compatible with current filter type. +* This error indicates that attribute configured in the Data Grid 2 for column is not compatible with current filter type. **Solution**: Change filter to appropriate filter type. For example for string attributes use text filter. > "The attribute is not filterable. Please choose a different attribute." -- This error indicates that it is not possible to use current attribute for filtering due to technical limitations. +* This error indicates that it is not possible to use current attribute for filtering due to technical limitations. **Solution**: Read and understand why some attributes are filterable and other are not. Change the model or choose another attribute. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/gallery.md b/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/gallery.md index 1a667e4b134..ba1f91ddbd5 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/gallery.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/gallery.md @@ -17,12 +17,12 @@ Here is an example of a Gallery widget using filters: The gallery has an option to enable advanced options. When this option is toggled on, it enables numerous features to customize your gallery: -- Pagination type -- Pagination position -- Empty list option -- Dynamic item class -- Filtering -- Sorting +* Pagination type +* Pagination position +* Empty list option +* Dynamic item class +* Filtering +* Sorting ## Configuration @@ -84,15 +84,15 @@ Triggers an action (such as a nanoflow, microflow, or Show page action) when the In order to enable filtering within the gallery items you need to select the desired attributes to be filtered in the **Filtering** tab. You can select attributes of the following types: -- Autonumber -- Boolean -- Date & time -- Decimal -- Enumeration -- Hashed string -- Integer -- Long -- String +* Autonumber +* Boolean +* Date & time +* Decimal +* Enumeration +* Hashed string +* Integer +* Long +* String The attributes selected here will be used for the matching filter placed inside the composable region. When using multiple attributes, the filters will automatically select the matching attributes and then compose the desired filter value in an `OR expression`. Make sure you just have one filter widget for each type, for example `Text Filter` and `Number Filter`. @@ -108,7 +108,7 @@ An example of text filter being used in the composable region combined with a dr {{< figure src="/attachments/appstore/platform-supported-content/modules/data-widgets/gallery/filter-region.png" alt="Example of filtering composable region" width="300" class="no-border" >}} -For more information about filters, see the [Filters](/appstore/modules/data-grid-2/#filters) section of _Data Grid 2_. +For more information about filters, see the [Filters](/appstore/modules/data-grid-2/#filters) section of *Data Grid 2*. ## Sorting @@ -128,8 +128,8 @@ The Drop-Down Sort widget is a widget you can use in combination with the Galler The Drop-Down Sort widget has two options you can set: -- Empty option caption: value to be used when no value is selected -- Screen reader caption: value to be announced by screen readers when using assistive technology +* Empty option caption: value to be used when no value is selected +* Screen reader caption: value to be announced by screen readers when using assistive technology ## Selection @@ -141,9 +141,9 @@ The Gallery widget keeps selected items in memory and supports selection persist The **Selection** property determines what type of selection is available to users: -- **None**: Selection is disabled. Users cannot select gallery items. -- **Single**: Users can select only one item at a time. Selecting a new item automatically deselects the previously selected item. -- **Multi**: Users can select multiple items simultaneously using various interaction methods. +* **None**: Selection is disabled. Users cannot select gallery items. +* **Single**: Users can select only one item at a time. Selecting a new item automatically deselects the previously selected item. +* **Multi**: Users can select multiple items simultaneously using various interaction methods. When **Selection** is enabled, the Gallery automatically provides visual feedback to indicate selected items and supports keyboard navigation for accessibility. @@ -184,17 +184,17 @@ Gallery selection works seamlessly with action buttons and other widgets placed Place a **Selection Helper** widget in the gallery header to provide bulk selection controls: -- **Select All**: Quickly select all visible items -- **Clear Selection**: Remove all current selections -- **Selection Status**: Visual indicator of current selection state (all, some, or none selected) +* **Select All**: Quickly select all visible items +* **Clear Selection**: Remove all current selections +* **Selection Status**: Visual indicator of current selection state (all, some, or none selected) #### Selection Count Display Enable the **Show selection count** property to display the number of selected items: -- **Top**: Shows count above the gallery items -- **Bottom**: Shows count below the gallery items -- **Off**: Hides the selection count +* **Top**: Shows count above the gallery items +* **Bottom**: Shows count below the gallery items +* **Off**: Hides the selection count The selection count automatically updates as users select or deselect items and includes a "Clear selection" button for easy deselection. @@ -202,10 +202,10 @@ The selection count automatically updates as users select or deselect items and Use the **On selection change** action to trigger custom logic when selection changes: -- Update UI elements based on selection state -- Enable/disable action buttons -- Load additional data for selected items -- Validate selection before allowing operations +* Update UI elements based on selection state +* Enable/disable action buttons +* Load additional data for selected items +* Validate selection before allowing operations ### Keep Selection @@ -225,8 +225,8 @@ You can also see when an item is selected: an item with a light gray background For the keyboard navigation and keyboard selection to work, the user must open the **General** tab and then set the **Selection** property to one of the following: -- **Single**: enables keyboard navigation with just single selection -- **Multi**: to enable keyboard navigation with multi-selection +* **Single**: enables keyboard navigation with just single selection +* **Multi**: to enable keyboard navigation with multi-selection ### Keyboard Navigation @@ -250,5 +250,5 @@ Employing keyboard navigation is an effective way of ensuring users who cannot u The new Gallery widget uses [CSS Grid](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout) as its base for styling. If you need to combine rows or columns you can achieve this using the following helper classes in the `Dynamic item class`: -- `widget-gallery-column-span-1` until `widget-gallery-column-span-12`: these classes merge column spaces, pushing items to a new row when the selected amount is reached for each platform -- `widget-gallery-row-span-1` until `widget-gallery-row-span-12`: these classes merge row spaces, pushing items into new columns or rows when needed +* `widget-gallery-column-span-1` until `widget-gallery-column-span-12`: these classes merge column spaces, pushing items to a new row when the selected amount is reached for each platform +* `widget-gallery-row-span-1` until `widget-gallery-row-span-12`: these classes merge row spaces, pushing items into new columns or rows when needed diff --git a/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/selection-helper.md b/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/selection-helper.md index dd2255c6cc0..25146c1e46e 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/selection-helper.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/data-widgets/selection-helper.md @@ -17,8 +17,8 @@ Here is an example of a Selection Helper widget in a Gallery: Before using the Selection Helper widget, ensure the following: -- **For Gallery** — Gallery widget is configured with Selection set to Multi. -- **For Data Grid 2** — Data Grid 2 is configured with Selection set to Multi. +* **For Gallery** — Gallery widget is configured with Selection set to Multi. +* **For Data Grid 2** — Data Grid 2 is configured with Selection set to Multi. The Selection Helper must be placed inside the data widget's header content area. For specific guidance, see the subsections below. @@ -40,16 +40,16 @@ The Selection Helper must be placed inside the data widget's header content area Controls how the selection control appears to users: -- **Check box** (default) — Displays a standard checkbox that reflects the current selection state. -- **Custom** — Allows you to define custom widgets for different selection states. +* **Check box** (default) — Displays a standard checkbox that reflects the current selection state. +* **Custom** — Allows you to define custom widgets for different selection states. #### Custom Style Available when `Style` is set to `Custom`. Defines custom widgets that display based on the current selection state: -- **None Selected Widget** — Widget displayed when no items are currently selected. Usually contains **Select all** controls or empty state indicators. -- **Some Selected Widget** — Widget displayed when some (but not all) items are selected. Often used to show **Select all** controls or partial selection indicators. -- **All Selected Widget** — Widget displayed when all visible items in the grid are selected. Typically used to show **Clear selection** controls or indicators. +* **None Selected Widget** — Widget displayed when no items are currently selected. Usually contains **Select all** controls or empty state indicators. +* **Some Selected Widget** — Widget displayed when some (but not all) items are selected. Often used to show **Select all** controls or partial selection indicators. +* **All Selected Widget** — Widget displayed when all visible items in the grid are selected. Typically used to show **Clear selection** controls or indicators. Here is an example of a **Selection Helper** widget with a custom style configured: @@ -75,9 +75,9 @@ Provides an optional text label displayed next to the checkbox. Use this to prov The Selection Helper maintains real-time synchronization with the parent data widget: -- Changes made through the Selection Helper immediately reflect in individual row and item selections -- Individual row and item selection changes update the Selection Helper state accordingly -- Selection state persists across pagination when **Keep selection** is enabled in the data widget +* Changes made through the Selection Helper immediately reflect in individual row and item selections +* Individual row and item selection changes update the Selection Helper state accordingly +* Selection state persists across pagination when **Keep selection** is enabled in the data widget ## Integration with Data Widgets @@ -85,8 +85,8 @@ The Selection Helper maintains real-time synchronization with the parent data wi The **Selection Helper** works with both **Gallery** and **Data Grid 2** selection methods: -- **Gallery**: Users can select via item clicks and the Selection Helper -- **Data Grid 2**: Users can select via both individual checkboxes and row clicks, and the Selection Helper +* **Gallery**: Users can select via item clicks and the Selection Helper +* **Data Grid 2**: Users can select via both individual checkboxes and row clicks, and the Selection Helper ## Common Use Cases diff --git a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md index 541c47b35f0..6839fbdc3a0 100755 --- a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md @@ -68,7 +68,7 @@ If you want to use specific resources, you should instead expose a new endpoint 9. Click **Back** to return to the **Details** page. 10. Click the **Ingestion Configuration** tab to set up your ingestion destination table. 11. Click **Create** to start setting up the Ingestion Configuration. - * **Target Database** – Name of the database for data ingestion + ***Target Database** – Name of the database for data ingestion * **Target Schema** – Target schema where all data will be ingested 12. Click **Save**. 13. Click the **Data Ingestion** tab, where you can start your data ingestion or set up a schedule. diff --git a/content/en/docs/marketplace/platform-supported-content/services/business-events/_index.md b/content/en/docs/marketplace/platform-supported-content/services/business-events/_index.md index ed1ba7b2844..ff27ea06dbc 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/business-events/_index.md +++ b/content/en/docs/marketplace/platform-supported-content/services/business-events/_index.md @@ -92,4 +92,4 @@ The Mendix Business Events service itself does not require a license, but it dep Read more to learn how to configure and deploy business events in the following documents: * [Business Event Configuration](/appstore/services/business-events-configuration/) -* [Deploy a Business Event](/appstore/services/business-events-deployment/) \ No newline at end of file +* [Deploy a Business Event](/appstore/services/business-events-deployment/) diff --git a/content/en/docs/marketplace/platform-supported-content/services/business-events/business-events-configuration.md b/content/en/docs/marketplace/platform-supported-content/services/business-events/business-events-configuration.md index 7d732311339..96cfd02500c 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/business-events/business-events-configuration.md +++ b/content/en/docs/marketplace/platform-supported-content/services/business-events/business-events-configuration.md @@ -122,4 +122,4 @@ Currently, Mendix does not support multiple subscribers to the same business eve ## Read More * [Deploy a Business Event](/appstore/services/business-events-deployment/) -* [Mendix Event Broker](/appstore/services/event-broker/) \ No newline at end of file +* [Mendix Event Broker](/appstore/services/event-broker/) diff --git a/content/en/docs/marketplace/platform-supported-content/services/business-events/business-events-deployment.md b/content/en/docs/marketplace/platform-supported-content/services/business-events/business-events-deployment.md index 37105a08696..b511b6ef6a5 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/business-events/business-events-deployment.md +++ b/content/en/docs/marketplace/platform-supported-content/services/business-events/business-events-deployment.md @@ -203,4 +203,4 @@ Below is an example of a Postgres service that you can add to your `docker-compo ## Read More * [Business Event Configuration](/appstore/services/business-events-configuration/) -* [Mendix Event Broker](/appstore/services/event-broker/) \ No newline at end of file +* [Mendix Event Broker](/appstore/services/event-broker/) diff --git a/content/en/docs/marketplace/platform-supported-content/services/event-broker.md b/content/en/docs/marketplace/platform-supported-content/services/event-broker.md index f2fca0dea26..22dd695806e 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/event-broker.md +++ b/content/en/docs/marketplace/platform-supported-content/services/event-broker.md @@ -485,7 +485,7 @@ To edit a bridge: **AWS S3** {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/edit-bridge/ebb_aws_s3_edit_mode.png" class="no-border" >}} -4. Once you have made your changes, you can: +1. Once you have made your changes, you can: * Click **Apply** to save and apply the changes. A confirmation message will indicate if the changes were successful. Changes to the event configuration take effect when applied. After applying changes, the bridge status will change to **Reconfiguring** and will return to **Running** once the reconfiguration is complete. * Click **Cancel** to exit editing mode without saving any changes. diff --git a/content/en/docs/private-platform/pmp-maia.md b/content/en/docs/private-platform/pmp-maia.md index e9c6d46704f..a9a57eba9bc 100644 --- a/content/en/docs/private-platform/pmp-maia.md +++ b/content/en/docs/private-platform/pmp-maia.md @@ -41,16 +41,16 @@ Generators: Starting in Private Mendix Platform 2.6, instead of usign the default Large Language Model, you can connect Maia to several different models of your choice. Currently this includes the following LLMs: * Anthropic - * Small text model - Claude Haiku 4.5 - * Large text model - Claude Opus 4.6 + * Small text model - Claude Haiku 4.5 + * Large text model - Claude Opus 4.6 * [AWS Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/models-regions.html) - * Small text model - Claude Haiku 4.5 - * Large text model - Claude Sonnet 4.5 - * Fallback model - Claude Sonnet 4 + * Small text model - Claude Haiku 4.5 + * Large text model - Claude Sonnet 4.5 + * Fallback model - Claude Sonnet 4 * [Azure](https://learn.microsoft.com/en-us/azure/ai-foundry/foundry-models/concepts/models-sold-directly-by-azure) - * o3-mini + * o3-mini * OpenAI - * GPT-5-Mini + * GPT-5-Mini ### Feature Comparison @@ -119,4 +119,4 @@ To configure Maia to use your own Large Language Model, perform the following st {{% alert color="info" %}} For AWS Bedrock Claude models, the region prefix is the same as for inference profile IDs, for example, `eu`. -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/private-platform/pmp-prerequisites.md b/content/en/docs/private-platform/pmp-prerequisites.md index d2e71853616..22d1d3e144a 100644 --- a/content/en/docs/private-platform/pmp-prerequisites.md +++ b/content/en/docs/private-platform/pmp-prerequisites.md @@ -127,15 +127,15 @@ For information about the infrastructure requirements, see [Supported Providers] Starting in Private Mendix Platform 2.6, instead of usign the default Large Language Model, you can connect [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/) to several different models of your choice. Currently this includes the following LLMs: * Anthropic - * Small text model - Claude Haiku 4.5 - * Large text model - Claude Opus 4.6 + * Small text model - Claude Haiku 4.5 + * Large text model - Claude Opus 4.6 * [AWS Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/models-regions.html) - * Small text model - Claude Haiku 4.5 - * Large text model - Claude Sonnet 4.5 - * Fallback model - Claude Sonnet 4 + * Small text model - Claude Haiku 4.5 + * Large text model - Claude Sonnet 4.5 + * Fallback model - Claude Sonnet 4 * [Azure](https://learn.microsoft.com/en-us/azure/ai-foundry/foundry-models/concepts/models-sold-directly-by-azure) - * o3-mini + * o3-mini * OpenAI - * GPT-5-Mini + * GPT-5-Mini - For more information, see [Maia in Private Mendix Platform](/private-mendix-platform/maia/). \ No newline at end of file + For more information, see [Maia in Private Mendix Platform](/private-mendix-platform/maia/). diff --git a/content/en/docs/private-platform/pmp-quickstart.md b/content/en/docs/private-platform/pmp-quickstart.md index 8d4987e51e9..42ba34d19fb 100644 --- a/content/en/docs/private-platform/pmp-quickstart.md +++ b/content/en/docs/private-platform/pmp-quickstart.md @@ -451,7 +451,7 @@ To install the Private Cloud components, perform the following steps: To allow other clusters to connect to Private Mendix Platform, you must expose the Interactor Bridge Service. Currently, the installer only supports using the generic Ingress template to expose the service. If you want to expose the Interactor Bridge with other method (for example, Openshift Route), contact the Private Mendix Platform team. {{% /alert %}} -10. Click **Review and Apply > Apply Configuration**. +1. Click **Review and Apply > Apply Configuration**. ### Uninstalling the Private Cloud Components diff --git a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/certificates-tab.md b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/certificates-tab.md index bcc81989174..db84caa4f51 100644 --- a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/certificates-tab.md +++ b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/certificates-tab.md @@ -49,4 +49,4 @@ When client and server are RFC-5746 compatible at a future point in time, this J For background information, see [Transport Layer Security (TLS) Renegotiation Issue Readme](https://www.oracle.com/technetwork/java/javase/documentation/tlsreadme2-176330.html). -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/dependencies-tab.md b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/dependencies-tab.md index 2e10097a498..bbd59f5cbe3 100644 --- a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/dependencies-tab.md +++ b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/dependencies-tab.md @@ -19,4 +19,4 @@ This shows all the managed dependencies in your app listed by package name. This ### Userlib Exclusions -This shows the libraries from the userlib directory and allows you to exclude them from deployment. Use this, for example, if there is an add-on module that ships with a different version of a library that is already in your userlib folder. \ No newline at end of file +This shows the libraries from the userlib directory and allows you to exclude them from deployment. Use this, for example, if there is an add-on module that ships with a different version of a library that is already in your userlib folder. diff --git a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/languages-tab.md b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/languages-tab.md index 744801b5d27..c727792169c 100644 --- a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/languages-tab.md +++ b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/languages-tab.md @@ -17,4 +17,4 @@ The **Default language** indicates the language that is used when a user has not This is the list of languages in which your application will be available for users. -For each language, you can configure whether to check that all mandatory texts have a value. The default language is always checked. If a language is not checked and certain texts are not translated in Studio Pro, the default language is used as fallback language. This means you can run your application even though you have only partially translated your interface into a new language. \ No newline at end of file +For each language, you can configure whether to check that all mandatory texts have a value. The default language is always checked. If a language is not checked and certain texts are not translated in Studio Pro, the default language is used as fallback language. This means you can run your application even though you have only partially translated your interface into a new language. diff --git a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/runtime-tab.md b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/runtime-tab.md index 630e0c85181..a00f009ba73 100644 --- a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/runtime-tab.md +++ b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/runtime-tab.md @@ -251,4 +251,4 @@ Default: *Yes* Choose between **PKIX (recommended)** and **SunX509 (for backwards compatibility)** as the Java validator and trust manager. According to [this JDK issue](https://bugs.openjdk.org/browse/JDK-8169745), the PKIX validator/trust manager supports richer extensions and features, and the use of SunX509 is discouraged. -Default: **SunX509 (for backwards compatibility)** \ No newline at end of file +Default: **SunX509 (for backwards compatibility)** diff --git a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/theme-tab.md b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/theme-tab.md index 303c6459c9c..a9bc12c7545 100644 --- a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/theme-tab.md +++ b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/theme-tab.md @@ -41,4 +41,4 @@ When a module contains styling (SCSS/CSS), be sure it is added to the compiled C You can set an explicit order in the theme settings (**App Settings** > **Theme**). This contains a list of all modules that are marked as UI resource modules, and allows you to set the explicit order in which they are added to the CSS file. Note that the lower a module is ordered in the list, the higher its precedence. For example, an app that uses a company theme module could be ordered as follows: -{{< figure src="/attachments/refguide/modeling/app-explorer/app/app-settings/theme-tab/app-theme-settings.png" alt="app theme settings" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/refguide/modeling/app-explorer/app/app-settings/theme-tab/app-theme-settings.png" alt="app theme settings" class="no-border" >}} diff --git a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/workflow-tab.md b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/workflow-tab.md index 675dcde48ec..4232751f49f 100644 --- a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/workflow-tab.md +++ b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/workflow-tab.md @@ -73,4 +73,4 @@ A microflow selected for this setting will start every time a workflow changes i #### User Task State Change {#user-task-state-change} -A microflow selected for this setting will start every time a user task changes its state, for example, when a user task is completed or paused. This setting is app-wide; you can override it by setting a workflow-specific microflow in [workflow properties](/refguide/workflow-properties/#events). \ No newline at end of file +A microflow selected for this setting will start every time a user task changes its state, for example, when a user task is completed or paused. This setting is app-wide; you can override it by setting a workflow-specific microflow in [workflow properties](/refguide/workflow-properties/#events). diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflow-element-common-properties.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflow-element-common-properties.md index c1e6f5559c1..9e992e3020a 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflow-element-common-properties.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflow-element-common-properties.md @@ -16,13 +16,13 @@ These are the common properties for microflows and nanoflows: {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflow-element-common-properties/microflow-element-common-properties.png" alt="Common properties in properties pane" width="300px" class="no-border" >}} -- [Introduction](#introduction) -- [Caption {#caption}](#caption) -- [Auto-Generate Caption {#auto-generate-caption}](#auto-generate-caption) -- [Background Color {#color}](#color) -- [Error Handling Type {#error-handling}](#error-handling) -- [Disabled {#disabled}](#disabled) -- [Read More](#read-more) +* [Introduction](#introduction) +* [Caption {#caption}](#caption) +* [Auto-Generate Caption {#auto-generate-caption}](#auto-generate-caption) +* [Background Color {#color}](#color) +* [Error Handling Type {#error-handling}](#error-handling) +* [Disabled {#disabled}](#disabled) +* [Read More](#read-more) ## Caption {#caption} diff --git a/content/en/docs/refguide/modeling/best-practices/dev-best-practices/app-setup.md b/content/en/docs/refguide/modeling/best-practices/dev-best-practices/app-setup.md index accb80aaf73..10826e54007 100644 --- a/content/en/docs/refguide/modeling/best-practices/dev-best-practices/app-setup.md +++ b/content/en/docs/refguide/modeling/best-practices/dev-best-practices/app-setup.md @@ -41,4 +41,4 @@ Always store secret information in a safe place. A safe place is the database. U You can also store [private constants](/refguide/configurations-tab/#constants) in configurations. These are encrypted and stored on your local machine so will not be shared with others. -Using either the default value of a constant or the project's shared configuration settings is unsafe. Both these places are readable by others and visible in the version management copies. \ No newline at end of file +Using either the default value of a constant or the project's shared configuration settings is unsafe. Both these places are readable by others and visible in the version management copies. diff --git a/content/en/docs/refguide/modeling/best-practices/dev-best-practices/naming-conventions.md b/content/en/docs/refguide/modeling/best-practices/dev-best-practices/naming-conventions.md index ecc91e327cf..cf5f50f2dc3 100644 --- a/content/en/docs/refguide/modeling/best-practices/dev-best-practices/naming-conventions.md +++ b/content/en/docs/refguide/modeling/best-practices/dev-best-practices/naming-conventions.md @@ -281,4 +281,4 @@ You can define the [home pages](/refguide/show-home-page/) per device and role i | Default home page | Mobile | Home_Phone_Default | | Role based home page | Desktop | Home_Desktop_{User role} | | Role based home page | Tablet | Home_Tablet_{User role} | -| Role based home page | Mobile | Home_Phone_{User role} | \ No newline at end of file +| Role based home page | Mobile | Home_Phone_{User role} | diff --git a/content/en/docs/refguide/runtime/date-and-time-handling/_index.md b/content/en/docs/refguide/runtime/date-and-time-handling/_index.md index 2dc3c05fdd5..a8389a75223 100644 --- a/content/en/docs/refguide/runtime/date-and-time-handling/_index.md +++ b/content/en/docs/refguide/runtime/date-and-time-handling/_index.md @@ -22,7 +22,7 @@ For brevity we will call these time zones user time, UTC, and server time. The server needs to know the time zone of each end-user. On startup, the browser reports both the current offset to UTC and, when available, a time zone identifier (for example, `Europe/Amsterdam`) from the underlying platform. When available, the runtime uses the identifier to properly handle DST for future and past dates. If no identifier is available, it falls back to the offset. You can explicitly set a time zone for each end-user, and that configured value takes precedence for server operations. -The `System` module contains the entity `TimeZone` which has an association with the `User` entity. `TimeZone` has three attributes: a code (based on the[ Olson database](https://en.wikipedia.org/wiki/Tz_database)), a description suitable for showing to the end-user (for example "(GMT-05:00) New York") and a raw offset that is using for sorting the list of time zones. +The `System` module contains the entity `TimeZone` which has an association with the `User` entity. `TimeZone` has three attributes: a code (based on the[Olson database](https://en.wikipedia.org/wiki/Tz_database)), a description suitable for showing to the end-user (for example "(GMT-05:00) New York") and a raw offset that is using for sorting the list of time zones. In the `Administration` module, the `Account_NewEdit` page adds a time zone selector to set the time zone of the end-user. By default, the `MyAccount` page does not have this selector. It is the administrator's task to correctly set the time zone. You can add it yourself if you want your end-users to be able to set their time zone. diff --git a/content/en/docs/refguide10/modeling/app-explorer/app/app-settings/_index.md b/content/en/docs/refguide10/modeling/app-explorer/app/app-settings/_index.md index 1ffbecb51d3..152504563d0 100644 --- a/content/en/docs/refguide10/modeling/app-explorer/app/app-settings/_index.md +++ b/content/en/docs/refguide10/modeling/app-explorer/app/app-settings/_index.md @@ -38,7 +38,6 @@ This setting enables the new React version of the Mendix Client. This React clie * **Yes**: Use the React client. In this mode, you will get consistency errors for incompatible widgets. * **Migration mode**: Use the React client and ignore incompatible widgets. Placeholders are displayed in the case of incompatible widgets. Recommended when trying out the new client. - ### Optimize Network Calls {#optimize-network-calls} If this option is enabled (**true** by default), Mendix analyzes every microflow that can be triggered from the client to minimize the number of objects required to be sent. This speeds up your app significantly. diff --git a/content/en/docs/refguide10/runtime/date-and-time-handling/_index.md b/content/en/docs/refguide10/runtime/date-and-time-handling/_index.md index 9d20f1ebcaa..f8f9e39ee3a 100644 --- a/content/en/docs/refguide10/runtime/date-and-time-handling/_index.md +++ b/content/en/docs/refguide10/runtime/date-and-time-handling/_index.md @@ -22,7 +22,7 @@ For brevity we will call these time zones user time, UTC, and server time. The server needs to know the time zone of each end-user. On startup, the browser reports both the current offset to UTC and, when available, a time zone identifier (for example, `Europe/Amsterdam`) from the underlying platform. When available, the runtime uses the identifier to properly handle DST for future and past dates. If no identifier is available, it falls back to the offset. You can explicitly set a time zone for each end-user, and that configured value takes precedence for server operations. -The `System` module contains the entity `TimeZone` which has an association with the `User` entity. `TimeZone` has three attributes: a code (based on the[ Olson database](https://en.wikipedia.org/wiki/Tz_database)), a description suitable for showing to the end-user (for example "(GMT-05:00) New York") and a raw offset that is using for sorting the list of time zones. +The `System` module contains the entity `TimeZone` which has an association with the `User` entity. `TimeZone` has three attributes: a code (based on the[Olson database](https://en.wikipedia.org/wiki/Tz_database)), a description suitable for showing to the end-user (for example "(GMT-05:00) New York") and a raw offset that is using for sorting the list of time zones. In the `Administration` module, the `Account_NewEdit` page adds a time zone selector to set the time zone of the end-user. By default, the `MyAccount` page does not have this selector. It is the administrator's task to correctly set the time zone. You can add it yourself if you want your end-users to be able to set their time zone. @@ -70,4 +70,4 @@ For more information, see the [Localize](/refguide10/attributes/#localize) secti ## Tokens -Tokens for referring to specific moments like `[%BeginOfCurrentDay%]` refer to the end-user time zone. Where it makes sense, a UTC versions of the token is available, for example, `[%BeginOfCurrentDayUTC%]`. \ No newline at end of file +Tokens for referring to specific moments like `[%BeginOfCurrentDay%]` refer to the end-user time zone. Where it makes sense, a UTC versions of the token is available, for example, `[%BeginOfCurrentDayUTC%]`. diff --git a/content/en/docs/refguide9/runtime/date-and-time-handling/_index.md b/content/en/docs/refguide9/runtime/date-and-time-handling/_index.md index 8af53479b85..957412e075c 100644 --- a/content/en/docs/refguide9/runtime/date-and-time-handling/_index.md +++ b/content/en/docs/refguide9/runtime/date-and-time-handling/_index.md @@ -22,7 +22,7 @@ For brevity we will call these time zones user time, UTC, and server time. The server needs to know the time zone of each end-user. On startup, the browser reports both the current offset to UTC and, when available, a time zone identifier (for example, `Europe/Amsterdam`) from the underlying platform. When available, the runtime uses the identifier to properly handle DST for future and past dates. If no identifier is available, it falls back to the offset. You can explicitly set a time zone for each end-user, and that configured value takes precedence for server operations. -The `System` module contains the entity `TimeZone` which has an association with the `User` entity. `TimeZone` has three attributes: a code (based on the[ Olson database](https://en.wikipedia.org/wiki/Tz_database)), a description suitable for showing to the end-user (for example "(GMT-05:00) New York") and a raw offset that is using for sorting the list of time zones. +The `System` module contains the entity `TimeZone` which has an association with the `User` entity. `TimeZone` has three attributes: a code (based on the[Olson database](https://en.wikipedia.org/wiki/Tz_database)), a description suitable for showing to the end-user (for example "(GMT-05:00) New York") and a raw offset that is using for sorting the list of time zones. In the `Administration` module, the `Account_NewEdit` page adds a time zone selector to set the time zone of the end-user. By default, the `MyAccount` page does not have this selector. It is the administrator's task to correctly set the time zone. You can add it yourself if you want your end-users to be able to set their time zone. @@ -70,4 +70,4 @@ For more information, see the [Localize](/refguide9/attributes/#localize) sectio ## Tokens -Tokens for referring to specific moments like `[%BeginOfCurrentDay%]` refer to the end-user time zone. Where it makes sense, a UTC versions of the token is available, for example, `[%BeginOfCurrentDayUTC%]`. \ No newline at end of file +Tokens for referring to specific moments like `[%BeginOfCurrentDay%]` refer to the end-user time zone. Where it makes sense, a UTC versions of the token is available, for example, `[%BeginOfCurrentDayUTC%]`. diff --git a/content/en/docs/releasenotes/catalog/2021.md b/content/en/docs/releasenotes/catalog/2021.md index c0e9ed217a1..8de2ce03935 100644 --- a/content/en/docs/releasenotes/catalog/2021.md +++ b/content/en/docs/releasenotes/catalog/2021.md @@ -351,4 +351,4 @@ The [Data Hub Transform API](https://datahub-spec.s3.eu-central-1.amazonaws.com/ #### Improvements -* There have been several improvements in the Data Hub user interface. \ No newline at end of file +* There have been several improvements in the Data Hub user interface. diff --git a/content/en/docs/releasenotes/catalog/2022.md b/content/en/docs/releasenotes/catalog/2022.md index f81d98c01c4..52ffe6063d6 100644 --- a/content/en/docs/releasenotes/catalog/2022.md +++ b/content/en/docs/releasenotes/catalog/2022.md @@ -421,4 +421,4 @@ numberless_headings: true #### Fixes -* We updated the Log4j dependency to 2.17.1, which addresses [CVE-2021-44832](https://cert-portal.siemens.com/productcert/pdf/ssa-784507.pdf). \ No newline at end of file +* We updated the Log4j dependency to 2.17.1, which addresses [CVE-2021-44832](https://cert-portal.siemens.com/productcert/pdf/ssa-784507.pdf). diff --git a/content/en/docs/releasenotes/catalog/2023.md b/content/en/docs/releasenotes/catalog/2023.md index 319b939174b..f87e3eecb74 100644 --- a/content/en/docs/releasenotes/catalog/2023.md +++ b/content/en/docs/releasenotes/catalog/2023.md @@ -268,4 +268,4 @@ numberless_headings: true #### Improvements -* You can now add [authentication](/catalog/register/register-data/#authentication) details to a data source. Click **Edit** on the data source and then click the **Authentication** tab. See the [Selecting an Authentication Method](/catalog/register/register-data/#authentication) section of *Register OData Resources in the Catalog* for more information on the authentication types. \ No newline at end of file +* You can now add [authentication](/catalog/register/register-data/#authentication) details to a data source. Click **Edit** on the data source and then click the **Authentication** tab. See the [Selecting an Authentication Method](/catalog/register/register-data/#authentication) section of *Register OData Resources in the Catalog* for more information on the authentication types. diff --git a/content/en/docs/releasenotes/catalog/2024.md b/content/en/docs/releasenotes/catalog/2024.md index 73437a02cee..f0356966891 100644 --- a/content/en/docs/releasenotes/catalog/2024.md +++ b/content/en/docs/releasenotes/catalog/2024.md @@ -240,4 +240,4 @@ numberless_headings: true #### Improvement -* Users that are not an administrator or curator can now view deeplinks to undiscoverable services. \ No newline at end of file +* Users that are not an administrator or curator can now view deeplinks to undiscoverable services. diff --git a/content/en/docs/releasenotes/catalog/2025.md b/content/en/docs/releasenotes/catalog/2025.md index ee8ede6372c..9bb3b774040 100644 --- a/content/en/docs/releasenotes/catalog/2025.md +++ b/content/en/docs/releasenotes/catalog/2025.md @@ -42,4 +42,4 @@ numberless_headings: true #### Fixes -* We fixed an issue where the search results were not always showing the latest information. \ No newline at end of file +* We fixed an issue where the search results were not always showing the latest information. diff --git a/content/en/docs/releasenotes/catalog/2026.md b/content/en/docs/releasenotes/catalog/2026.md index 778b1de6e6a..ebc2f55386e 100644 --- a/content/en/docs/releasenotes/catalog/2026.md +++ b/content/en/docs/releasenotes/catalog/2026.md @@ -14,4 +14,4 @@ numberless_headings: true #### Fixes -* We fixed an issue where a CloudEvent containing a consumed OData service without a specified constant failed to register in the Catalog. \ No newline at end of file +* We fixed an issue where a CloudEvent containing a consumed OData service without a specified constant failed to register in the Catalog. diff --git a/content/en/docs/releasenotes/catalog/_index.md b/content/en/docs/releasenotes/catalog/_index.md index 1301998f792..562fb2550e2 100644 --- a/content/en/docs/releasenotes/catalog/_index.md +++ b/content/en/docs/releasenotes/catalog/_index.md @@ -22,4 +22,4 @@ Click the link corresponding to the year for which you want to read release note * [2023](/releasenotes/catalog/2023/) * [2022](/releasenotes/catalog/2022/) * [2021](/releasenotes/catalog/2021/) -* [2020](/releasenotes/catalog/2020/) \ No newline at end of file +* [2020](/releasenotes/catalog/2020/) diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md index dafcd7d106e..1cb3a193412 100644 --- a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md +++ b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md @@ -11,12 +11,12 @@ description: "Native Template 14" ### Improvements -- We changed iOS Keychain item accessibility to **After First Unlock** for encrypted storage and persisted session cookies. +* We changed iOS Keychain item accessibility to **After First Unlock** for encrypted storage and persisted session cookies. ### Fixes -- We fixed an iOS crash in encrypted storage by correcting native error handling. Now Keychain failures no longer trigger an unrecognized selector abort. -- We added a mandatory, one-time Keychain migration to update existing stored items. For compatibility, this Native Template version still works with older Studio Pro 10.24.x, but migration support requires a version of Studio Pro 10.24.16 or newer, as well as a new iOS app build and rollout. Without migration, the original Keychain accessibility issue can still occur, although improved error handling reduces crash severity. +* We fixed an iOS crash in encrypted storage by correcting native error handling. Now Keychain failures no longer trigger an unrecognized selector abort. +* We added a mandatory, one-time Keychain migration to update existing stored items. For compatibility, this Native Template version still works with older Studio Pro 10.24.x, but migration support requires a version of Studio Pro 10.24.16 or newer, as well as a new iOS app build and rollout. Without migration, the original Keychain accessibility issue can still occur, although improved error handling reduces crash severity. ## 14.1.11 {#1421} diff --git a/content/en/docs/releasenotes/studio-pro/10/10.24.md b/content/en/docs/releasenotes/studio-pro/10/10.24.md index 0509cf53fea..3a358e12d7d 100644 --- a/content/en/docs/releasenotes/studio-pro/10/10.24.md +++ b/content/en/docs/releasenotes/studio-pro/10/10.24.md @@ -18,23 +18,23 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for ### Improvements -- We have improved the performance of session cleanup. +* We have improved the performance of session cleanup. ### Fixes -- We fixed an issue where System.UserRole's **Description** attribute was not readable. (Ticket 259857) -- We fixed an issue where the short revision hash of the commit was being sent when deploying a package. (Ticket 264621, Ticket 266012) -- We fixed an issue in offline apps that could result in errors like "[Synchronization] SQLiteError: table mx10414574138294561$_guidToTable has no column named inaccessibleAttrs" by ensuring database migrations happen properly for all users in the client database. (Tickets 264910, 265393, 269740) -- In the logic editors, we fixed an issue where extracted microflows did not contain all the expected parameters for a newly-created activity. (Ticket 265542) -- We fixed an issue with the [tab container](/refguide10/tab-container/) widget. It would reset to the first tab when returning to the page, causing data sources to reload unnecessarily and other tabs to be blocked. (Tickets 266083, 266090, 267249) -- We fixed an issue where the last attributes were truncated in entity properties dialog boxes. (Tickets 266554, 260953, 256106, 251278, 255882) -- We fixed an issue where an import mapping would not read JSON attribute values when a JSON attribute was preceded by another attribute with an attribute name that is a prefix (for example `StatusId` and `Status`). We also improved how JSON objects were read when one object name was a prefix of another object name. (Ticket 266571) -- In the logic editors, we fixed an issue where a **Show Message** activity had an empty caption after initial loading of the microflow. (Ticket 268024). -- We fixed an issue that caused setting the image of a building block to show an error dialog instead of resizing the image. (Ticket 268856) -- We fixed an issue in Maia chat where it crashed if the **Studio Pro Version** attribute was missing in a reference. -- We fixed scenarios in Android where navigating fields of a data view (of different types) would not be possible using an external keyboard. -- We now parse `StdOut` and `StdError` streams separately when calling git process. This improves the stability of git operations. -- We fixed an issue during local development where system texts would not be updated in the application when hot-reloading. They are now correctly updated without the need to fully restart the server. +* We fixed an issue where System.UserRole's **Description** attribute was not readable. (Ticket 259857) +* We fixed an issue where the short revision hash of the commit was being sent when deploying a package. (Ticket 264621, Ticket 266012) +* We fixed an issue in offline apps that could result in errors like "[Synchronization] SQLiteError: table mx10414574138294561$_guidToTable has no column named inaccessibleAttrs" by ensuring database migrations happen properly for all users in the client database. (Tickets 264910, 265393, 269740) +* In the logic editors, we fixed an issue where extracted microflows did not contain all the expected parameters for a newly-created activity. (Ticket 265542) +* We fixed an issue with the [tab container](/refguide10/tab-container/) widget. It would reset to the first tab when returning to the page, causing data sources to reload unnecessarily and other tabs to be blocked. (Tickets 266083, 266090, 267249) +* We fixed an issue where the last attributes were truncated in entity properties dialog boxes. (Tickets 266554, 260953, 256106, 251278, 255882) +* We fixed an issue where an import mapping would not read JSON attribute values when a JSON attribute was preceded by another attribute with an attribute name that is a prefix (for example `StatusId` and `Status`). We also improved how JSON objects were read when one object name was a prefix of another object name. (Ticket 266571) +* In the logic editors, we fixed an issue where a **Show Message** activity had an empty caption after initial loading of the microflow. (Ticket 268024). +* We fixed an issue that caused setting the image of a building block to show an error dialog instead of resizing the image. (Ticket 268856) +* We fixed an issue in Maia chat where it crashed if the **Studio Pro Version** attribute was missing in a reference. +* We fixed scenarios in Android where navigating fields of a data view (of different types) would not be possible using an external keyboard. +* We now parse `StdOut` and `StdError` streams separately when calling git process. This improves the stability of git operations. +* We fixed an issue during local development where system texts would not be updated in the application when hot-reloading. They are now correctly updated without the need to fully restart the server. ## 10.24.14 {#102414} diff --git a/content/en/docs/releasenotes/studio-pro/11/11.3.md b/content/en/docs/releasenotes/studio-pro/11/11.3.md index 3c825716a2c..322b643f546 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.3.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.3.md @@ -13,7 +13,6 @@ weight: 97 For more guidance, see the official [11.3 Mendix release blog](https://www.mendix.com/blog/release-11-3-from-workflows-to-ai-whats-new-this-month/). - ### New Features * We introduced a setting in the **Advanced** tab of the **Preferences** dialog to enable starting Studio Pro in Extension Development Mode, so users do not need to provide the feature flag themselves. diff --git a/content/en/docs/workstation/wks-batch-registration.md b/content/en/docs/workstation/wks-batch-registration.md index d81cf945da6..013edd5bd0a 100644 --- a/content/en/docs/workstation/wks-batch-registration.md +++ b/content/en/docs/workstation/wks-batch-registration.md @@ -76,5 +76,4 @@ Instead of reassigning computers to stations manually after the bulk import, you You can also specify this name during station creation. {{% /alert %}} - -Computers with this name are automatically assigned to the station during the bulk import. \ No newline at end of file +Computers with this name are automatically assigned to the station during the bulk import. diff --git a/content/en/docs/workstation/wks-message-syntax.md b/content/en/docs/workstation/wks-message-syntax.md index 3710f0e19b0..037436e5b88 100644 --- a/content/en/docs/workstation/wks-message-syntax.md +++ b/content/en/docs/workstation/wks-message-syntax.md @@ -37,6 +37,7 @@ Before sending messages to the File Device, review the following points: * Delimiter - The `#` character is used as a delimiter within messages. Paths and data may not contain the `#` character. * Case sensitivity - File and directory paths may be case-sensitive depending on the underlying operating system. For example, Linux paths are typically case-sensitive, while Windows paths are not.   + ### Message * `0#Path` - Initiate watching for changes in the specified `Path`. If `Path` is a directory, the device will watch for changes within that directory (creation, deletion, renaming, or modification of files/subdirectories). If `Path` is a file, the device will watch for changes to that specific file (modification, deletion, or renaming).