diff --git a/content/en/docs/control-center/security/software-composition/components.md b/content/en/docs/control-center/security/software-composition/components.md index e4508799152..9fd0f9319c2 100644 --- a/content/en/docs/control-center/security/software-composition/components.md +++ b/content/en/docs/control-center/security/software-composition/components.md @@ -109,4 +109,4 @@ The component usage list contains the following information: * **Runtime** — The runtime version to which the component is compatible. * **Target Cloud** — The type of cloud where the deployment package is deployed. * **Technical Contact** — The Technical Contact of the app. -* Column customization ({{% icon name="view" %}}) — You can customize the columns in the list by clicking the {{% icon name="view" %}} icon and selecting or deselecting options. \ No newline at end of file +* Column customization ({{% icon name="view" %}}) — You can customize the columns in the list by clicking the {{% icon name="view" %}} icon and selecting or deselecting options. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/deploying-to-mendix-cloud.md b/content/en/docs/deployment/mendix-cloud-deploy/deploying-to-mendix-cloud.md index 75e791836aa..f8756cd63de 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/deploying-to-mendix-cloud.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/deploying-to-mendix-cloud.md @@ -116,7 +116,6 @@ With a Free App, you can deploy your app to Mendix Cloud from Studio Pro by usin * Alternatively, in the top bar of Studio Pro, click **Publish**. - ## Deployment Status and Troubleshooting The [Mendix Platform Status page](https://status.mendix.com/) shows the current status of Mendix services. If you have issues with deployment, you can check the status page to see if deployment is operational (under **Mendix Services**) or if there are other Mendix issues that may be affecting your deployment. For more information, see [Mendix Cloud Status](/developerportal/deploy/mendix-cloud-status/). diff --git a/content/en/docs/deployment/mx-azure/mx-azure-installation.md b/content/en/docs/deployment/mx-azure/mx-azure-installation.md index de4c679e493..7aeadb82223 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-installation.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-installation.md @@ -254,4 +254,3 @@ Once the cluster is successfully created and initialized in the Mendix on the Az After being added, the new cluster manager has the ability to view and manage the cluster within the Mendix on the Azure portal. They can also access and update the support ticket associated with the cluster in the Mendix on Azure portal. However, the newly added cluster manager does not have access to the Zendesk ticket linked to the cluster's support ticket. If a cluster manager is deleted, they can no longer view the associated cluster or its support ticket in the Mendix on Azure portal. - diff --git a/content/en/docs/developerportal/digital-execution/implement-mendix/_index.md b/content/en/docs/developerportal/digital-execution/implement-mendix/_index.md index af87c82b9ae..63296674bba 100644 --- a/content/en/docs/developerportal/digital-execution/implement-mendix/_index.md +++ b/content/en/docs/developerportal/digital-execution/implement-mendix/_index.md @@ -26,4 +26,4 @@ After completing the steps outlined in this guide, you will be able to: * Prepare your first project, and onboard your first project team. * Launch your first app. -## Documents in This Category \ No newline at end of file +## Documents in This Category diff --git a/content/en/docs/developerportal/digital-execution/implement-mendix/mendix-ecosystem.md b/content/en/docs/developerportal/digital-execution/implement-mendix/mendix-ecosystem.md index 70c5c589948..d7190ea76af 100644 --- a/content/en/docs/developerportal/digital-execution/implement-mendix/mendix-ecosystem.md +++ b/content/en/docs/developerportal/digital-execution/implement-mendix/mendix-ecosystem.md @@ -166,4 +166,4 @@ It is important to know what’s happening with the Mendix Platform to be sure t * [Join the Mendix Community](https://community.mendix.com/p/questions) to connect with over 290,000 community members. The Mendix Community is a great place for developers to ask questions and post ideas for our product managers. -* [Subscribe to our blog](https://www.mendix.com/blog/#blog__subscribe) and deep dive into our diverse library of articles and blog posts, where we discuss everything from Mendix best practices to industry trends. \ No newline at end of file +* [Subscribe to our blog](https://www.mendix.com/blog/#blog__subscribe) and deep dive into our diverse library of articles and blog posts, where we discuss everything from Mendix best practices to industry trends. diff --git a/content/en/docs/developerportal/digital-execution/implement-mendix/questions-feedback.md b/content/en/docs/developerportal/digital-execution/implement-mendix/questions-feedback.md index 4f5f1067aed..bfb1b8e2db0 100644 --- a/content/en/docs/developerportal/digital-execution/implement-mendix/questions-feedback.md +++ b/content/en/docs/developerportal/digital-execution/implement-mendix/questions-feedback.md @@ -23,4 +23,4 @@ If you need help with technical matters: Be sure to first check whether someone has already asked the question you're wondering about. If not, feel free to post it, and our community will help you out. Doing so will gain you points. * Submit a support ticket. If something really appears to be broken from a technical point of view, such as not being able to visit or edit your app anymore, contact our [Support Team](https://support.mendix.com/hc/en-us). -If you have feedback or any improvement suggestions, use the **Feedback** option at the bottom of this page. \ No newline at end of file +If you have feedback or any improvement suggestions, use the **Feedback** option at the bottom of this page. diff --git a/content/en/docs/marketplace/genai/concepts/_index.md b/content/en/docs/marketplace/genai/concepts/_index.md index 2620a4649ba..ccd275c71d9 100644 --- a/content/en/docs/marketplace/genai/concepts/_index.md +++ b/content/en/docs/marketplace/genai/concepts/_index.md @@ -102,7 +102,6 @@ See [Function Calling](/appstore/modules/genai/function-calling/) for more infor This pattern is supported both by [OpenAI](https://platform.openai.com/docs/guides/function-calling) and [various models available on Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/conversation-inference.html#conversation-inference-supported-models-features). - ## Agents and Assistants {#agents} The agent concept combines prompts, RAG (Retrieval Augmented Generation), and ReAct patterns in a single call. These components of agent-based logic are all supported by our Agents Kit. Using LLMs, business logic can be enriched by enabling AI agents to reason and autonomously execute actions while being grounded in domain-specific knowledge. With Mendix's Agents Kit, agents become a seamless part of your application's logic. @@ -110,5 +109,3 @@ The agent concept combines prompts, RAG (Retrieval Augmented Generation), and Re For an overview of the components that help you get started, refer to [the Agents Kit overview](/appstore/modules/genai/#architecture). In addition, you can integrate agentic behavior in a Mendix app by leveraging external agents through cloud infrastructure providers. In this case, the Mendix app does not store the agent definition. Instead, it only calls the external agent. For example, [Agents for Amazon Bedrock](https://aws.amazon.com/bedrock/agents/) provides this functionality for Amazon Bedrock. You can find out how to use this in your Mendix application in [Invoking an Agent with the InvokeAgent Operation](/appstore/modules/aws/amazon-bedrock/#invokeagent) section of the *Amazon Bedrock* module documentation. - - diff --git a/content/en/docs/marketplace/platform-supported-content/modules/oidc.md b/content/en/docs/marketplace/platform-supported-content/modules/oidc.md index 5612391b5a9..bde35de8ed6 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/oidc.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/oidc.md @@ -1146,4 +1146,4 @@ If a user logs in on one tab and then attempts to log in on another tab, a `401` ### Endpoints cannot be reached -This issue can be caused by wrong configuration of your firewall. If you have a firewall between your application and your IdP, make sure it is properly configured for the consumption of the endpoints. \ No newline at end of file +This issue can be caused by wrong configuration of your firewall. If you have a firewall between your application and your IdP, make sure it is properly configured for the consumption of the endpoints. 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 a43440e3bd6..45698979c72 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 @@ -42,15 +42,12 @@ Once the Mendix Data Loader is deployed, follow these steps to configure and use 4. Click **Create** to create a new data source. 1. Enter a **Name** for your data source within the Data Loader. 2. Enter an **API endpoint** – that is, the base endpoint for the OData resource in your Mendix application, for example, `https://yourmendixapp.mendixcloud.com/odata/snowflakedata/v1/`. - {{% alert color="warning" %}}This must be the root URL, that is, it must end in `/v1/` or `/v2/` Adding anything to the root URL (such as a resource path) will prevent the Mendix Data Loader from working. If you want to use specific resources, you should instead expose a new endpoint that only contains the resources that you require. This is because it is only possible to use every resource that is exposed in the OData endpoint, and impossible to exclude certain resources.{{% /alert %}} - 3. Use the **Use Delta Ingestion** check box to specify if you want to ingest all exposed data with every ingestion, or if you want to ingest only data that was newly created or changed since the last ingestion for this data source. 4. Click **Save**. 5. Grant the application **CREATE DATABASE** and **EXECUTE TASK** privileges. This step is necessary for the application to create the staging database for data ingestion and to execute tasks. - 5. To view the status of your data source, check the **Details**. 6. To view the configuration status, click the **Authentication Configuration** tab. 7. To set up authentication, click **Edit**, and then provide the required information based on the selected authentication type: @@ -75,6 +72,7 @@ If you want to use specific resources, you should instead expose a new endpoint 13. Click the **Data Ingestion** tab, where you can start your data ingestion or set up a schedule. 14. Click **Ingest Now** to start a data ingestion. 15. Click **New Task** to create a CRON job for scheduled data ingestions. + * To schedule the data ingestion, specify the following parameters: * **Ingestion Task Schedule** – Choose from custom CRON expression, every day at 00:00 AM UTC, every Monday at 00:00 AM UTC, or every first day of the month at 00:00 AM UTC. * **Custom CRON Expression** – Use this field only when specifying a custom CRON expression. diff --git a/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md b/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md index 8b8d1c3528f..103d4493466 100644 --- a/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md +++ b/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md @@ -147,14 +147,14 @@ Before use, please ensure you meet the following prerequisites: * Prior to adding a new font, the font files and font family have to already be included in your project. To add font files into the project, you can put the font files inside your styles/web directory. * Define font family in styling. You will need to define the new font by adding the font face custom styling. - ```css + ```css @font-face { font-family: 'Your-font-family-name'; src: url('YourFontFile.ttf') format('truetype'); font-weight: 100; font-style: normal; } - ``` + ``` #### Adding a Custom Font diff --git a/content/en/docs/mendix-portal/_index.md b/content/en/docs/mendix-portal/_index.md index f2296310b13..8c0b55d0d51 100755 --- a/content/en/docs/mendix-portal/_index.md +++ b/content/en/docs/mendix-portal/_index.md @@ -24,4 +24,4 @@ Mendix Portal is the online platform from Mendix. It allows you to create, share * Academy — Explore learning paths. * [Community](/community-tools/) — Connect with Community members, and ask and answer questions. -## Documents in This Category \ No newline at end of file +## Documents in This Category diff --git a/content/en/docs/mendix-portal/maia-portal.md b/content/en/docs/mendix-portal/maia-portal.md index 6fa524247fa..2393c231d85 100644 --- a/content/en/docs/mendix-portal/maia-portal.md +++ b/content/en/docs/mendix-portal/maia-portal.md @@ -59,4 +59,4 @@ Maia Chat supports asking follow-up questions based on your previous question an Maia Chat only keeps track of a conversation history within a session on a page in Mendix Portal. -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/private-platform/configuration/pmp-configure-aws-secret.md b/content/en/docs/private-platform/configuration/pmp-configure-aws-secret.md index f55705bf595..c8f840094d9 100644 --- a/content/en/docs/private-platform/configuration/pmp-configure-aws-secret.md +++ b/content/en/docs/private-platform/configuration/pmp-configure-aws-secret.md @@ -78,13 +78,13 @@ When creating a property to use as a key for external secret storage, use the fo * BuildPackage - * fileServerBasic + * fileServerBasic * **BuildPackage.FileBasicAuthPassword** - Password for the file server - * AwsAKSK + * AwsAKSK - * **BuildPackage.AwsSecretAccessKey** - AWS secret access key for the file server + * **BuildPackage.AwsSecretAccessKey** - AWS secret access key for the file server * RuntimeBaseImage @@ -292,7 +292,7 @@ The following example shows how you can configure Private Mendix Platform to wor The secret template contains a sample key structure which you can use: - ```text + ```text { //...other keys "VCS": { // ...other keys @@ -301,7 +301,7 @@ The following example shows how you can configure Private Mendix Platform to wor }, // ...other keys } - ``` + ``` 8. Repeat the process for other credentials as needed, ensuring you follow the naming conventions for each service. diff --git a/content/en/docs/refguide/general/mxbuild.md b/content/en/docs/refguide/general/mxbuild.md index 8dff9a27dae..9803e784c02 100644 --- a/content/en/docs/refguide/general/mxbuild.md +++ b/content/en/docs/refguide/general/mxbuild.md @@ -42,7 +42,6 @@ For MxBuild and macOS users: If you are using the macOS version of Studio Pro and you store your project files on an external drive not formatted using the Apple File System, macOS can generate hidden files and folders that can make Windows versions of Studio Pro or MxBuild not work as expected. {{% /alert %}} - ## Command Line To build your package, specify the Mendix app file (*.mpr*) for which you want to build the deployment package (*.mda*) on the command-line. The file name may be preceded by a relative or absolute path. The app file should be located inside a Mendix app directory. diff --git a/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/best-practices.md b/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/best-practices.md index db4787eb670..f6fe49e9b33 100644 --- a/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/best-practices.md +++ b/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/best-practices.md @@ -143,11 +143,13 @@ Attribute paths can not be used in sort orderings in offline apps. ## Enhancing Persistent Mode in File Storage {#persistent-mode} When using offline profiles, files are stored locally on a user's device in the browser Origin Private File System (OPFS). The OPFS can operate in two modes: **persistent** and **best-effort**. The **persistent** mode is preferable because it offers greater storage capacity and better data durability. While **persistent** mode is used by default, a browser may opt for **best-effort** mode if it assesses the site's importance as low. This assessment is made based on internal browser heuristics, which include the following: + * The level of site engagement * Whether the site has been bookmarked * Whether permission for site notifications has been granted To enhance the likelihood of operating the OPFS in 'persistent' mode, consider taking the following actions: + * Bookmark the site * Enable notifications for the site diff --git a/content/en/docs/refguide/mobile/distributing-mobile-apps/testing-mobile-apps.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/testing-mobile-apps.md index bbb63896001..2deda60aa74 100644 --- a/content/en/docs/refguide/mobile/distributing-mobile-apps/testing-mobile-apps.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/testing-mobile-apps.md @@ -99,10 +99,10 @@ While using Espresso in combination with Mendix apps, there have been occasional ```json { -"toolsVersions": { - "compileSdk": "30" - ... -} + "toolsVersions": { + "compileSdk": "30" + ... + } } ``` diff --git a/content/en/docs/refguide/modeling/menus/translatable-texts/advanced-translations-export.md b/content/en/docs/refguide/modeling/menus/translatable-texts/advanced-translations-export.md index d7e686d400d..bfc55f99db0 100644 --- a/content/en/docs/refguide/modeling/menus/translatable-texts/advanced-translations-export.md +++ b/content/en/docs/refguide/modeling/menus/translatable-texts/advanced-translations-export.md @@ -53,4 +53,4 @@ After completion, a confirmation pop-up appears. If the operation fails, a failu {{% alert color="warning" %}} Do not close the app while the export is running. -{{% /alert %}} \ No newline at end of file +{{% /alert %}} diff --git a/content/en/docs/refguide10/mobile/distributing-mobile-apps/testing-mobile-apps.md b/content/en/docs/refguide10/mobile/distributing-mobile-apps/testing-mobile-apps.md index 198bedb2689..c30fa293151 100644 --- a/content/en/docs/refguide10/mobile/distributing-mobile-apps/testing-mobile-apps.md +++ b/content/en/docs/refguide10/mobile/distributing-mobile-apps/testing-mobile-apps.md @@ -99,10 +99,10 @@ While using Espresso in combination with Mendix apps, there have been occasional ```json { -"toolsVersions": { - "compileSdk": "30" - ... -} + "toolsVersions": { + "compileSdk": "30" + ... + } } ``` diff --git a/content/en/docs/refguide9/mobile/distributing-mobile-apps/testing-mobile-apps.md b/content/en/docs/refguide9/mobile/distributing-mobile-apps/testing-mobile-apps.md index 4b98be05e13..164e9afe617 100644 --- a/content/en/docs/refguide9/mobile/distributing-mobile-apps/testing-mobile-apps.md +++ b/content/en/docs/refguide9/mobile/distributing-mobile-apps/testing-mobile-apps.md @@ -85,10 +85,8 @@ To set up Appium Desktop for native Android testing, do the following: 1. Click on the blue **Select Elements** button, and then click on an element in the app preview to spy on that element. - ### Troubleshooting Espresso - While using Espresso in combination with Mendix apps, we observed a `No static method lifecycleEventObserver` error. More information about this can be found [here](https://github.com/appium/appium-espresso-driver/issues/639). You can fix this by adding the `espressoBuildConfig` property to the capabilities. It should point to a JSON file containing: ```json @@ -101,10 +99,10 @@ While using Espresso in combination with Mendix apps, there have been occasional ```json { -"toolsVersions": { - "compileSdk": "30" - ... -} + "toolsVersions": { + "compileSdk": "30" + ... + } } ``` diff --git a/content/en/docs/releasenotes/marketplace/marketplace-services/_index.md b/content/en/docs/releasenotes/marketplace/marketplace-services/_index.md index ad10071dd7b..1495dda6211 100644 --- a/content/en/docs/releasenotes/marketplace/marketplace-services/_index.md +++ b/content/en/docs/releasenotes/marketplace/marketplace-services/_index.md @@ -9,4 +9,4 @@ numberless_headings: true The Marketplace Services Release Notes include updates to services delivered through the Mendix Marketplace: -* [Private PDF Document Generation Service](/releasenotes/marketplace/private-service/) \ No newline at end of file +* [Private PDF Document Generation Service](/releasenotes/marketplace/private-service/) diff --git a/content/en/docs/releasenotes/marketplace/marketplace-services/private-service.md b/content/en/docs/releasenotes/marketplace/marketplace-services/private-service.md index 90d9c1ad7d7..fb8a860bd71 100644 --- a/content/en/docs/releasenotes/marketplace/marketplace-services/private-service.md +++ b/content/en/docs/releasenotes/marketplace/marketplace-services/private-service.md @@ -22,4 +22,4 @@ With this version of the private PDF Document Generation service, we have improv ### Private PDF Document Generation Service -The [PDF Document Generation](/appstore/modules/document-generation/) module now supports the use of [private PDF document generation service instances](/appstore/services/private-document-generation-service/). This flexible solution is based on Docker, and is hosted and managed by you. It allows you to run your own version of the PDF Document Generation service with additional control and configuration options, and it specifically targets air-gapped apps, or tailored performance and data sharing requirements. \ No newline at end of file +The [PDF Document Generation](/appstore/modules/document-generation/) module now supports the use of [private PDF document generation service instances](/appstore/services/private-document-generation-service/). This flexible solution is based on Docker, and is hosted and managed by you. It allows you to run your own version of the PDF Document Generation service with additional control and configuration options, and it specifically targets air-gapped apps, or tailored performance and data sharing requirements. diff --git a/content/en/docs/releasenotes/mobile/native-template/_index.md b/content/en/docs/releasenotes/mobile/native-template/_index.md index 97431d3c3e0..79e9d43d19e 100644 --- a/content/en/docs/releasenotes/mobile/native-template/_index.md +++ b/content/en/docs/releasenotes/mobile/native-template/_index.md @@ -9,6 +9,7 @@ description: "Native Template release notes." For more information on native mobile app development, see the [native-template](https://github.com/mendix/native-template/) repository and the [Building, Testing, and Distributing Apps](/refguide/mobile/distributing-mobile-apps/) guide. Below you can see the current versions in active development and which Mendix Studio Pro versions they correspond with. Compatible with Studio Pro 11: + * Native Template versions of [15](/releasenotes/mobile/nt-15-rn/) are compatible with apps built using Studio Pro [11.0](/releasenotes/studio-pro/11.0/) and above. Compatible with Studio Pro 10: diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/_index.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/_index.md index d6a46759f90..96a8e0f15d1 100644 --- a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/_index.md +++ b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/_index.md @@ -8,4 +8,4 @@ description: "Studio Pro 11 compatible Native Template release notes." These are the current Native Template versions for Studio Pro 11 in active development: * Native Template versions of [15](/releasenotes/mobile/nt-15-rn/) are compatible with apps built using the following versions of Studio Pro: - * Studio Pro 11.0 and above. \ No newline at end of file + * Studio Pro 11.0 and above. diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-15-rn.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-15-rn.md index 348ff941b84..064844686bf 100644 --- a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-15-rn.md +++ b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-15-rn.md @@ -11,8 +11,8 @@ description: "Native Template 15" ### Improvements -- We migrated several libraries that had not been maintained to modern, actively-supported alternatives. -- We improved the update process from an older version of Studio Pro to the latest version. +* We migrated several libraries that had not been maintained to modern, actively-supported alternatives. +* We improved the update process from an older version of Studio Pro to the latest version. ### Removed @@ -34,11 +34,11 @@ description: "Native Template 15" ### Improvements -- We updated one library. +* We updated one library. ### Library Updates and Improvements -- **@mendix/native**: 10.1.4 +* **@mendix/native**: 10.1.4 ## 15.1.1 {#1511} @@ -66,8 +66,8 @@ description: "Native Template 15" ### Improvements -- We upgraded our Database Backend Library to the most recent version. This update brings better performance on database operations and performance improvements. +* We upgraded our Database Backend Library to the most recent version. This update brings better performance on database operations and performance improvements. ### Library Updates and Improvements -- **@op-engineering/op-sqlite**: 12.0.2 +* **@op-engineering/op-sqlite**: 12.0.2 diff --git a/content/en/docs/releasenotes/studio-pro/10/10.18.md b/content/en/docs/releasenotes/studio-pro/10/10.18.md index 0530c97fb60..1b3efd31d45 100644 --- a/content/en/docs/releasenotes/studio-pro/10/10.18.md +++ b/content/en/docs/releasenotes/studio-pro/10/10.18.md @@ -77,7 +77,7 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for ### Known Issues * Importing a module containing workflows makes all running workflow instances incompatible. (Ticket 234084) - * Fixed in [10.21.0](/releasenotes/studio-pro/10.21/#fix-workflow-instances). + * Fixed in [10.21.0](/releasenotes/studio-pro/10.21/#fix-workflow-instances). * In the React client, re-running an app locally with runtime-only changes does not properly apply those changes. (Tickets 253176, 253539, 253842, 253932, 254100) * In the React client, the debugger does not reconnect when restarting an app. diff --git a/content/en/docs/releasenotes/studio-pro/11/11.0.md b/content/en/docs/releasenotes/studio-pro/11/11.0.md index ac1e482330f..f4fa31150ef 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.0.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.0.md @@ -359,4 +359,4 @@ For details on upgrading to Studio Pro 11, see [Upgrading from Mendix Studio Pro * In the React client, re-running an app locally with runtime-only changes does not properly apply those changes. (Tickets 253176, 253539, 253842, 253932, 254100) * Fixed in [11.1.0](/releasenotes/studio-pro/11.1/#fix-runtime-only-changes) * In the React client, the debugger does not reconnect when restarting an app. - * Fixed in [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-reconnect) \ No newline at end of file + * Fixed in [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-reconnect) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.1.md b/content/en/docs/releasenotes/studio-pro/11/11.1.md index cd67249dbc7..e84b06078b1 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.1.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.1.md @@ -30,38 +30,39 @@ weight: 99 ### Improvements -- We slightly improved the memory consumption of object attributes. -- We improved the `toString` implementation of the `IMendixObjectMember` Java API to include useful data, such as name and value. -- We made various improvements to the logic editors: - - We now include Change Object activities when finding Entity usages. (Ticket 249539) - - When expanding loops after inserting elements into them, connected objects are now also moved aside. - - When resizing an element, connected annotations are now moved the same way as other elements. -- We have defined a list of associations: `System.WorkflowActivityRecord_Actor`, `System.WorkflowActivityRecord_TaskAssignedUsers`, and `System.WorkflowActivityRecord_TaskTargetedUsers`. Non-persistable objects referencing the current user through any of these associations will no longer be prevented from being garbage collected. -- The Chinese, Korean, and Japanese versions of the Studio Pro UI are now in general availability (GA). Please see the [Language](/refguide/preferences-dialog/#language) section of *Preferences* for more information. -- When updating pluggable widgets, Studio Pro will now try to preserve the value of properties that change type between versions. This is done when [the property types are compatible](/apidocs-mxsdk/apidocs/pluggable-widgets-property-types/#converting-properties). -- We improved [Start with Maia](/refguide/start-with-maia/) by making the test data generation step optional. -- We improved the way Start with Maia handles errors when test data is generated. The errors are now processed more gracefully and lead to fewer unnecessary crashes. -- We improved the notification system to alert users that third-party antivirus software (Microsoft Defender excepted) may impact system performance. -- We improved the item order in the **Go to** dialog in Studio Pro when searching to make more relevant items appear higher in the list. (Ticket 221215) -- We improved the quality of Korean and Chinese translations for error, warning, and deprecation messages. -- We improved the warning message shown when running an OQL query in view entities. When a query refers to '[%CurrentUser%]' and **App Security** is not toggled off, the warning message disappears as soon as the user is specified. -- We improved published REST services in Studio Pro so you can now download OpenAPI files, even when unrelated parts of the app are inconsistent. -- We improved the logging of published OData services so the **Debug** and **Trace** log levels of the `ConnectionBus_Retrieve` log node now log XPaths of requests. -- We removed the legacy toolbox in favor of the modernized **Toolbox**. -- Page, snippet, and action variables are now automatically mapped to microflow and nanoflow parameters that share the same name. -- We enabled [persistent mode](/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/best-practices/#persistent-mode) for storing file data in offline PWAs. This enables larger storage quotas (which are browser dependent), and the data will not be evicted in case of low disk space or infrequent Offline PWA use. In some web browsers this may lead to a browser dialog asking for permission. -- We fixed an issue when there are some files left after aborting a merge, cherry-pick, or revert operation on a commit. That caused an ERROR in STP. Now the files are reset to the initial state after aborting any of the mentioned operations. -- We now remove web service user sessions if they are expired. +* We slightly improved the memory consumption of object attributes. +* We improved the `toString` implementation of the `IMendixObjectMember` Java API to include useful data, such as name and value. +* We made various improvements to the logic editors: + * We now include Change Object activities when finding Entity usages. (Ticket 249539) + * When expanding loops after inserting elements into them, connected objects are now also moved aside. + * When resizing an element, connected annotations are now moved the same way as other elements. +* We have defined a list of associations: `System.WorkflowActivityRecord_Actor`, `System.WorkflowActivityRecord_TaskAssignedUsers`, and `System.WorkflowActivityRecord_TaskTargetedUsers`. Non-persistable objects referencing the current user through any of these associations will no longer be prevented from being garbage collected. +* The Chinese, Korean, and Japanese versions of the Studio Pro UI are now in general availability (GA). Please see the [Language](/refguide/preferences-dialog/#language) section of *Preferences* for more information. +* When updating pluggable widgets, Studio Pro will now try to preserve the value of properties that change type between versions. This is done when [the property types are compatible](/apidocs-mxsdk/apidocs/pluggable-widgets-property-types/#converting-properties). +* We improved [Start with Maia](/refguide/start-with-maia/) by making the test data generation step optional. +* We improved the way Start with Maia handles errors when test data is generated. The errors are now processed more gracefully and lead to fewer unnecessary crashes. +* We improved the notification system to alert users that third-party antivirus software (Microsoft Defender excepted) may impact system performance. +* We improved the item order in the **Go to** dialog in Studio Pro when searching to make more relevant items appear higher in the list. (Ticket 221215) +* We improved the quality of Korean and Chinese translations for error, warning, and deprecation messages. +* We improved the warning message shown when running an OQL query in view entities. When a query refers to '[%CurrentUser%]' and **App Security** is not toggled off, the warning message disappears as soon as the user is specified. +* We improved published REST services in Studio Pro so you can now download OpenAPI files, even when unrelated parts of the app are inconsistent. +* We improved the logging of published OData services so the **Debug** and **Trace** log levels of the `ConnectionBus_Retrieve` log node now log XPaths of requests. +* We removed the legacy toolbox in favor of the modernized **Toolbox**. +* Page, snippet, and action variables are now automatically mapped to microflow and nanoflow parameters that share the same name. +* We enabled [persistent mode](/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/best-practices/#persistent-mode) for storing file data in offline PWAs. This enables larger storage quotas (which are browser dependent), and the data will not be evicted in case of low disk space or infrequent Offline PWA use. In some web browsers this may lead to a browser dialog asking for permission. +* We fixed an issue when there are some files left after aborting a merge, cherry-pick, or revert operation on a commit. That caused an ERROR in STP. Now the files are reset to the initial state after aborting any of the mentioned operations. +* We now remove web service user sessions if they are expired. + * We upgraded the JDBC driver for Microsoft SQL Server to version 12.10.1. * If you connect to SQL Server using integrated security in a module such as [Database Connector](https://marketplace.mendix.com/link/component/2888), you may need to update the JDBC driver in `userlib` as well. -- When committing a list of objects, we now use JDBC batch updates to update associations instead of using separate JDBC calls. This was already the case for attribute updates. -- We enhanced the version control portfix functionality by integrating the Git CLI to perform this operation. This update optimizes the process and improves the overall stability of the portfix functionality. -- We removed the old **Show Changes On Disk** dialog, as changes to files on disk are now shown in the regular **Changes** pane. -- Buttons to **Choose branch line** and **Open in Studio Pro** are now always visible in the **Open App** window. -- We now allow the `session` and `parser` API's from `mx-api` to be used in pluggable widgets as well. They can be imported from `mendix/session` and `mendix/parser` with your widget code. -- We added the `formatValue` and `parseValue` methods from the legacy `mx.parser` API to the new client API. -- We updated the bundled Node.js from v20 to v22. -- We improved the On Change action of the Tab Container widget. +* When committing a list of objects, we now use JDBC batch updates to update associations instead of using separate JDBC calls. This was already the case for attribute updates. +* We enhanced the version control portfix functionality by integrating the Git CLI to perform this operation. This update optimizes the process and improves the overall stability of the portfix functionality. +* We removed the old **Show Changes On Disk** dialog, as changes to files on disk are now shown in the regular **Changes** pane. +* Buttons to **Choose branch line** and **Open in Studio Pro** are now always visible in the **Open App** window. +* We now allow the `session` and `parser` API's from `mx-api` to be used in pluggable widgets as well. They can be imported from `mendix/session` and `mendix/parser` with your widget code. +* We added the `formatValue` and `parseValue` methods from the legacy `mx.parser` API to the new client API. +* We updated the bundled Node.js from v20 to v22. +* We improved the On Change action of the Tab Container widget. * Now, no attribute is required and the action is triggered whenever the tab is changed. We changed the caption for the attribute setting from **Attribute** to **Active tab index**. - We improved the External Database Connector so you can dynamically modify connection settings at runtime by configuring connection parameters in the Query External Database microflow activity. - We upgraded the ONNX dependency to version 1.22.0. @@ -124,4 +125,4 @@ weight: 99 ### Breaking Changes -- We removed `com.mendix.modules.email.EmailModule` as it is no longer supported. Please use the [Email Connector](https://marketplace.mendix.com/link/component/120739) module instead. +* We removed `com.mendix.modules.email.EmailModule` as it is no longer supported. Please use the [Email Connector](https://marketplace.mendix.com/link/component/120739) module instead. diff --git a/content/en/docs/releasenotes/studio-pro/8/8.18.md b/content/en/docs/releasenotes/studio-pro/8/8.18.md index f06c2671359..8f20504a820 100644 --- a/content/en/docs/releasenotes/studio-pro/8/8.18.md +++ b/content/en/docs/releasenotes/studio-pro/8/8.18.md @@ -20,7 +20,6 @@ weight: 82 * We fixed a security issue related to importing modules into Studio Pro. (6.1 – CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N – for more information see [Security Advisories](/releasenotes/security-advisories/#40592)) * We fixed an issue where Consumed Web Service caused a validation failure at runtime for WSDL files imported locally. (Ticket 146066) - ## 8.18.34 {#81834} **Release date: April 24, 2025** 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 1dc592c42a7..3f4cbba932e 100644 --- a/content/en/docs/releasenotes/studio-pro/9/9.24.md +++ b/content/en/docs/releasenotes/studio-pro/9/9.24.md @@ -30,8 +30,7 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 9 release for a ### Known Issues * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](/refguide9/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](/refguide9/version-control-menu/#show-changes) dialog box. - * Workaround: For details, see [this section](/refguide9/troubleshoot-git-issues/#css-error) in *Troubleshooting Version Control*. - + * Workaround: For details, see [this section](/refguide9/troubleshoot-git-issues/#css-error) in *Troubleshooting Version Control*. ## 9.24.35 {#92435}