From 6e4ba09eadd12bb397c1193fefb3765e4b59803f Mon Sep 17 00:00:00 2001 From: Arjo Bruijnes Date: Thu, 18 Jun 2026 09:20:34 +0200 Subject: [PATCH 1/4] Bonus: Remove references to Mx10 in Mx11 documentation --- .../pluggable-widgets/pluggable-widgets-client-apis/_index.md | 2 +- .../pluggable-widgets-client-apis-list-values.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md index c41be071670..879b3204659 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md @@ -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. weight: 20 aliases: - /apidocs-mxsdk/apidocs/client-apis-for-pluggable-widgets diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/pluggable-widgets-client-apis-list-values.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/pluggable-widgets-client-apis-list-values.md index 149bcaccd74..0dc22d6daeb 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/pluggable-widgets-client-apis-list-values.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/pluggable-widgets-client-apis-list-values.md @@ -1,7 +1,7 @@ --- title: "List Values" url: /apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/ -description: A guide to understanding the list of objects for the datasource property in Mx10. +description: A guide to understanding the list of objects for the datasource property. --- ## Introduction From 196a696e7e4bcb39afeb06219dd44f493c9fbf83 Mon Sep 17 00:00:00 2001 From: Arjo Bruijnes Date: Wed, 2 Jul 2025 14:14:04 +0200 Subject: [PATCH 2/4] Document auto-mapping primitive variables --- .../pluggable-widgets/pluggable-widgets-property-types.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) 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 544224a055d..d32e55e09ce 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 @@ -484,6 +484,8 @@ If a `dataSource` attribute is not specified, the client will receive an `Action When a `dataSource` attribute is specified and configured by the user, it is passed as a [`ListActionValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listactionvalue). For more information, see the [Datasource](#datasource) section below. +Action properties can be preconfigured using the `defaultValue` and `defaultType` attributes. This is particularly useful when the widget is intended to be used with a specific microflow, nanoflow, or page. When the property [exposes action variables](#action-xml-elements), they are automatically mapped to parameters of matching name and type. + #### XML Attributes {#xml-attributes} | Attribute | Required | Attribute Type | Description | @@ -496,7 +498,7 @@ When a `dataSource` attribute is specified and configured by the user, it is pas #### XML Elements {#action-xml-elements} -`` — Defines variables a widget provides when calling [execute() on an ActionValue](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#execute). The variables are made available in Studio Pro when configuring [Call a Microflow](/refguide/on-click-event/#call-microflow) and [Call a Nanoflow](/refguide/on-click-event/#call-nanoflow) actions. +`` — Defines variables a widget provides when calling [execute() on an ActionValue](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#execute). The variables are made available in Studio Pro when configuring [Call a Microflow](/refguide/on-click-event/#call-microflow) and [Call a Nanoflow](/refguide/on-click-event/#call-nanoflow) actions. Action variables are automatically mapped to parameters of the same name (`key`) and type. `` (required one or more) — Represents a primitive value provided by the widget as an argument when calling `ActionValue.execute()`. The variable is defined by the following attributes: From ba1b3a5f9ae219b82b3761d9810a6170e1ed7467 Mon Sep 17 00:00:00 2001 From: Arjo Bruijnes Date: Wed, 2 Jul 2025 14:14:25 +0200 Subject: [PATCH 3/4] Bonus: Add link to relevant type --- .../pluggable-widgets/pluggable-widgets-property-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 d32e55e09ce..b0bdaeff555 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 @@ -480,7 +480,7 @@ Then the Studio Pro UI for the property appears like this: 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. +If a `dataSource` attribute is not specified, the client will receive an [`ActionValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#actionvalue) representing the action or `undefined` if the **Do nothing** action was selected. When a `dataSource` attribute is specified and configured by the user, it is passed as a [`ListActionValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listactionvalue). For more information, see the [Datasource](#datasource) section below. From 2f8af983baf0ad4b58756a7c86dd605a6c4c567b Mon Sep 17 00:00:00 2001 From: Arjo Bruijnes Date: Mon, 14 Jul 2025 12:30:46 +0200 Subject: [PATCH 4/4] Update documentation describing argument mappings for document calls --- content/en/docs/refguide/modeling/pages/on-click-event.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/en/docs/refguide/modeling/pages/on-click-event.md b/content/en/docs/refguide/modeling/pages/on-click-event.md index f87cf9f2d3c..6f0be9702ec 100644 --- a/content/en/docs/refguide/modeling/pages/on-click-event.md +++ b/content/en/docs/refguide/modeling/pages/on-click-event.md @@ -138,9 +138,7 @@ This duplicates the [Microflow](#microflow) specified above. ##### Microflow Arguments -**Microflow arguments** are automatically configured based on the parameters of the selected microflow and the available arguments. In general arguments are taken from any enclosing data widget. If the data widget enclosing the widget calling a microflow is inside another (nested) data widget, then objects from that data widget and any others in which it is nested can also be passed. - -If the microflow is triggered within a grid and has an object list parameter, the objects which are passed in the list depend on the selection mode of the grid. Simple multi-selection allows for either all rows or selection, and defaults to selection. This can be configured via the drop-down menu in the microflow settings page. A grid with single selection always passes all rows to the microflow. +**Microflow arguments** specify the values that are passed as parameters when the microflow is called. Each argument can be defined using an expression or by choosing a variable that is available on the page. Variables are exposed by the widget itself, surrounding data widgets, a widget with selection, page variables, and page parameters. When the [**Microflow**](#microflow) is set, arguments are automatically filled for parameters with clear candidate variables. For example, because the name of the variable matches that of the parameter, or only one variable of the parameter's type is available. ##### Microflow Call Type @@ -225,7 +223,7 @@ Set the **Nanoflow** property to specify a [nanoflow](/refguide/nanoflow/) that You can either select an existing nanoflow or create a new nanoflow by clicking the **New** button from the **Select Nanoflow** dialog box. -When creating a new nanoflow, a dialog box is shown where you can set the name and select parameters for the new nanoflow. You can choose the data view, snippet, page parameter, or available selection from which the parameter must be created in the new nanoflow. +**Nanoflow arguments** specify the values that are passed as parameters when the nanoflow is called. Each argument can be defined using an expression or by choosing a variable that is available on the page. Variables are exposed by the widget itself, surrounding data widgets, a widget with selection, page variables, and page parameters. When the **Nanoflow** is set, arguments are automatically filled for parameters with clear candidate variables. For example, because the name of the variable matches that of the parameter, or only one variable of the parameter's type is available. If there is nothing to pass to the new nanoflow, then a dialog box is shown where you can only specify the name of the nanoflow.