Skip to content

Draft: [WTF]: Remove Mx10 references from Mx11 Pluggable Widgets Docs #10953

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
weirdwater wants to merge 3 commits into
base: development
Choose a base branch
from
Draft

Draft: [WTF]: Remove Mx10 references from Mx11 Pluggable Widgets Docs #10953

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
651c324
Remove Introduced In 10.x callouts in 11 Pluggable Widgets docs
weirdwater Mar 31, 2026
e7dbe55
Add Introduced In 11.x callouts for Pluggable Widgets docs
weirdwater Mar 31, 2026
dde1977
Correct reference to 10 in 11 docs
weirdwater Mar 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: "Client APIs"
linktitle: "Client APIs for Pluggable Widgets"
url: /apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/
description: A guide for understanding the client APIs available to pluggable widgets in Mx10.
description: A guide for understanding the client APIs available to pluggable widgets in Mx11.
weight: 20
aliases:
- /apidocs-mxsdk/apidocs/client-apis-for-pluggable-widgets
Expand Down
24 changes: 8 additions & 16 deletions ...sdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -277,6 +277,10 @@ The user can use the optional attribute [`allowUpload`](#allow-upload) with defa

#### XML Attributes

{{% alert color="info" %}}
The `allowUpload` attribute was introduced in Mendix [11.8](/releasenotes/studio-pro/11.8/).
{{% /alert %}}

| Attribute | Required | Attribute Type | Description |
|---------------|----------|----------------|-----------------------------------------------------------------------|
| `type` | Yes | String | Must be `image` |
Expand Down Expand Up @@ -480,10 +484,6 @@ Then the Studio Pro UI for the property appears like this:

### Action {#action}

{{% alert color="info" %}}
The `defaultType` and `defaultValue` attributes for Action were introduced in Mendix [10.15](/releasenotes/studio-pro/10.15/).
{{% /alert %}}

The action property type allows a user to configure an action which can do things like call nanoflows, save changes, and open pages.

If a `dataSource` attribute is not specified, the client will receive an `ActionValue` representing the action or `undefined` if the **Do nothing** action was selected.
Expand Down Expand Up @@ -722,6 +722,10 @@ The user can use the optional attribute [`allowUpload`](#allow-upload) with defa

#### XML Attributes

{{% alert color="info" %}}
The `allowUpload` attribute was introduced in Mendix [11.8](/releasenotes/studio-pro/11.8/).
{{% /alert %}}

| Attribute | Required | Attribute Type | Description |
|---------------|----------|----------------|----------------------------------|
| `type` | Yes | String | Must be `file` |
Expand Down Expand Up @@ -767,10 +771,6 @@ Only list datasources are supported, therefore specifying `isList="true"` is req

##### Data Source Defaults {#data-source-defaults}

{{% alert color="info" %}}
The `defaultType` and `defaultValue` attributes for datasources were introduced in Mendix [10.16](/releasenotes/studio-pro/10.16/).
{{% /alert %}}

You can use the `defaultType` and `defaultValue` attributes to configure default data sources for your widget. Unless overridden in Studio Pro, the widget will attempt to configure the data source according to its defaults. Both attributes need to be set for the defaults to be applied.

The format of `defaultValue` depends on the chosen `defaultType`:
Expand All @@ -797,10 +797,6 @@ Then the Studio Pro UI for the property appears like this:

### Selection {#selection}

{{% alert color="info" %}}
The property type was introduced in Mendix [10.7](/releasenotes/studio-pro/10.7/).
{{% /alert %}}

The selection property allows a widget to read and set a selection that can be used in actions, expressions, or a `Listen to` data source of a data view.

#### XML Attributes
Expand Down Expand Up @@ -867,10 +863,6 @@ Label property allows a pluggable widget to have labeling functionality similar

#### setLabel {#setLabel}

{{% alert color="info" %}}
The `setLabel` attribute was introduced in Mendix [10.5](/releasenotes/studio-pro/10.5/).
{{% /alert %}}

You can use `setLabel` to specify which properties can be used to set the `Label` property value.

Configuring the value of a property with the `setLabel` attribute will automatically update the value of `Label`.
Expand Down