From c870d53b3f5f3d45a9469f1d0719c696b448e1d1 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 1 Apr 2026 20:38:14 +0000 Subject: [PATCH] Run markdownlint-cli2 on docs to find (and correct) linting errors. --- content/en/docs/academy/_index.md | 1 - .../pluggable-widgets-property-types.md | 8 +- .../monitoring-with-apm/splunk-metrics.md | 3 +- .../modules/global-inbox.md | 2 +- .../modules/snowflake/mendix-data-loader.md | 2 +- .../snowflake/snowflake-ai-data-connector.md | 2 +- .../odata-services/build-odata-apis.md | 1 - .../menus/version-control-menu/_index.md | 2 +- .../version-control-menu/commit-dialog.md | 2 +- .../download-from-version-control-dialog.md | 2 +- .../version-control-menu/history-dialog.md | 2 +- .../version-control-menu/merge-dialog.md | 2 +- .../xpath-constraint-functions/_index.md | 2 +- .../runtime/custom-settings/_index.md | 2 +- content/en/docs/refguide/testing/_index.md | 2 +- .../configure/version-control-enable.md | 2 +- .../deploy-external.md | 2 - .../peer-review.md | 2 +- .../push-pull.md | 2 +- .../reverting-changes.md | 2 +- .../version-control-troubleshooting/_index.md | 2 +- .../runtime/custom-settings/_index.md | 2 +- content/en/docs/refguide10/testing/_index.md | 2 +- content/en/docs/refguide9/general/install.md | 1 + .../nt-studio-pro-10-parent/nt-14-rn.md | 2 +- .../docs/releasenotes/studio-pro/10/10.24.md | 40 ++--- .../docs/releasenotes/studio-pro/11/11.6.md | 33 +++-- .../docs/releasenotes/studio-pro/11/11.8.md | 137 +++++++++--------- .../en/docs/releasenotes/studio-pro/9/9.24.md | 16 +- content/en/docs/workstation/wks-import.md | 2 +- .../en/docs/workstation/wks-message-syntax.md | 1 - 31 files changed, 140 insertions(+), 143 deletions(-) diff --git a/content/en/docs/academy/_index.md b/content/en/docs/academy/_index.md index eeab0f73d76..c38eb9565c9 100755 --- a/content/en/docs/academy/_index.md +++ b/content/en/docs/academy/_index.md @@ -44,4 +44,3 @@ Refer to the following pages for details on Mendix Academy exams: * [Purchasing Mendix Exam Seats](/academy/purchasing-exams/) * [Managing Exam Seats](/academy/purchasing-exams/manage-exam-seats/) * [Managing Exam Admins](/academy/purchasing-exams/manage-exam-admins/) - diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md index 4cbc4147f12..599c78ae64e 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md @@ -277,11 +277,11 @@ The user can use the optional attribute [`allowUpload`](#allow-upload) with defa #### XML Attributes -| Attribute | Required | Attribute Type | Description | +| Attribute | Required | Attribute Type | Description | |---------------|----------|----------------|-----------------------------------------------------------------------| -| `type` | Yes | String | Must be `image` | -| `key` | Yes | String | See [key](#key) | -| `required` | No | Boolean | Whether the property must be specified by the user, `true` by default | +| `type` | Yes | String | Must be `image` | +| `key` | Yes | String | See [key](#key) | +| `required` | No | Boolean | Whether the property must be specified by the user, `true` by default | | `allowUpload` | No | Boolean | See [allowUpload](#allow-upload) | #### Studio Pro UI diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md b/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md index feb7e11457c..fa9cb971f6e 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md @@ -58,8 +58,7 @@ To send your runtime information to Splunk Cloud Platform, you need to set it up {{% /alert %}} - -5. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment. +1. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment. {{% alert color="warning" %}}The first time you set up the Splunk Cloud Platform integration, you must redeploy your app and then restart it. Just restarting the app is not sufficient because additional dependencies need to be included.{{% /alert %}} diff --git a/content/en/docs/marketplace/platform-supported-content/modules/global-inbox.md b/content/en/docs/marketplace/platform-supported-content/modules/global-inbox.md index 5f369a68027..7ca96ae377e 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/global-inbox.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/global-inbox.md @@ -140,4 +140,4 @@ Any user that can see a task in Publisher Application can see the same task in t * **Global Inbox** does not support [Workflow Groups](/refguide/workflow-groups/) at the moment. This will be introduced at a later stage. * The beta version of **Global Inbox** has limited support for error handling. Any exceptions that occur in a microflow after updating a user task (or other Workflow-related entity) in the same microflow (for example, updating the targeted users or due date) might result in data becoming out of sync. This is a temporary limitation that will be resolved in an upcoming version. -* Workflows and tasks that are modeled in the same app that includes the Global Inbox module are NOT available in the Global Inbox. The Global Inbox app only consumes and displays workflow instances from other Mendix applications. \ No newline at end of file +* Workflows and tasks that are modeled in the same app that includes the Global Inbox module are NOT available in the Global Inbox. The Global Inbox app only consumes and displays workflow instances from other Mendix applications. 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 2971d5fce00..c803f98a717 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/modules/snowflake/snowflake-ai-data-connector.md b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-ai-data-connector.md index 631dc120bff..a6aa099539b 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-ai-data-connector.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-ai-data-connector.md @@ -315,7 +315,7 @@ To configure your Mendix app for Snowflake Cortex Analyst, perform the following {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-ai-data-connector/CortexAnalystRequestExample.png" >}} - ## Configuring Snowflake Cortex Search {#cortex-search} +## Configuring Snowflake Cortex Search {#cortex-search} Snowflake Cortex Search is a fully-managed, ML-powered Snowflake Cortex feature that helps you retrieve data relevant to a prompt to help an LLM generate informed answers (Retrieval Augmented Generation). diff --git a/content/en/docs/refguide/modeling/integration/odata-services/build-odata-apis.md b/content/en/docs/refguide/modeling/integration/odata-services/build-odata-apis.md index a73e90b187c..ff66347be4a 100644 --- a/content/en/docs/refguide/modeling/integration/odata-services/build-odata-apis.md +++ b/content/en/docs/refguide/modeling/integration/odata-services/build-odata-apis.md @@ -505,7 +505,6 @@ You can generate and reuse generated validation microflows. The following exampl } ``` - ### Deleting Data Deleting is provided using the `DELETE` operation. See the following `DELETE` request: diff --git a/content/en/docs/refguide/modeling/menus/version-control-menu/_index.md b/content/en/docs/refguide/modeling/menus/version-control-menu/_index.md index ed71e9ebaee..fb962212272 100644 --- a/content/en/docs/refguide/modeling/menus/version-control-menu/_index.md +++ b/content/en/docs/refguide/modeling/menus/version-control-menu/_index.md @@ -76,4 +76,4 @@ The **Add Snapshot of Data** option creates a snapshot of the built-in database * [Studio Pro Overview](/refguide/studio-pro-overview/) * [Version Control](/refguide/version-control/) -* [Pulling, Committing, and Pushing](/refguide/pushing-pulling/) \ No newline at end of file +* [Pulling, Committing, and Pushing](/refguide/pushing-pulling/) diff --git a/content/en/docs/refguide/modeling/menus/version-control-menu/commit-dialog.md b/content/en/docs/refguide/modeling/menus/version-control-menu/commit-dialog.md index 8d5e1eef8ff..6dd821e9dcd 100644 --- a/content/en/docs/refguide/modeling/menus/version-control-menu/commit-dialog.md +++ b/content/en/docs/refguide/modeling/menus/version-control-menu/commit-dialog.md @@ -79,4 +79,4 @@ If any synchronization fails during this step, you are asked if the commit shoul ## Read More -* [Pulling, Committing, and Pushing](/refguide/pushing-pulling/) \ No newline at end of file +* [Pulling, Committing, and Pushing](/refguide/pushing-pulling/) diff --git a/content/en/docs/refguide/modeling/menus/version-control-menu/download-from-version-control-dialog.md b/content/en/docs/refguide/modeling/menus/version-control-menu/download-from-version-control-dialog.md index 78abe2d7647..fb29d7b16a6 100644 --- a/content/en/docs/refguide/modeling/menus/version-control-menu/download-from-version-control-dialog.md +++ b/content/en/docs/refguide/modeling/menus/version-control-menu/download-from-version-control-dialog.md @@ -53,4 +53,4 @@ Choose the **App directory** to which want to download the app. The suggested na ## Read More * [Enabling Version Control for Your App](/refguide/version-control/enable/) -* [Optional: Working with Private Git](/refguide/on-premises-git/) \ No newline at end of file +* [Optional: Working with Private Git](/refguide/on-premises-git/) diff --git a/content/en/docs/refguide/modeling/menus/version-control-menu/history-dialog.md b/content/en/docs/refguide/modeling/menus/version-control-menu/history-dialog.md index 9887315abeb..1a95f2e9aa8 100644 --- a/content/en/docs/refguide/modeling/menus/version-control-menu/history-dialog.md +++ b/content/en/docs/refguide/modeling/menus/version-control-menu/history-dialog.md @@ -95,4 +95,4 @@ This tab shows a list of stories that are related to the changes. * [Version Control](/refguide/version-control/) * [Stories Pane](/refguide/stories-pane/) -* [Using Version Control History](/refguide/version-control-using-history/) \ No newline at end of file +* [Using Version Control History](/refguide/version-control-using-history/) diff --git a/content/en/docs/refguide/modeling/menus/version-control-menu/merge-dialog.md b/content/en/docs/refguide/modeling/menus/version-control-menu/merge-dialog.md index 67236b70aa9..ea79a7df304 100644 --- a/content/en/docs/refguide/modeling/menus/version-control-menu/merge-dialog.md +++ b/content/en/docs/refguide/modeling/menus/version-control-menu/merge-dialog.md @@ -64,4 +64,4 @@ Choose the branch line that you want to merge. It is not necessary to select ind ## Read More * [Pulling, Committing, and Pushing](/refguide/pushing-pulling/) -* [Combining Changes and Resolving Conflicts](/refguide/resolving-conflicts/) \ No newline at end of file +* [Combining Changes and Resolving Conflicts](/refguide/resolving-conflicts/) diff --git a/content/en/docs/refguide/modeling/xpath/xpath-constraints/xpath-constraint-functions/_index.md b/content/en/docs/refguide/modeling/xpath/xpath-constraints/xpath-constraint-functions/_index.md index 93914978f80..30a60e894a3 100644 --- a/content/en/docs/refguide/modeling/xpath/xpath-constraints/xpath-constraint-functions/_index.md +++ b/content/en/docs/refguide/modeling/xpath/xpath-constraints/xpath-constraint-functions/_index.md @@ -26,4 +26,4 @@ The following pages describe the functions that can be executed within constrain {{% alert color="info" %}} In all these functions, the attribute in the example is just the name of the attribute, for example `Name`. This is for clarity. However, the attribute can also contain the path to the attribute, for example `Sales.Order_Customer/Sales.Customer/Name`. -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/refguide/runtime/custom-settings/_index.md b/content/en/docs/refguide/runtime/custom-settings/_index.md index 1a5f48d8766..a0dfff94d27 100644 --- a/content/en/docs/refguide/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide/runtime/custom-settings/_index.md @@ -289,7 +289,7 @@ The settings below influence the behavior of the Mendix web client. | com.mendix.webui.FeedbackSizeWarningThreshold | A warning is logged when the feedback size exceeds the threshold. Feedback is sent from server to client to instruct (for example, to refresh objects or to open a page). They are serialized as "instructions" in the server response. If there are too many instructions, this can have performance implications, as they all have to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. | 5000 | | com.mendix.webui.StateSizeWarningThreshold | A warning is logged when the state size exceeds the threshold. The state consists of changes in objects and of objects not committed to the database (yet). If there is too much state, this will have performance implications, as the whole state has to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. | 100 | | com.mendix.webui.CommittedObjectsThreshold | The threshold controls how much data is sent back to the client after executing a microflow. By default, we send back full objects when they are changed or committed. When this threshold is reached, only object GUIDs are sent back instead so that the client knows about the changes while the amount of data sent over the network is reduced. The client will then retrieve the objects later on, if needed. | 100 | -| MaxRetrieveAmount | The maximum number of objects the client is allowed to retrieve by list widgets using database datasource runtime operation.
When requesting more objects than allowed, the runtime will enforce the `MaxRetrieveAmount` by setting a limit on the query and will log the following warning: `A retrieve action requested more objects than allowed by the `MaxRetrieveAmount` runtime setting. Amount requested: (...), MaxRetrieveAmount: (...).`
*This setting was introduced in Mendix version 11.8.0 and 11.6.5 MTS* | | +| MaxRetrieveAmount | The maximum number of objects the client is allowed to retrieve by list widgets using database datasource runtime operation.
When requesting more objects than allowed, the runtime will enforce the `MaxRetrieveAmount` by setting a limit on the query and will log the following warning: `A retrieve action requested more objects than allowed by the`MaxRetrieveAmount`runtime setting. Amount requested: (...), MaxRetrieveAmount: (...).`
*This setting was introduced in Mendix version 11.8.0 and 11.6.5 MTS* | | ## Metrics Settings{#metrics-settings} diff --git a/content/en/docs/refguide/testing/_index.md b/content/en/docs/refguide/testing/_index.md index e0cf0363698..a96f9647a15 100644 --- a/content/en/docs/refguide/testing/_index.md +++ b/content/en/docs/refguide/testing/_index.md @@ -80,4 +80,4 @@ Performance testing involves unit-level performance checks for critical microflo You can use the following offerings to help with this test type: -* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/). \ No newline at end of file +* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/). diff --git a/content/en/docs/refguide/version-control/configure/version-control-enable.md b/content/en/docs/refguide/version-control/configure/version-control-enable.md index 9e68beb6dd6..1389ca2554f 100644 --- a/content/en/docs/refguide/version-control/configure/version-control-enable.md +++ b/content/en/docs/refguide/version-control/configure/version-control-enable.md @@ -44,4 +44,4 @@ If version control was disabled during the app creation, you can enable it by pe 1. In Studio Pro, open the [Version Control menu](/refguide/upload-to-version-control-dialog/). 2. Click **Upload to Version Control Server**. -3. Select the server where you want to store the app. You can also create a new server. \ No newline at end of file +3. Select the server where you want to store the app. You can also create a new server. diff --git a/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/deploy-external.md b/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/deploy-external.md index 43b9a453f04..038e57d0b44 100644 --- a/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/deploy-external.md +++ b/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/deploy-external.md @@ -76,5 +76,3 @@ git fetch --depth 1 origin # reset this repository's master branch to the commit of interest git reset --hard FETCH_HEAD ``` - - diff --git a/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/peer-review.md b/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/peer-review.md index c17ef786f2c..655e5636b10 100644 --- a/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/peer-review.md +++ b/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/peer-review.md @@ -25,4 +25,4 @@ The [Name and Email settings](/refguide/preferences-dialog/#name) can be adjuste Select a revision to see additional details, such as related stories, changed documents, Studio Pro version, and changes on disk. Icons summarize the kinds of changes that happened in the app. -{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/history-dialog/revisions.png" class="no-border" >}} \ No newline at end of file +{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/history-dialog/revisions.png" class="no-border" >}} diff --git a/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/push-pull.md b/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/push-pull.md index ec0ce1e7fb6..8f89bc79268 100644 --- a/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/push-pull.md +++ b/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/push-pull.md @@ -154,4 +154,4 @@ If your team is committing often, you then should pull often. Frequent pulling h ## Read More -* [Mx Command-Line Tool: Merging and Diffing Commands](/refguide/mx-command-line-tool/#merging-and-diffing-commands) \ No newline at end of file +* [Mx Command-Line Tool: Merging and Diffing Commands](/refguide/mx-command-line-tool/#merging-and-diffing-commands) diff --git a/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/reverting-changes.md b/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/reverting-changes.md index 809dfad7780..abe8fa0d61f 100644 --- a/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/reverting-changes.md +++ b/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/reverting-changes.md @@ -45,4 +45,4 @@ Reverting changes is done with one commit at a time. If you want to revert multi You can also revert a commit where another branch was merged into the current branch. Reverting a merge removes the changes introduced by that merge, making it appear as if they never happened. For example, if the merge added a new page, reverting it will remove the page locally. -Just like with a normal merge, conflicts can occur when reverting a merge. For example, if later commits change the new page, the reverse merge will result in a conflict. Once you resolved the conflict, you can commit the changes and push them to the remote repository. \ No newline at end of file +Just like with a normal merge, conflicts can occur when reverting a merge. For example, if later commits change the new page, the reverse merge will result in a conflict. Once you resolved the conflict, you can commit the changes and push them to the remote repository. diff --git a/content/en/docs/refguide/version-control/version-control-troubleshooting/_index.md b/content/en/docs/refguide/version-control/version-control-troubleshooting/_index.md index e34cb799ed4..5006de94e73 100644 --- a/content/en/docs/refguide/version-control/version-control-troubleshooting/_index.md +++ b/content/en/docs/refguide/version-control/version-control-troubleshooting/_index.md @@ -208,4 +208,4 @@ To solve this issue, perform the following steps: 2. Abort the current operation in Studio Pro. 3. Retry the operation. -## Read More \ No newline at end of file +## Read More diff --git a/content/en/docs/refguide10/runtime/custom-settings/_index.md b/content/en/docs/refguide10/runtime/custom-settings/_index.md index a85b5ae2031..248a2c6ff4e 100644 --- a/content/en/docs/refguide10/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide10/runtime/custom-settings/_index.md @@ -282,7 +282,7 @@ The settings below influence the behavior of the Mendix web client. | com.mendix.webui.FeedbackSizeWarningThreshold | A warning is logged when the feedback size exceeds the threshold. Feedback is sent from server to client to instruct (for example, to refresh objects or to open a page). They are serialized as "instructions" in the server response. If there are too many instructions, this can have performance implications, as they all have to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. | 5000 | | com.mendix.webui.StateSizeWarningThreshold | A warning is logged when the state size exceeds the threshold. The state consists of changes in objects and of objects not committed to the database (yet). If there is too much state, this will have performance implications, as the whole state has to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. | 100 | | com.mendix.webui.CommittedObjectsThreshold | The threshold controls how much data is sent back to the client after executing a microflow. By default, we send back full objects when they are changed or committed. When this threshold is reached, only object GUIDs are sent back instead so that the client knows about the changes while the amount of data sent over the network is reduced. The client will then retrieve the objects later on, if needed. | 100 | -| MaxRetrieveAmount | The maximum number of objects the client is allowed to retrieve by list widgets using database datasource runtime operation.
When requesting more objects than allowed, the runtime will enforce the `MaxRetrieveAmount` by setting a limit on the query and will log the following warning: `A retrieve action requested more objects than allowed by the `MaxRetrieveAmount` runtime setting. Amount requested: (...), MaxRetrieveAmount: (...).`
*This setting was introduced in Mendix version 10.24.16* | | +| MaxRetrieveAmount | The maximum number of objects the client is allowed to retrieve by list widgets using database datasource runtime operation.
When requesting more objects than allowed, the runtime will enforce the `MaxRetrieveAmount` by setting a limit on the query and will log the following warning: `A retrieve action requested more objects than allowed by the`MaxRetrieveAmount`runtime setting. Amount requested: (...), MaxRetrieveAmount: (...).`
*This setting was introduced in Mendix version 10.24.16* | | ## Metrics Settings{#metrics-settings} diff --git a/content/en/docs/refguide10/testing/_index.md b/content/en/docs/refguide10/testing/_index.md index b4c0c139b8f..069f2ba356a 100644 --- a/content/en/docs/refguide10/testing/_index.md +++ b/content/en/docs/refguide10/testing/_index.md @@ -80,4 +80,4 @@ Performance testing involves unit-level performance checks for critical microflo You can use the following offerings to help with this test type: -* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/). \ No newline at end of file +* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/). diff --git a/content/en/docs/refguide9/general/install.md b/content/en/docs/refguide9/general/install.md index 3833dbfe28e..8aca9cd8da0 100644 --- a/content/en/docs/refguide9/general/install.md +++ b/content/en/docs/refguide9/general/install.md @@ -62,6 +62,7 @@ Sometimes you can run into problems when installing Studio Pro. One work-around The prerequisites are the following: * Microsoft .NET Desktop Runtime + | Studio Pro 9.0.0 - 9.24.33 | Studio Pro 9.24.34 - 9.24.41 | Studio Pro 9.24.42 and above | | --- | --- | --- | | [Microsoft .NET Desktop Runtime 6.0.x](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) – Mendix recommends using version 6.0.6 or above | [Microsoft .NET Desktop Runtime 8.0.x](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) – Mendix recommends using version 8.0.14 or above | [.NET Desktop Runtime 10.0.x (x64 or ARM64)](https://dotnet.microsoft.com/en-us/download/dotnet/10.0)
Mendix recommends using version 10.0.3 or above | 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 5ab1f8f59c9..edac5de5837 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 @@ -9,7 +9,7 @@ description: "Native Template 14" **Release date: Feb 25, 2026** -- We updated `.gitignore` to more precisely exclude `node_modules` directories in specific locations. +* We updated `.gitignore` to more precisely exclude `node_modules` directories in specific locations. ## 14.1.13 {#1423} 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 5b51ce9fed9..6a920a51132 100644 --- a/content/en/docs/releasenotes/studio-pro/10/10.24.md +++ b/content/en/docs/releasenotes/studio-pro/10/10.24.md @@ -18,30 +18,30 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for ### Improvements -- We introduced an opt-in runtime setting `MaxRetrieveAmount` that limits the maximum amount of objects retrieved by database data source operation. (Tickets 236618, 247111) -- We improved the resizing behavior of object list grids when editing pluggable widget properties in Studio Pro. These grids now resize when their dialog windows are resized. This enhancement, for example, improves the resizing of the **Columns** grids in Data Grid 2 widgets. -- Studio Pro has been updated to run on .NET 10 instead of .NET 8. As a result, .NET 10 is now a required [prerequisite](/refguide10/system-requirements/) for the application. -- We improved handling of cases where a user is deleted concurrently while a session is retrieved for the same user. -- We improved the `Set all to` toggle in the entity access rules editor so that when some members have access rights and others do not. Now, the toggle disables all rights instead of enabling them. This prevents the `Write` toggle from unexpectedly affecting read access. +* We introduced an opt-in runtime setting `MaxRetrieveAmount` that limits the maximum amount of objects retrieved by database data source operation. (Tickets 236618, 247111) +* We improved the resizing behavior of object list grids when editing pluggable widget properties in Studio Pro. These grids now resize when their dialog windows are resized. This enhancement, for example, improves the resizing of the **Columns** grids in Data Grid 2 widgets. +* Studio Pro has been updated to run on .NET 10 instead of .NET 8. As a result, .NET 10 is now a required [prerequisite](/refguide10/system-requirements/) for the application. +* We improved handling of cases where a user is deleted concurrently while a session is retrieved for the same user. +* We improved the `Set all to` toggle in the entity access rules editor so that when some members have access rights and others do not. Now, the toggle disables all rights instead of enabling them. This prevents the `Write` toggle from unexpectedly affecting read access. ### Fixes -- We fixed an issue with data sources where non-committed specialization objects with associations would cause a system administrator error pop-up in the client. (Ticket 262690) -- We fixed an issue where an Oops dialog appeared with conditional editability settings when a page contains multiple widgets with the same name, for example as a side effect of a merge. (Ticket 264502) -- We fixed an issue where, when re-running an app, an error would be thrown when the browser's session storage quota was exceeded because the object cache was too large. We now log this error to the console and reload the app without preserving state. (Ticket 264656) -- We fixed the `NullPointerException` which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403) -- We fixed an error affecting offline Retrieve actions when the entity was not accessible to the current user. (Ticket 266127) -- We fixed an issue in database retrievals with constraints in offline apps that caused empty result sets when the constraint referred to an association defined on a generalization of the entity of the database retrieval. (Ticket 267432) -- In the logic editors, we fixed an issue affecting users [extracting submicroflows](/refguide10/extracting-and-using-sub-microflows/) if the sequence flow in the original microflow had invalid condition value, and the extracted microflow was missing one. (Ticket 269233) +* We fixed an issue with data sources where non-committed specialization objects with associations would cause a system administrator error pop-up in the client. (Ticket 262690) +* We fixed an issue where an Oops dialog appeared with conditional editability settings when a page contains multiple widgets with the same name, for example as a side effect of a merge. (Ticket 264502) +* We fixed an issue where, when re-running an app, an error would be thrown when the browser's session storage quota was exceeded because the object cache was too large. We now log this error to the console and reload the app without preserving state. (Ticket 264656) +* We fixed the `NullPointerException` which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403) +* We fixed an error affecting offline Retrieve actions when the entity was not accessible to the current user. (Ticket 266127) +* We fixed an issue in database retrievals with constraints in offline apps that caused empty result sets when the constraint referred to an association defined on a generalization of the entity of the database retrieval. (Ticket 267432) +* In the logic editors, we fixed an issue affecting users [extracting submicroflows](/refguide10/extracting-and-using-sub-microflows/) if the sequence flow in the original microflow had invalid condition value, and the extracted microflow was missing one. (Ticket 269233) We fixed an issue where long-running after-startup microflows caused other nodes to assume it had crashed. (Ticket 269993) -- We fixed an issue where an Oops pop-up window was displayed when a widget with a data source contained expressions referring to unavailable variables. (Ticket 270865) -- We fixed an issue where SVGs failed to render in offline profiles. -- We fixed an issue where `access denied` exceptions could occur during rebase, merge, cherry-pick, revert, or feature branch merge operations. -- We fixed an issue that when a document was modified on one source and deleted on other during a combination process, users lacked the option to resolve a conflict by deleting a document -- We fixed an issue when, after performing a rebase or cherry-pick when user did not close the push notification bar and started with new combination operation, they could end up with two visible notification bars. -- We fixed an issue with the Native ListView widget where, due to a race condition, items would not consistently load beyond a certain threshold. -- We fixed an issue where bundling protected modules used in App Modules would not include JavaScript Actions and other dependencies as expected. -- We fixed an issue where deleting a duplicate navigation profile would delete the wrong duplicate profile. +* We fixed an issue where an Oops pop-up window was displayed when a widget with a data source contained expressions referring to unavailable variables. (Ticket 270865) +* We fixed an issue where SVGs failed to render in offline profiles. +* We fixed an issue where `access denied` exceptions could occur during rebase, merge, cherry-pick, revert, or feature branch merge operations. +* We fixed an issue that when a document was modified on one source and deleted on other during a combination process, users lacked the option to resolve a conflict by deleting a document +* We fixed an issue when, after performing a rebase or cherry-pick when user did not close the push notification bar and started with new combination operation, they could end up with two visible notification bars. +* We fixed an issue with the Native ListView widget where, due to a race condition, items would not consistently load beyond a certain threshold. +* We fixed an issue where bundling protected modules used in App Modules would not include JavaScript Actions and other dependencies as expected. +* We fixed an issue where deleting a duplicate navigation profile would delete the wrong duplicate profile. ## 10.24.15 {#102415} diff --git a/content/en/docs/releasenotes/studio-pro/11/11.6.md b/content/en/docs/releasenotes/studio-pro/11/11.6.md index a8a206ecd05..457ab1fb263 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.6.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.6.md @@ -14,26 +14,27 @@ mts: true ### Improvements -- The macOS installer now includes the Mendix Version Selector. This enhancement allows macOS Studio Pro users to open applications directly from [Apps](https://sprintr.home.mendix.com/link/myapps), double-click MPR/MPK files to open them, or send stories to Studio Pro from the **Plan & Build with Maia** flow in Mendix Portal. -- We renamed Studio Pro on macOS to Mendix Studio Pro. -- We improved handling of cases where a user is deleted concurrently while a session is retrieved for the same user. -- We improved the `Set all to` toggle in the entity access rules editor so that when some members have access rights and others don't, the toggle now disables all rights instead of enabling them. This prevents the `Write` toggle from unexpectedly affecting read access. +* The macOS installer now includes the Mendix Version Selector. This enhancement allows macOS Studio Pro users to open applications directly from [Apps](https://sprintr.home.mendix.com/link/myapps), double-click MPR/MPK files to open them, or send stories to Studio Pro from the **Plan & Build with Maia** flow in Mendix Portal. +* We renamed Studio Pro on macOS to Mendix Studio Pro. +* We improved handling of cases where a user is deleted concurrently while a session is retrieved for the same user. +* We improved the `Set all to` toggle in the entity access rules editor so that when some members have access rights and others don't, the toggle now disables all rights instead of enabling them. This prevents the `Write` toggle from unexpectedly affecting read access. ### Fixes -- We fixed an issue where an Oops pop-up window appeared with conditional editability settings when a page contains multiple widgets with the same name, for example as a side effect of a merge. (Ticket 264502) -- 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) -- We fixed the NullPointerException which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403) -- In the logic editors, we fixed an issue when a Show Message activity could have an empty caption after initial loading of the microflow. (Ticket 268024). -- In the logic editors, we fixed an issue affecting users [extracting submicroflows](/refguide/extracting-and-using-sub-microflows/) if the sequence flow in the original microflow had invalid condition value, and the extracted microflow was missing one. (Ticket 269233). -- We fixed an issue where long-running after-startup microflows caused other nodes to assume it had crashed. (Ticket 269993) -- We fixed an issue where an Oops pop-up window appeared with conditional editability settings when a widget referenced a default variable. (Ticket 270420) -- We fixed an issue where an Oops pop-up window was displayed when a widget with a data source contained expressions referring to unavailable variables. (Ticket 270865) -- We fixed an issue where, when downloading a widget from the Marketplace or updating a widget via the widget updater, the widget MPK file would become corrupted. This corruption led to an error dialog appearing in Studio Pro when attempting to read the widget package. (Tickets 270889, 271134) -- We fixed an issue where SVGs failed to render in the offline profile. -- We fixed an issue that when document was modified on one source and deleted on other during combination process user had no option to resolve a conflict by deleting a document. +* We fixed an issue where an Oops pop-up window appeared with conditional editability settings when a page contains multiple widgets with the same name, for example as a side effect of a merge. (Ticket 264502) +* 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) +* We fixed the NullPointerException which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403) +* In the logic editors, we fixed an issue when a Show Message activity could have an empty caption after initial loading of the microflow. (Ticket 268024). +* In the logic editors, we fixed an issue affecting users [extracting submicroflows](/refguide/extracting-and-using-sub-microflows/) if the sequence flow in the original microflow had invalid condition value, and the extracted microflow was missing one. (Ticket 269233). +* We fixed an issue where long-running after-startup microflows caused other nodes to assume it had crashed. (Ticket 269993) +* We fixed an issue where an Oops pop-up window appeared with conditional editability settings when a widget referenced a default variable. (Ticket 270420) +* We fixed an issue where an Oops pop-up window was displayed when a widget with a data source contained expressions referring to unavailable variables. (Ticket 270865) +* We fixed an issue where, when downloading a widget from the Marketplace or updating a widget via the widget updater, the widget MPK file would become corrupted. This corruption led to an error dialog appearing in Studio Pro when attempting to read the widget package. (Tickets 270889, 271134) +* We fixed an issue where SVGs failed to render in the offline profile. +* We fixed an issue that when document was modified on one source and deleted on other during combination process user had no option to resolve a conflict by deleting a document. + * We fixed an issue when, after rebasing or cherry-picking, the user did not close the push notification bar. Starting with new combination operations in these scenarios led to two visible notification bars. -- We fixed an issue in the React client where enabling autofocus on a popup that only contained focusable elements in the header or footer resulted in no element being focused. +* We fixed an issue in the React client where enabling autofocus on a popup that only contained focusable elements in the header or footer resulted in no element being focused. ## 11.6.3 {#1163} diff --git a/content/en/docs/releasenotes/studio-pro/11/11.8.md b/content/en/docs/releasenotes/studio-pro/11/11.8.md index 7f4af2c1c37..01b071c8454 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.8.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.8.md @@ -36,89 +36,90 @@ Maia Make capabilities are enabled by default. You can disable them in Studio Pr #### Other New Features {#other-new-features} -- We added a **Cancel synchronization** nanoflow activity to stop synchronization. -- We added a `reloadApp` function to the `mx-api/ui` Client API that allows you to reload your application. By passing the optional `withState` parameter, you can preserve the application's state during the reload. This method is not supported on native mobile. For more information, refer to the [Client API documentation](/apidocs-mxsdk/apidocs/client-api/). -- We added non-interrupting event sub-processes to the workflow editor. This allows users to trigger optional process flows at any point during a workflow's execution. By using the `notify workflow` mechanism and targeting the sub-process's start event, these additional flows can be initiated without interrupting the main workflow. For more information, see [Event Sub-Processes](/refguide/workflow-event-sub-processes/). -- We added an `allowUpload` flag on `file` and `image` properties that provides upload capabilities to progressive web apps. We added new types `EditableFileValue` and `EditableImageValue` to provide upload-related methods (such as `setValue` and `setValidator`). This flag is optional to ensure backwards compatibility, with the default value being `false`. Native widgets do not currently support this feature. +* We added a **Cancel synchronization** nanoflow activity to stop synchronization. +* We added a `reloadApp` function to the `mx-api/ui` Client API that allows you to reload your application. By passing the optional `withState` parameter, you can preserve the application's state during the reload. This method is not supported on native mobile. For more information, refer to the [Client API documentation](/apidocs-mxsdk/apidocs/client-api/). +* We added non-interrupting event sub-processes to the workflow editor. This allows users to trigger optional process flows at any point during a workflow's execution. By using the `notify workflow` mechanism and targeting the sub-process's start event, these additional flows can be initiated without interrupting the main workflow. For more information, see [Event Sub-Processes](/refguide/workflow-event-sub-processes/). +* We added an `allowUpload` flag on `file` and `image` properties that provides upload capabilities to progressive web apps. We added new types `EditableFileValue` and `EditableImageValue` to provide upload-related methods (such as `setValue` and `setValidator`). This flag is optional to ensure backwards compatibility, with the default value being `false`. Native widgets do not currently support this feature. ### Improvements -- We introduced an opt-in runtime setting `MaxRetrieveAmount` that limits the maximum amount of objects retrieved by database datasource operation. (Tickets 236618, 247111) -- We fixed the issue in OData Exists queries where an XPath constraint with nested-associations would result in incorrect OData filter (Ticket 261698). -- We improved the new `reloadApp` function (explained in Other Improvements [above](#other-new-features)) in the `mx-api/ui` Client API to better handle sessionStorage quota exceeded errors. When `withState` is `true` and the browser's sessionStorage quota is exceeded, it now throws a `ReloadStateQuotaExceededError` that you can catch and handle. For more information, refer to the [Client API documentation](/apidocs-mxsdk/apidocs/client-api-11/). When re-running an app in development and the sessionStorage quota is exceeded, the reload gracefully falls back to reloading without preserving state. (Ticket 264656) -- The `OQL DELETE FROM` statement now supports associations with [on delete](/refguide/association-properties/#delete-behavior) behavior with the following functionality: +* We introduced an opt-in runtime setting `MaxRetrieveAmount` that limits the maximum amount of objects retrieved by database datasource operation. (Tickets 236618, 247111) +* We fixed the issue in OData Exists queries where an XPath constraint with nested-associations would result in incorrect OData filter (Ticket 261698). +* We improved the new `reloadApp` function (explained in Other Improvements [above](#other-new-features)) in the `mx-api/ui` Client API to better handle sessionStorage quota exceeded errors. When `withState` is `true` and the browser's sessionStorage quota is exceeded, it now throws a `ReloadStateQuotaExceededError` that you can catch and handle. For more information, refer to the [Client API documentation](/apidocs-mxsdk/apidocs/client-api-11/). When re-running an app in development and the sessionStorage quota is exceeded, the reload gracefully falls back to reloading without preserving state. (Ticket 264656) +* The `OQL DELETE FROM` statement now supports associations with [on delete](/refguide/association-properties/#delete-behavior) behavior with the following functionality: * Delete associated objects as well * Delete the object only if there are no associated objects -- We removed unnecessary transaction savepoints created by the runtime when committing or deleting multiple objects. -- We added a configurable option **Use new string behavior** in the Runtime tab that controls how null and undefined values are handled for string attributes in the client. The new behavior (on by default for new projects) keeps these values as null to maintain consistency between nanoflows and microflows, while the old behavior converts them to empty strings. This option provides backward compatibility and gives developers time to migrate to the new more consistent behavior. -- [Date Picker](/refguide/date-picker/) now shows placeholder (or date format if placeholder is empty) even if the widget is in read only state. This makes the date picker widget consistent with other input widgets. -- When the progress dialog only has one step, we now only show the progress bar. -- We improved performance for the `mx.exe diff` command. Now the command consumes less memory and executes faster. -- The macOS installer now includes the Mendix Version Selector. This enhancement allows macOS Studio Pro users to open applications directly from Sprintr, double-click MPR/MPK files to open them, and then use the `Start from Maia` feature within the Mendix Portal. -- The Studio Pro on macOS was renamed to Mendix Studio Pro. -- We improved the error message in case the database does not contain a pre-analysis migration version. That can happen only when upgrading from a Mendix version earlier than 5.10. -- We have removed a redundant **Maia Explain** button from the logic editors. We recommend using the **Maia Explain** item in the context menu of the App Explorer. -- We simplified Maia preferences by adding a single toggle to enable or disable all Maia features at once. -- The OpenAPI documentation pane in Studio Pro now allows you to copy text using Ctrl + C. -- We improved the Gradle settings in the Preferences. The Gradle location will now not be hidden if Gradle synchronization is disabled. -- We clarified an error message when cloning or checking out a branch into a directory with a long path. -- We increased the width of scrollbars on editors and some of the panes to increase usability. -- We improved the `Set all to` toggle in the entity access rules editor so that when some members have access rights and others do not, the toggle now disables all rights instead of enabling them. This prevents the `Write` toggle from unexpectedly affecting read access. -- The consumed REST service editor in Studio Pro is now available in all languages that Studio Pro supports, not just English. -- We improved the security of Git process execution during version control operations. - +* We removed unnecessary transaction savepoints created by the runtime when committing or deleting multiple objects. +* We added a configurable option **Use new string behavior** in the Runtime tab that controls how null and undefined values are handled for string attributes in the client. The new behavior (on by default for new projects) keeps these values as null to maintain consistency between nanoflows and microflows, while the old behavior converts them to empty strings. This option provides backward compatibility and gives developers time to migrate to the new more consistent behavior. +* [Date Picker](/refguide/date-picker/) now shows placeholder (or date format if placeholder is empty) even if the widget is in read only state. This makes the date picker widget consistent with other input widgets. +* When the progress dialog only has one step, we now only show the progress bar. +* We improved performance for the `mx.exe diff` command. Now the command consumes less memory and executes faster. +* The macOS installer now includes the Mendix Version Selector. This enhancement allows macOS Studio Pro users to open applications directly from Sprintr, double-click MPR/MPK files to open them, and then use the `Start from Maia` feature within the Mendix Portal. +* The Studio Pro on macOS was renamed to Mendix Studio Pro. +* We improved the error message in case the database does not contain a pre-analysis migration version. That can happen only when upgrading from a Mendix version earlier than 5.10. +* We have removed a redundant **Maia Explain** button from the logic editors. We recommend using the **Maia Explain** item in the context menu of the App Explorer. +* We simplified Maia preferences by adding a single toggle to enable or disable all Maia features at once. +* The OpenAPI documentation pane in Studio Pro now allows you to copy text using Ctrl + C. +* We improved the Gradle settings in the Preferences. The Gradle location will now not be hidden if Gradle synchronization is disabled. +* We clarified an error message when cloning or checking out a branch into a directory with a long path. +* We increased the width of scrollbars on editors and some of the panes to increase usability. +* We improved the `Set all to` toggle in the entity access rules editor so that when some members have access rights and others do not, the toggle now disables all rights instead of enabling them. This prevents the `Write` toggle from unexpectedly affecting read access. +* The consumed REST service editor in Studio Pro is now available in all languages that Studio Pro supports, not just English. +* We improved the security of Git process execution during version control operations. #### Updated Language Codes for Hebrew and Indonesian We updated the ISO 639 language codes for **Hebrew** and **Indonesian** to align with the current standard: - - **Hebrew**: Changed from `iw_IL` (deprecated) to `he_IL` (current standard) - - **Indonesian**: Changed from `in_ID` (deprecated) to `id_ID` (current standard) + +* **Hebrew**: Changed from `iw_IL` (deprecated) to `he_IL` (current standard) +* **Indonesian**: Changed from `in_ID` (deprecated) to `id_ID` (current standard) If your app uses **Hebrew** or **Indonesian**, these languages will be marked with an asterisk in your project, and you will see a deprecation warning. To migrate to the updated language codes: - - Add the non-deprecated version of the language to your app (one without asterisk) - - Move existing translations from the deprecated language to the new version using **Language** > **Language Operations** - - Remove the deprecated language version (marked with asterisk) from your app + +* Add the non-deprecated version of the language to your app (one without asterisk) +* Move existing translations from the deprecated language to the new version using **Language** > **Language Operations** +* Remove the deprecated language version (marked with asterisk) from your app This ensures your app uses the current ISO 639 standard and avoids future compatibility issues. ### Fixes -- We fixed an issue when Studio Pro was not able to find git after fresh installation if it was run from installer. (Tickets 232343, 232540, 232452, 234800, 231989) -- We fixed an issue where when a document was modified in one source and deleted in another, user had no option to resolve a conflict by deleting the document during the combination process. (Ticket 263119) -- We fixed an issue where an Oops dialog appeared with conditional editability settings when a page contains multiple widgets with the same name, for example as a side effect of a merge. (Ticket 264502) -- We fixed an issue where an Oops dialog appeared with conditional editability settings when a widget referenced a default variable. (Ticket 270420) -- We fixed an issue where an Oops pop-up window was displayed when a widget with a data source contained expressions referring to unavailable variables. (Ticket 270865) -- 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) -- We fixed the NullPointerException which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403) -- In the logic editors, we fixed an issue where **Show Message** activity had an empty caption after initial loading of the microflow. (Ticket 268024). -- We fixed an issue where signing in with incorrect credentials would throw an error in the client console instead of showing a validation message. This was caused by the Runtime not returning a 401 response for authentication failures. We also fixed the same issue for license-related errors where a 402 response was not being returned. (Ticket 268509) -- 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) -- In the logic editors, we fixed an issue when Extracting submicroflow the sequence flow in the original microflow had invalid condition value, and extracted microflow was missing one. (Ticket 269233) -- We fixed an issue where a long-running after startup microflow caused other nodes to assume that the node had crashed. (Ticket 269993) -- We fixed an issue where, when downloading a widget from the Marketplace or updating a widget via the widget updater, the widget MPK file would become corrupted. This corruption led to an error dialog appearing in Studio Pro when attempting to read the widget package. (Ticket 270889, 271134) -- We fixed an issue where deleting an external object with a local association to it that uses the direct association storage format would fail with an exception. -- We fixed an issue where reversing an association’s direction via the context menu in the Domain Model editor did not function correctly. -- We fixed an issue in workflow user tasks, where having no fallback outcome in majority or threshold criteria with a single outcome would prevent the runtime from starting. -- We fixed an issue in the modernized app explorer where pressing the Del key in the search input would trigger document deletion instead of text deletion. -- We fixed an issue in the modernized app explorer where the version number of an add-on module would not show. -- We fixed the issue in the modernized App Explorer where the visibility icon was not displayed when the export level was set to 'Usable'. -- We fixed an issue in the modernized App Explorer where pressing [Escape] would not clear the search query. -- We fixed an issue in the modernized App Explorer where the hotkey combination for opening the context menu (Shift + F10) did not work. -- We fixed an issue in the modernized App Explorer where a Domain Model node with View Entity documents as children would automatically expand on double click. -- We fixed an issue in several right-click context menus that made MacOS several hotkey combinations display incorrectly. -- We fixed an `SQLite Error 5: 'database is locked'` error. -- We fixed an issue where 'access denied' exceptions could occur during rebase, merge, cherry-pick, revert, or feature branch merge operations. -- We fixed an issue where Maia explain for Microflows crashed sometimes. -- We fixed an issue in Maia chat causing it to crash when a Studio Pro version attribute was missing in a reference. -- We fixed scenarios in Android where navigating fields of a Dataview, of different types, was not possible using an external keyboard. -- We fixed an issue in the **Call external action** activity in Studio Pro where resolving inconsistencies would clear additional attributes. -- We fixed an issue in the OpenAPI documents of published REST services. The dates used in examples now use correct values. -- We fixed `com.mendix.systemwideinterfaces.core.IUser::getUserName` which was always returning the user name at the time of login. It is now returning the actual user name after a cached session has been revalidated. -- We resolved an issue where partially cloned apps were mistakenly identified as fully cloned during the cloning process, potentially leading to a 128 error. -- We fixed an issue on macOS where some views would behave in unwanted ways when scrolling. -- We fixed an issue in the React client where enabling autofocus on a popup that only contained focusable elements in the header or footer resulted in no element being focused. -- We fixed an issue where autofocus was not enabled for login dialogs and popups shown by the `Show message` action. -- We fixed an issue where a TabContainer was not updating the active tab attribute or firing the onChange nanoflow on tab switch when the TabContainer entity was passed as a nanoflow argument. -- We fixed an issue where an Oops pop-up window appeared when page actions with return value mappings were copied and pasted or extracted to a snippet. +* We fixed an issue when Studio Pro was not able to find git after fresh installation if it was run from installer. (Tickets 232343, 232540, 232452, 234800, 231989) +* We fixed an issue where when a document was modified in one source and deleted in another, user had no option to resolve a conflict by deleting the document during the combination process. (Ticket 263119) +* We fixed an issue where an Oops dialog appeared with conditional editability settings when a page contains multiple widgets with the same name, for example as a side effect of a merge. (Ticket 264502) +* We fixed an issue where an Oops dialog appeared with conditional editability settings when a widget referenced a default variable. (Ticket 270420) +* We fixed an issue where an Oops pop-up window was displayed when a widget with a data source contained expressions referring to unavailable variables. (Ticket 270865) +* 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) +* We fixed the NullPointerException which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403) +* In the logic editors, we fixed an issue where **Show Message** activity had an empty caption after initial loading of the microflow. (Ticket 268024). +* We fixed an issue where signing in with incorrect credentials would throw an error in the client console instead of showing a validation message. This was caused by the Runtime not returning a 401 response for authentication failures. We also fixed the same issue for license-related errors where a 402 response was not being returned. (Ticket 268509) +* 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) +* In the logic editors, we fixed an issue when Extracting submicroflow the sequence flow in the original microflow had invalid condition value, and extracted microflow was missing one. (Ticket 269233) +* We fixed an issue where a long-running after startup microflow caused other nodes to assume that the node had crashed. (Ticket 269993) +* We fixed an issue where, when downloading a widget from the Marketplace or updating a widget via the widget updater, the widget MPK file would become corrupted. This corruption led to an error dialog appearing in Studio Pro when attempting to read the widget package. (Ticket 270889, 271134) +* We fixed an issue where deleting an external object with a local association to it that uses the direct association storage format would fail with an exception. +* We fixed an issue where reversing an association’s direction via the context menu in the Domain Model editor did not function correctly. +* We fixed an issue in workflow user tasks, where having no fallback outcome in majority or threshold criteria with a single outcome would prevent the runtime from starting. +* We fixed an issue in the modernized app explorer where pressing the Del key in the search input would trigger document deletion instead of text deletion. +* We fixed an issue in the modernized app explorer where the version number of an add-on module would not show. +* We fixed the issue in the modernized App Explorer where the visibility icon was not displayed when the export level was set to 'Usable'. +* We fixed an issue in the modernized App Explorer where pressing [Escape] would not clear the search query. +* We fixed an issue in the modernized App Explorer where the hotkey combination for opening the context menu (Shift + F10) did not work. +* We fixed an issue in the modernized App Explorer where a Domain Model node with View Entity documents as children would automatically expand on double click. +* We fixed an issue in several right-click context menus that made MacOS several hotkey combinations display incorrectly. +* We fixed an `SQLite Error 5: 'database is locked'` error. +* We fixed an issue where 'access denied' exceptions could occur during rebase, merge, cherry-pick, revert, or feature branch merge operations. +* We fixed an issue where Maia explain for Microflows crashed sometimes. +* We fixed an issue in Maia chat causing it to crash when a Studio Pro version attribute was missing in a reference. +* We fixed scenarios in Android where navigating fields of a Dataview, of different types, was not possible using an external keyboard. +* We fixed an issue in the **Call external action** activity in Studio Pro where resolving inconsistencies would clear additional attributes. +* We fixed an issue in the OpenAPI documents of published REST services. The dates used in examples now use correct values. +* We fixed `com.mendix.systemwideinterfaces.core.IUser::getUserName` which was always returning the user name at the time of login. It is now returning the actual user name after a cached session has been revalidated. +* We resolved an issue where partially cloned apps were mistakenly identified as fully cloned during the cloning process, potentially leading to a 128 error. +* We fixed an issue on macOS where some views would behave in unwanted ways when scrolling. +* We fixed an issue in the React client where enabling autofocus on a popup that only contained focusable elements in the header or footer resulted in no element being focused. +* We fixed an issue where autofocus was not enabled for login dialogs and popups shown by the `Show message` action. +* We fixed an issue where a TabContainer was not updating the active tab attribute or firing the onChange nanoflow on tab switch when the TabContainer entity was passed as a nanoflow argument. +* We fixed an issue where an Oops pop-up window appeared when page actions with return value mappings were copied and pasted or extracted to a snippet. diff --git a/content/en/docs/releasenotes/studio-pro/9/9.24.md b/content/en/docs/releasenotes/studio-pro/9/9.24.md index 818e235348d..d0bfac25b9b 100644 --- a/content/en/docs/releasenotes/studio-pro/9/9.24.md +++ b/content/en/docs/releasenotes/studio-pro/9/9.24.md @@ -19,17 +19,17 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 9 release for a ### Improvements -- Studio Pro has been updated to run on .NET 10 instead of .NET 8. As a result, .NET 10 is now a required prerequisite for the application. For more information, see [System Requirements](/refguide9/system-requirements/#software-specifications) -- We updated the .NET runtime version installed with Studio Pro to .NET 10.0.3. -- We improved the performance of session cleanup. -- We changed the level of log messages on the **SystemTask** log node to debug. For non-development deployments this log node was set to info, which was causing too many messages. +* Studio Pro has been updated to run on .NET 10 instead of .NET 8. As a result, .NET 10 is now a required prerequisite for the application. For more information, see [System Requirements](/refguide9/system-requirements/#software-specifications) +* We updated the .NET runtime version installed with Studio Pro to .NET 10.0.3. +* We improved the performance of session cleanup. +* We changed the level of log messages on the **SystemTask** log node to debug. For non-development deployments this log node was set to info, which was causing too many messages. ### Fixes -- 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) -- We fixed an issue where changing the queue parallelism through a microflow constant was not working correctly for cluster-wide queues. (Ticket 267097) -- We fixed an issue where a long-running after startup microflow causes the node to be assumed crashed by other nodes. (Ticket 269993) -- We fixed an issue in import/export mapping in Studio Pro where elements except first of the child array in JSON were omitted. +* 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) +* We fixed an issue where changing the queue parallelism through a microflow constant was not working correctly for cluster-wide queues. (Ticket 267097) +* We fixed an issue where a long-running after startup microflow causes the node to be assumed crashed by other nodes. (Ticket 269993) +* We fixed an issue in import/export mapping in Studio Pro where elements except first of the child array in JSON were omitted. ## 9.24.41 diff --git a/content/en/docs/workstation/wks-import.md b/content/en/docs/workstation/wks-import.md index 233be2c05c3..ad559dc40cb 100644 --- a/content/en/docs/workstation/wks-import.md +++ b/content/en/docs/workstation/wks-import.md @@ -79,4 +79,4 @@ To transfer the contents of a single station, perform the following steps: {{% alert color="info" %}} By default, the single station import operates in duplicate mode. That is, when you import a station with same name as an existing station, a new station is created with a number appended to the name. For example, copying and pasting a station called *My Station* creates a station called *My Station (1)*. -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/workstation/wks-message-syntax.md b/content/en/docs/workstation/wks-message-syntax.md index 037436e5b88..3710f0e19b0 100644 --- a/content/en/docs/workstation/wks-message-syntax.md +++ b/content/en/docs/workstation/wks-message-syntax.md @@ -37,7 +37,6 @@ 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).