Merge branch 'development' into qt-updateappsettings

Author: quinntracy

content/en/docs/deployment/general/mendix-pipelines.md

@@ -329,20 +329,21 @@ Mendix Pipeline failure notifications only send if the user who triggered the Me
 
 ## Additional Notes
 
-Mendix Pipelines time out if they run for more than three hours. In other words, if the operations in your Mendix Pipeline cumulatively take longer than three hours to complete, then the Mendix Pipeline will fail.
+Mendix Pipelines time out if they run for more than three hours. In other words, if the cumulative execution time of all operations in your Mendix Pipeline exceeds this limit, the Mendix Pipeline will fail.
 
-Mendix automatically creates a webhook on your behalf to trigger Mendix Pipelines based on [Teamserver push (Git)](/developerportal/deploy/webhooks/#teamserver-push-git):
+Existing Mendix Pipeline users can view previously created webhooks that trigger Mendix Pipelines from [Teamserver push (Git)](/developerportal/deploy/webhooks/#teamserver-push-git) by clicking **Webhooks** in the [navigation pane](/developerportal/#navigation-pane).
 
-* This webhook is not visible to first-time Mendix Pipeline users. 
-* For existing Mendix Pipeline users, you can view this webhook by clicking **Webhooks** in the [navigation pane](/developerportal/#navigation-pane). Do not delete this webhook. Deleting it causes failures for Mendix Pipelines that rely on the Teamserver push (Git) trigger.
+These webhooks can be safely deleted without affecting the functionality of your Teamserver push (Git) triggers and are not visible to first-time Mendix Pipeline users.
 
 ### Known Issues and Limitations
 
-Mendix Pipeline runs are not picked up and executed if the Mendix Pipelines functionality is undergoing maintenance.
+* **Mendix Pipelines maintenance behavior** – Mendix Pipeline runs are not picked up and executed if the Mendix Pipelines functionality is undergoing maintenance.
 
-It is not currently possible to add the same Mendix Pipeline step more than once in a Mendix Pipeline. This will be improved in the future.
+* **Duplicate pipeline steps not supported** – It is not currently possible to add the same Mendix Pipeline step more than once in a Mendix Pipeline. This will be improved in the future.
 
-In case of a system outage, Mendix Pipelines triggered during that time are not executed.
+* **System outages prevent pipeline execution** – In case of a system outage, Mendix Pipelines triggered during that time are not executed.
+
+* **Pipelines continue to run after app offboarding** – If an app is offboarded while pipelines are still configured, they will continue to run on their automated schedules and generate failure notifications. To prevent this, active pipelines must be deactivated during the app offboarding process, before the app is removed.
 
 ## Read More
 

content/en/docs/deployment/general/webhooks.md

@@ -162,9 +162,9 @@ Make sure to use the correct key names when using this payload information to ca
 ## Teamserver Push (Git)
 
 {{% alert color="info" %}}
-This webhook is not visible to first-time Mendix Pipeline users. 
+This webhook is not visible to first-time [Mendix Pipeline](/developerportal/deploy/mendix-pipelines/) users. 
 
-For existing Mendix Pipeline users who can view this webhook, do not delete it. Deleting it causes failures for Mendix Pipelines that rely on the Teamserver push (Git) trigger.
+Existing Mendix Pipeline users can view this webhook, but it can be safely deleted without affecting the functionality of the Teamserver push (Git) triggers.
 {{% /alert %}}
 
 When you push a model change to the [Git Team Server](/developerportal/repository/team-server/), and the webhook responds to the event **Teamserver push (Git)**, request content is sent to the configured endpoint. The request content contains a payload with the following format:

content/en/docs/marketplace/platform-supported-content/modules/mendix-feedback.md

@@ -83,10 +83,12 @@ To configure the Feedback widget, double-click it to open the **Edit Feedback**
         {{% alert color="info" %}}The original value of **App ID** is *1*, but this value should automatically change to your correct app ID. If it does not change automatically, see [Updating App ID](#update-app-id) below.
         {{% /alert %}}
 
-    * **Show advanced settings** – The advanced settings control html2canvas, a backup screen capture tool the Mendix Feedback widget uses when the default browser screenshot tool fails. By default, this is set to **No**. If you select **Yes**, the following items appear:
+    * **Show advanced settings** – These advanced settings allow you to customize where the widget renders and how screenshots are captured when the default behavior does not work as expected. By default, this is set to **No**. If you select **Yes**, the following items are displayed:
 
+        * **Target container selector** – This allows you to manually choose where the feedback widget is displayed within the app. To do that, add a CSS selector here to specify the location.    
+            By default, this field is set to `.mx-scrollcontainer-center`.
         * **Enable object rendering** – By default, this is set to **No**. Only select **Yes**, when you experience problems with creating screenshots. Then it will enable the `foreignObjectRendering` method which helps rendering complex HTML, including styles, SVGs, and embedded elements.
-        * **CSS scrollable area**– If your app does not use the default scrolling behavior in Studio Pro, the screenshot feature may not work correctly. You can add a CSS selector here to specify which element on your page scrolls the content.
+        * **CSS scrollable area** – If your app does not use the default scrolling behavior in Studio Pro, the screenshot feature may not work correctly. You can add a CSS selector here to specify which element on your page scrolls the content.
 * **Customize Button** tab
     * **Feedback and screenshot button labels** – These are the labels for the buttons on the feedback form. You can change the captions for those button here.
     * **Feedback Button Styling** – This controls how the **Feedback** button is rendered. There are three options:

content/en/docs/mendix-portal/maia-portal.md

@@ -9,7 +9,7 @@ aliases:
 
 ## Introduction
 
-Mendix AI Assistance (Maia) refers to Mendix Platform capabilities that leverage [artificial intelligence (AI)](https://www.mendix.com/glossary/artificial-intelligence-ai/) and [machine learning (ML)](https://www.mendix.com/glossary/machine-learning/) to assist developers in application development. Maia is designed to help development teams in modeling and delivering Mendix applications faster, more consistently, and with higher quality. 
+Mendix AI Assistance (Maia) refers to Mendix Platform capabilities that leverage [artificial intelligence (AI)](https://www.mendix.com/glossary/artificial-intelligence-ai/) and [machine learning (ML)](https://www.mendix.com/glossary/machine-learning/) to assist developers in application development. Maia is designed to help development teams in modeling and delivering Mendix applications faster, more consistently, and with higher quality.
 
 {{< figure src="/attachments/developerportal/global-nav/maia-mendix-portal.jpg" width="500" >}}
 
@@ -53,9 +53,9 @@ For information on Mendix data storage policies and practices for Maia, see [Mai
 
 You can access Maia Chat in Mendix Portal by clicking the **Maia** ({{% icon name="sparkles" %}}) icon to the right of the top bar.
 
-The chat interface appears at the right side of your browser window. You can start using Maia Chat either by clicking one of the demo questions or by asking your own question in the chatbox. 
+The chat interface appears at the right side of your browser window. You can start using Maia Chat either by clicking one of the demo questions or by asking your own question in the chatbox.
 
-### Asking Follow-Up Questions
+### Asking Follow-Up Questions {#follow-up}
 
 Maia Chat supports asking follow-up questions based on your previous question and the answer you have received. For example, you can ask it to summarize the latest answer you received by typing *Can you summarize that?*.
 
@@ -64,3 +64,49 @@ 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 %}}
+
+## Best Practices {#best-practices}
+
+Maia can normally provide a good answer to any question you pose. However, it may sometimes not give you the information you are looking for. You may get a better answer if you consider the following best practices.
+
+### Asking Questions in English
+
+Maia is trained on data which is primarily in English. Although Maia can cope with questions in other languages, the imprecision of (particularly machine-) translation means there is more chance of Maia misunderstanding or giving a less precise answer.
+
+### Asking Direct Questions
+
+Maia uses the Mendix documentation and the Mendix Community when producing an answer. The documentation is addressed to you, the reader, and questions to the Community are usually asked directly by the person who is asking. Maia therefore gives better answers if you put yourself in the position of asking the question.
+
+So, for example, ask "How can I do something" rather than "How can my colleague do something" or "How does Mendix do something".
+
+### Asking Specific Questions
+
+Try to make your question as specific as possible. If your question is too vague or is very general Maia can find it difficult to get the right context.
+
+### Giving Relevant Information
+
+Maia needs to know as much as possible about what you are doing. However, it can be sidetracked if you include information which is not directly relevant to what you are asking. So ensure that you do not include irrelevant information.
+
+However, do include enough information for context. For questions about errors, specific code behavior, or complex configurations, include concrete examples if possible, remembering to redact any sensitive information.
+
+For example, if you ask "How do I sign in to Mendix" it will not necessarily be clear whether you are talking about the Mendix Portal, Studio Pro, or perhaps even your deployed Mendix App, so give Maia the complete context to ensure the answer is relevant.
+
+### Using Mendix Terminology
+
+Maia will provide better answers if you use Mendix terminology which it can recognize from the documentation and Community. If you use different terms, Maia may struggle to find the right answer, and is more likely to get confused about the subject of your question.
+
+In addition, some terms in Mendix might have slightly different meanings depending on the context. If you suspect your term might be ambiguous, try to add a small clarifying detail.
+
+For example, use "Studio Pro" rather than "the IDE" when talking about working on a Mendix model. If you have a question about a Marketplace module, make sure you give the exact name of the module.
+
+### Using Follow Up Questions
+
+If Maia does not give a response which clearly answers your question, try following up to ensure that it has understood the context and terminology you are using. Try rephrasing your question, adding more details, or focusing on a different aspect of your query.
+
+### Separating Different Questions
+
+If you are asking a second, unrelated, question, start a new interaction with Maia. If you continue in the same chat with Maia, it will remember what you asked before and the answers it gave. This may lead to it using the information from the previous interactions as input to your new question. See [Asking Follow-Up Questions](#follow-up) to see when Maia keeps track of conversation history.
+
+### Looking at the Source Material
+
+Remember that Maia is an AI and can make mistakes. Maia will give references to the source of the information. The reference titles can indicate whether the information is relevant to your case, and following the links may give additional help.

content/en/docs/refguide/installation/upgrading-from-10-to-11/_index.md

@@ -101,11 +101,19 @@ In a Microflow, this distinction exists and the expression would yield `false`.
 
 Moreover, on the client side a String attribute with a value set to `empty` would be treated as if it contains `''`. This made it impossible to check in a Nanoflow whether an attribute is `empty` or if it has an empty String value `''`.
 
+#### Mendix 11.0.0
+
 In Mendix 11.0.0, we have made this behavior consistent. Now, strings are handled in the same way no matter where you use them. 
 
 We understand that this change might cause unexpected changes in existing applications migrated from older versions of Mendix. 
 
-We recommend carefully analyzing all expressions that are comparing strings against `''` or `empty` and doing extensive testing after the migration. 
+#### Mendix 11.6.3
+
+In Mendix 11.6.3, we introduced [an option](https://docs.mendix.com/refguide/app-settings/#new-string-behavior) to toggle between the old and the new client-side String attribute behaviors. Projects migrating from Mendix 10 to 11 will retain the old String behavior unless you manually switch to the new one.
+
+It is recommended to migrate your pre-existing projects to use the new behavior as soon as possible. The new behavior will improve consistency between nanoflows and microflows, which will lead to fewer bugs in your applications.
+
+Make sure to carefully analyze all expressions that are comparing strings against `''` or `empty` and do extensive testing after the migration. 
 
 #### Example 1
 

content/en/docs/refguide/modeling/app-explorer/app/app-settings/_index.md

@@ -40,6 +40,18 @@ The available configuration options are as follows:
 * **Yes**: Use the React client (default). In this mode, you will get consistency errors for incompatible widgets.
 * **Migration mode**: Use the React client and ignore incompatible widgets. Placeholders are displayed in the case of incompatible widgets. Recommended when trying out the new client.
 
+### Use New String Behavior {#new-string-behavior}
+
+{{% alert type="info" %}}
+This setting was introduced in Mendix 11.6.3. 
+{{% /alert %}} 
+
+If this option is enabled, Web (both React and Dojo) and Native Mobile clients will be able to handle both `empty` and empty string `''` values for `String` attributes. <br>
+
+If this options is disabled, `String` attribute values on the client-side will always contain only the `''` value to represent empty state. `empty` values will be automatically converted to `''` when transfered to the client-side. 
+
+For a detailed explanation, see the *Empty Strings Handling* section of [Upgrading from Mendix Studio Pro 10 to 11](/refguide/upgrading-from-10-to-11/#empty-strings-handling).
+
 ### Optimize Network Calls {#optimize-network-calls}
 
 If this option is enabled (**yes** by default), Mendix analyzes every microflow that can be triggered from the client to minimize the number of objects required to be sent. This speeds up your app significantly.

content/en/docs/refguide/modeling/mendix-ai-assistance/maia-chat.md

@@ -49,6 +49,8 @@ You can start using Maia Chat by clicking one of the demo questions. Alternative
 
 For more information on Maia Chat features in Studio Pro, see the sub-sections below.
 
+If Maia is not giving you a good answer, check the [best practices](/portal/maia/#best-practices) in *Maia in Mendix Portal*. If you still can't get a good answer, please see [Giving Feedback](#feedback), below for information on how to let Mendix know.
+
 ### Maia Chat Features in Studio Pro
 
 After a question is sent to Maia Chat, you will see the following in the chat interface:
@@ -61,7 +63,7 @@ After a question is sent to Maia Chat, you will see the following in the chat in
 * A copy icon ({{% icon name="copy" %}}) which allows you to copy the given answer to a clipboard
 * Feedback icons
 
-#### Giving Feedback
+#### Giving Feedback {#feedback}
 
 Mendix encourages giving feedback on the answers generated by Maia Chat. Feedback will be used to further improve Maia Chat.
 

content/en/docs/releasenotes/studio-pro/10/10.24.md

@@ -10,6 +10,32 @@ weight: 76
 This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for apps in production.
 {{% /alert %}}
 
+## 10.24.15 {#102415}
+
+**Release date: February 9, 2026**
+
+{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/10.24.15" text="Go to Marketplace" title="Download version 10.24.15 from the Marketplace" %}}
+
+### Improvements
+    
+- We have improved the performance of session cleanup.
+
+### Fixes
+
+- We fixed an issue where System.UserRole's **Description** attribute was not readable. (Ticket 259857)
+- We fixed an issue where the short revision hash of the commit was being sent when deploying a package. (Ticket 264621, Ticket 266012)
+- We fixed an issue in offline apps that could result in errors like "[Synchronization] SQLiteError: table mx10414574138294561$_guidToTable has no column named inaccessibleAttrs" by ensuring database migrations happen properly for all users in the client database. (Tickets 264910, 265393, 269740)
+- In the logic editors, we fixed an issue where extracted microflows did not contain all the expected parameters for a newly-created activity. (Ticket 265542)
+- We fixed an issue with the [tab container](/refguide10/tab-container/) widget. It would reset to the first tab when returning to the page, causing data sources to reload unnecessarily and other tabs to be blocked. (Tickets 266083, 266090, 267249) 
+- We fixed an issue where the last attributes were truncated in entity properties dialog boxes. (Tickets 266554, 260953, 256106, 251278, 255882)
+- We fixed an issue where an import mapping would not read JSON attribute values when a JSON attribute was preceded by another attribute with an attribute name that is a prefix (for example `StatusId` and `Status`). We also improved how JSON objects were read when one object name was a prefix of another object name. (Ticket 266571)
+- In the logic editors, we fixed an issue where a **Show Message** activity had an empty caption after initial loading of the microflow. (Ticket 268024).
+- We fixed an issue that caused setting the image of a building block to show an error dialog instead of resizing the image. (Ticket 268856)
+- We fixed an issue in Maia chat where it crashed if the **Studio Pro Version** attribute was missing in a reference.
+- We fixed scenarios in Android where navigating fields of a data view (of different types) would not be possible using an external keyboard.
+- We now parse `StdOut` and `StdError` streams separately when calling git process. This improves the stability of git operations.
+- We fixed an issue during local development where system texts would not be updated in the application when hot-reloading. They are now correctly updated without the need to fully restart the server.
+
 ## 10.24.14 {#102414}
 
 **Release date: January 16, 2026**
@@ -428,7 +454,7 @@ We have retracted version 10.24.7 due to an issue in database schema migration.
 * We fixed an issue where uploading a SVG image caused an error. (Ticket 244585)
 * We fixed an issue where the runtime log levels were not restored correctly when restarting the app from Studio Pro, in cases where the runtime had been stopped earlier due to the trial version timeout. (Ticket 251399)
 * We fixed an issue where, during module import, the widget version check was incorrectly comparing different widgets. (Ticket 252131)
-* We fixed an issue that caused a page to crash during navigation when using a Data View widget in the page with a nanoflow.(Tickets 252234, 254377, 254487)
+* We fixed an issue that caused a page to crash during navigation when using a data view widget in the page with a nanoflow. (Tickets 252234, 254377, 254487)
 * We fixed an issue with MxBuild that reported successful build before the build process had finished.  (Ticket 252729)
 * We fixed an issue in the logic editors on macOS where pressing <kbd>Command</kbd> + <kbd>C</kbd> failed to copy the selected activity to clipboard and instead changed its caption. (Ticket 253384)
 * We fixed a recurring error being caused by showing conditional hidden properties when configuring pluggable widgets through the **Properties** pane, such as Data Grid 2 columns. (Tickets 254074, 254426, 254632, 254637)