Merge branch 'mendix:development' into development

Author: atul-lahade-mx

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md

@@ -485,6 +485,39 @@ if (selection.type === "Single") {
 
 ## Exposed Modules
 
+ ### Session {#session}
+
+The Mendix Platform exposes a `mendix/session` module for inspecting the current user session. It is available in both web and native.
+
+For instance, `getUserId` returns the current user's GUID as a `string`.
+
+```ts
+function getUserId(): GUID;
+```
+
+---
+
+### Parser {#parser}
+
+The Mendix Platform exposes a `mendix/parser` module that provides locale-aware formatting and parsing of attribute values. These functions use the same locale and formatting settings of the built-in Mendix widgets. It is available in both web and native.
+
+```ts
+import { formatValue, parseValue } from "mendix/parser";
+```
+
+Both functions accept an optional configuration object:
+
+```ts
+interface FormatValueConfig {
+    selector?: "date" | "time" | "datetime";
+    datePattern?: string;
+    places?: number;
+    groups?: boolean;
+}
+```
+
+For the reference of the API, you can refer to the [API documentation](https://apidocs.rnd.mendix.com/11/client-mx-api/module-mx-api_parser.html).
+
 ### Icon {#icon}
 
 Mendix Platform exposes two versions of an `Icon` react component: `mendix/components/web/Icon` and `mendix/components/native/Icon`. Both components are useful helpers to render `WebIcon` and `NativeIcon` values respectively. They should be passed through an `icon` prop. The native `Icon` component additionally accepts `color` (`string`) and `size` (`number`) props.

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/pluggable-widgets-client-apis-list-values.md

@@ -197,6 +197,12 @@ It is possible to set filtering conditions for items of a datasource. `setFilter
 
 Some examples of builder functions are `equals`, `greaterThan`, `lessThanOrEqual` for filtering on `DateTime` or `Decimal` attributes. Functions like `startsWith`, `contains` are useful for filtering on `String` attributes. Filtering based on associations is also possible. For example, you can use `equals` with references and `contains` with reference sets.
 
+To use the filter builders in a pluggable widget, import the individual builder functions you need directly from the "mendix/filters/builders" module path:
+
+```ts
+import { attribute, literal, equals, startsWith, and, or } from "mendix/filters/builders";
+```
+
 The following code samples show how to use filter builders and apply filtering to a data source property with three linked attributes and two linked associations:
 
 ```ts

content/en/docs/developerportal/project-management/jira-connector.md

@@ -23,7 +23,7 @@ If you are a Scrum Master of a Mendix app, you can link your app to Jira if you
     * For a team-managed board, the **Stories** pane shows all stories from your board, which may include your backlog. If you do not wish to see backlog stories in Studio Pro, consider setting up your board without a backlog, and using a separate board to manage your backlog.
 
 * Allows you to change the status of a story or mark a task as **Done** from the [Stories pane](/refguide/stories-pane/) in Studio Pro.
-* Converting your [feedback items](/developerportal/app-insights/feedback/) in App Insights will result in a story in Jira.
+* Converting your [feedback items](/developerportal/app-insights/feedback/) in App Insights results in a story in Jira.
 
 ## Limitations
 
@@ -32,15 +32,16 @@ As we further develop this feature, we may lift these limitations with future re
 {{% /alert %}}
 
 * Feedback issues, and stories from Epics are not migrated to Jira.
-* When a feedback item is being converted to an issue, the story type, title, and description of the issue will be set. If your Jira configuration requires additional mandatory fields, this process might not work.
+* When a feedback item is being converted to an issue, the story type, title, and description of the issue are set. If your Jira configuration requires additional mandatory fields, this process might not work.
 
 ## Prerequisites
 
 * You need to have the [Scrum Master](/developerportal/general/app-roles/#team-roles) role for the app.
 * You need to have an active subscription to Jira Software Cloud.
+      {{% alert color="info" %}} Local or on-premises installations are not supported.{{% /alert %}}
 * You need to have a project in Jira with a Scrum board, a Kanban board, or a team-managed board.
-* You need to have a user account and API token with administration rights to the project in Jira. For more information on how to get this API token, see [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
-* To convert feedback items to stories in Jira, your project in Jira must have the issue types "Story" and "Bug". For more information on how to set up issue types for your project, see [Associate issue types with projects](https://support.atlassian.com/jira-cloud-administration/docs/associate-issue-types-with-projects/).
+* You need to have a user account and API token with administration rights to the project in Jira. For more information on how to get this API token, refer to [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
+* To convert feedback items to stories in Jira, your project in Jira must have the issue types **Story** and **Bug**. For more information on how to set up issue types for your project, refer to [Associate issue types with projects](https://support.atlassian.com/jira-cloud-administration/docs/associate-issue-types-with-projects/).
 
 ## Procedure
 
@@ -55,10 +56,10 @@ To connect your app to Jira, perform the following steps:
 4. Click **Connect Jira**. The **Set Up Jira Configuration** dialog box opens.    
    Fill in the information as follows:
 
-    * **URL Jira Environment**: This is the URL of your company’s environment within the Jira platform, as provided by Jira. This URL usually looks like this: `https://my-company.atlassian.net`.
-    * **Project Key**: This is the unique key of your project within the Jira platform.
-    * **Admin User**: This is the login name of a user on the Jira platform with project administration rights.
-    * **API Token**: This is a valid API token issued by the Jira platform and assigned to the above-mentioned admin user. For more information on how to get this API token, see [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
+    * **URL Jira Environment** – This is the URL of your company’s environment within the Jira platform, as provided by Jira. This URL usually looks like this: `https://my-company.atlassian.net`.
+    * **Project Key** – This is the unique key of your project within the Jira platform.
+    * **Admin User** – This is the login name of a user on the Jira platform with project administration rights.
+    * **API Token** – This is a valid API token issued by the Jira platform and assigned to the above-mentioned admin user. For more information on how to get this API token, refer to [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
 
 5. Click **Next**. 
 
@@ -72,7 +73,7 @@ Once the activation is completed, your app is connected to Jira. You can see the
 
     * If you connect your app to a Scrum board in Jira, the **Stories** pane shows all stories from all your active Sprints.
     * If you connect your app to a Kanban board, the **Stories** pane shows all stories from your board, taking the filter and sub-query of the board settings into account, ordered by story key.
-        * You can find the filters and sub-query in the board settings in Jira (for more information, see [Configure a company-managed board](https://support.atlassian.com/jira-software-cloud/docs/configure-a-company-managed-board/)).
+        * You can find the filters and sub-query in the board settings in Jira. For more information, refer to [Configure a company-managed board](https://support.atlassian.com/jira-software-cloud/docs/configure-a-company-managed-board/)).
     * If you connect your app to a team-managed board, the **Stories** pane shows all stories from your board, which may include your backlog.
     * If you do not wish to see backlog stories in Studio Pro, consider setting up your board without a backlog, and using a separate board to manage your backlog.
     * The list of stories is ordered by the Jira story key.
@@ -90,6 +91,6 @@ After you activated the Jira connector, you can review the configuration details
 
 If you need to connect to a different Jira environment, or need to rotate the API key used by the Jira connector, click **Edit Connection Details**. If you want to switch to a different Jira board within the same environment, click **Change Board**.
 
-In order for the Jira connector to work, Mendix caches some information from your Jira board in our system. This include the name of the estimation field that you use to set story points, as well as the status schema that you use in your board. If this information changes in Jira, you may need to refresh the cache by clicking **Reconnect**.
+In order for the Jira connector to work, Mendix caches some information from your Jira board in our system. This includes the name of the estimation field that you use to set story points, as well as the status schema that you use in your board. If this information changes in Jira, you may need to refresh the cache by clicking **Reconnect**.
 
-If you no longer wish to use the Jira connector, simply click **Deactivate Connection**. This will revert your project management tool automatically to [Epics](/developerportal/project-management/epics/).
+If you no longer wish to use the Jira connector, simply click **Deactivate Connection**. This reverts your project management tool automatically to [Epics](/developerportal/project-management/epics/).

content/en/docs/refguide/mendix-ai-assistance/maia-make/_index.md

@@ -72,6 +72,7 @@ The following table lists the general capabilities of Maia Make and the Studio P
 | Folder structure support | Organizes new documents into existing folders and follows your established folder hierarchy when generating content. | Studio Pro 11.10 | Not supported for pages. |
 | Themes and styling | Allows Maia to modify theme variables, create custom styling, and manage design properties. | Studio Pro 11.12 | |
 | Markdown attachment support | Allows you to provide Markdown documents as input to help Maia better understand your requirements. | Studio Pro 11.12 | |
+| Explain and solve consistency errors | Allows you to use Maia to explain or solve problems by right-clicking the item in the **Errors** pane. | Studio Pro 11.12.1 | |
 
 ## Using Maia Make Capabilities
 

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

@@ -63,20 +63,31 @@ Solution modules are only used for developing a solution and are an inseparable
 
 When the module is set as the solution module, it gets the letter **S** as an icon.
 
-### Module Version
+### Module Version {#module-version}
 
 {{% alert color="info" %}}
 Version is available for all module types for Studio Pro 11.12 and above. In earlier versions of Studio Pro, version is available only for add-on and solution module types. 
 {{% /alert %}}  
 
-This is the version number of the module. The version should be a semantic version, consisting of at least three parts: major, minor, and patch version. For more information on semantic versions, see [Semantic Versioning](https://semver.org/).
+This is the version number of the module which is shown in various places in the Studio Pro user interface, as well as in the Marketplace. 
 
-Mendix recommends setting a new version every time you make changes to the module. For modules that will be published to the Marketplace, the version must be set before exporting the package.
+When redistributing a module, you should always change the version number when changes are made. For modules that will be published to the Marketplace, the version must be set before exporting the package.
 
 {{% alert color="info" %}}
 The Marketplace automatically uses the version from the exported package. You cannot change this manually. If the version is already in use, the Marketplace rejects the package.
 {{% /alert %}}  
 
+#### Version format
+
+The version should be a semantic version, consisting of at least three numerical parts: major, minor, and patch version, such as *1.3.7*.
+Refer to the following guidance when changing the version number:
+
+* Increase the major version when making breaking changes, such as removing a functionality like an entity or a microflow, or upgrading the module to a new major version of Studio Pro.
+* Increase the minor version when adding new features in a backward compatible manner. For example, when adding a microflow or entity that do not interfere with existing behavior.
+* Increase the patch version when making backward compatible bug fixes, such as fixing a styling issue on a page or changing a calculation in a microflow without changing the parameters and output type.
+
+Next to the numerical major, minor and patch version, alphanumerical characters are allowed. This is considered to be an advanced feature, for more information, please see [Semantic Versioning](https://semver.org/). An example of an advanced version number is *1.3.7-beta.2*.
+
 ## Package {#package}
 
 {{% alert color="info" %}}

content/en/docs/refguide/runtime/mendix-client/embedding-the-client.md

@@ -180,12 +180,6 @@ If the host app uses CSP, make sure its policy allows JavaScript to load from th
 
 Cross-site cookies must be enabled in the browser when the Mendix application is hosted on a different domain from the host application.
 
-## Known Issues
-
-### Optional Parameters
-
-Omitting a parameter that is marked as optional from the `parameters` object will result in the fallback page being shown instead of the default value being passed.
-
 ## Read More
 
 * [Mendix Client](/refguide/mendix-client/)

content/en/docs/refguide/runtime/mendix-client/mendix-inside-teamcenter.md

@@ -229,7 +229,6 @@ For the full `render()` API, see [Embedding the Client](/refguide/mendix-client/
 ## Known Limitations (Beta)
 
 * **Authentication pop-up:** During Beta, the Teamcenter Connector SSO flow opens a pop-up window. This can be automated to require zero additional clicks after the user is already authenticated with TcSS.
-* **Optional parameters fallback:** If an optional startup parameter is omitted, the embedded client shows the fallback page rather than using the parameter's default value. This is a known issue with the embedded client. See [Embedding the Client](/refguide/mendix-client/embedding-the-client/).
 
 ## Read More
 

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

@@ -5,6 +5,7 @@ description: "The release notes for Mendix Studio Pro 10.21 (including all patch
 weight: 79
 # KI: "Runtime-only changes": UFC-1647
 # KI: "The debugger does not reconnect": UFC-1644
+# KI: "t is not a function": Zendesk Problem 282636
 ---
 
 {{% alert color="info" %}}For highlights of this release, see the [Mendix Release 10.21](https://www.mendix.com/blog/mendix-release-10-21-ai-ai-ai-boosting-developer-productivity/) blog post.{{% /alert %}}
@@ -27,6 +28,9 @@ weight: 79
     * Fixed in [10.24.4](/releasenotes/studio-pro/10.24/#fix-debugger-runtime-only) and [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-runtime-only).
 * In the React client, the debugger does not reconnect when restarting an app.
     * Fixed in [10.24.4](/releasenotes/studio-pro/10.24/#fix-debugger-reconnect) and [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-reconnect).
+* A known issue occurs in two ways due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150:
+    * When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
+    * When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
 
 ## 10.21.0 {#10210}
 
@@ -198,3 +202,6 @@ This improvement simplifies widget code. Widget developers no longer need to set
     * Fixed in [10.24.4](/releasenotes/studio-pro/10.24/#fix-debugger-runtime-only) and [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-runtime-only).
 * In the React client, the debugger does not reconnect when restarting an app.
     * Fixed in [10.24.4](/releasenotes/studio-pro/10.24/#fix-debugger-reconnect) and [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-reconnect).
+* A known issue occurs in two ways due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150:
+    * When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
+    * When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.

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

@@ -5,6 +5,7 @@ description: "The release notes for Mendix Studio Pro 10.22 (including all patch
 weight: 78
 # KI: "Runtime-only changes": UFC-1647
 # KI: "The debugger does not reconnect": UFC-1644
+# KI: "t is not a function": Zendesk Problem 282636
 ---
 
 {{% alert color="info" %}}For highlights of this release, see the [Mendix Release 10.22](https://www.mendix.com/blog/mendix-release-10-22-and-11-0-beta-1/) blog post.{{% /alert %}}
@@ -126,3 +127,6 @@ weight: 78
 * In the React client, the debugger does not reconnect when restarting an app.
     * Fixed in [10.24.4](/releasenotes/studio-pro/10.24/#fix-debugger-reconnect) and [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-reconnect).
 * When loading a view entity without entity access applied, an exception is thrown if it is then used in a context requiring entity access. (Tickets 257900, 259602, 260557)
+* A known issue occurs in two ways due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150:
+    * When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
+    * When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.

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

@@ -5,6 +5,7 @@ description: "The release notes for Mendix Studio Pro 10.23 (including all patch
 weight: 77
 # KI: "Runtime-only changes": UFC-1647
 # KI: "The debugger does not reconnect": UFC-1644
+# KI: "t is not a function": Zendesk Problem 282636
 ---
 
 {{% alert color="info" %}}For highlights of this release, see the [Mendix Release 10.23](https://www.mendix.com/blog/mendix-release-10-23-and-11-0-beta-2/) blog post.{{% /alert %}}
@@ -76,3 +77,6 @@ weight: 77
     * Fixed in [10.24.4](/releasenotes/studio-pro/10.24/#fix-debugger-runtime-only) and [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-runtime-only).
 * In the React client, the debugger does not reconnect when restarting an app.
     * Fixed in [10.24.4](/releasenotes/studio-pro/10.24/#fix-debugger-reconnect) and [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-reconnect).
+* A known issue occurs in two ways due to the `t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support.` error introduced by Microsoft Edge WebView 2 version 150:
+    * When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
+    * When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.