Merge branch 'development' into nc-audit-logging-ga

Author: NicoletaComan

.github/workflows/vale.yml

@@ -1,6 +1,6 @@
 name: Vale Linting
 
-# Trigger on PRs that change Markdown files
+# Trigger on PRs that change Markdown files (but skip run on draft PRs)
 on:
   pull_request:
     types: [opened, synchronize, reopened, ready_for_review]

content/en/docs/apidocs-mxsdk/apidocs/marketplace/_index.md

@@ -0,0 +1,11 @@
+---
+title: "APIs for Marketplace"
+url: /apidocs-mxsdk/apidocs/apis-for-marketplace/
+type: swagger
+no_list: false
+description_list: true
+description: "Provides the documentation of APIs for Marketplace."
+linktitle: "Marketplace"
+---
+
+Mendix offers the following APIs for Marketplace:

…ocs/apidocs-mxsdk/apidocs/content-api.md …mxsdk/apidocs/marketplace/content-api.mdcontent/en/docs/apidocs-mxsdk/apidocs/content-api.md renamed to content/en/docs/apidocs-mxsdk/apidocs/marketplace/content-api.md content/en/docs/apidocs-mxsdk/apidocs/content-api.md renamed to content/en/docs/apidocs-mxsdk/apidocs/marketplace/content-api.md

@@ -1,11 +1,10 @@
 ---
-title: "Content API"
-linktitle: "Marketplace Content"
+title: "Marketplace Content API"
 url: /apidocs-mxsdk/apidocs/content-api/
 type: swagger
 description: "The Content API accesses both public and company-specific Marketplace content information."
 restapi: true
-weight: 45
+weight: 10
 ---
 
 ## Introduction
@@ -22,7 +21,7 @@ If you have Marketplace content, this API can help you get the following informa
 
 ### Generating a PAT
 
-For details on how to generate a PAT, see the [Personal Access Tokens](/portal/user-settings/#pat) section of *User Settings*.
+For details on how to generate a PAT, refer to the [Personal Access Tokens](/portal/user-settings/#pat) section of *User Settings*.
 
 Select at least the following as the **Marketplace** scope:
 
@@ -39,7 +38,7 @@ GET /content HTTP/1.1
 Authorization: MxToken 7LJE…vk
 ```
 
-To authenticate calls when using the OpenAPI specification below, click **Authorize** and use the value `MxToken {GENERATED_PAT}`.
+To authenticate calls when using the OpenAPI specification included in the next section, click **Authorize** and use the value `MxToken {GENERATED_PAT}`.
 
 ## API Reference
 

content/en/docs/apidocs-mxsdk/apidocs/marketplace/publish-api.md

@@ -0,0 +1,44 @@
+---
+title: "Marketplace Publish API"
+url: /apidocs-mxsdk/apidocs/publish-api/
+type: swagger
+description: "The Publish API accesses both public and company-specific Marketplace content information."
+restapi: true
+weight: 20
+---
+
+## Introduction
+
+The Marketplace Publish API allows you to manage the releases of your Marketplace components. It provides endpoints to create new releases with version metadata, upload source files, check release status as it moves through review and publication workflows, and unpublish releases when needed.     
+The API handles both public and private components.
+
+{{% alert color="warning" %}}
+You can currently only publish new releases of existing components.
+{{% /alert %}}
+
+## Authentication {#authentication}
+
+### Generating a PAT
+
+For details on how to generate a PAT, refer to the [Personal Access Tokens](/portal/user-settings/#pat) section of *User Settings*.
+
+Select at least the following as the **Marketplace** scope:
+
+* `mx:marketplace:write`
+
+Store the generated value `{GENERATED_PAT}` somewhere safe so you can use it to authorize your Content API calls.
+
+### Using the PAT
+
+Each request must contain an `Authorization` header with the value `MxToken {GENERATED_PAT}`. Here is an example:
+
+```http
+GET /content HTTP/1.1
+Authorization: MxToken 7LJE…vk
+```
+
+To authenticate calls when using the OpenAPI specification included in the next section, click **Authorize** and use the value `MxToken {GENERATED_PAT}`.
+
+## API Reference
+
+{{< swaggerui-disable-try-it-out src="/openapi-spec/marketplace-publish.yaml"  >}}

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

@@ -69,7 +69,8 @@ A widget package file is just a ZIP archive containing the following things:
     * *{widgetName}.tile.png* sets the tile image inside the Studio Pro toolbox in tile view (the ideal image size is 256x192 pixels, but other sizes will be resized to fit)
     * *{widgetName}.tile.dark.png* sets the dark-mode equivalent to *{widgetName}.tile.png*
 * Optionally, some widget-related resources, preferably located next to the file which contains the client component
-    * Note that all CSS files you add (except the one located in the **lib** sub-directory) will automatically be loaded in an app via the widget
+    * All CSS files you add (except the ones located in the **lib** sub-directory) will automatically be loaded in an app via the widget.
+    * When the React client is enabled for an app, any `assets` directories in a widget package are automatically copied to the widget's directory under `dist` during bundling. This ensures that all asset files from a pluggable widget are included in the final build and available at runtime.
 
 Naming your widget package file after the `widgetName` is best practice. Also, a widget package can include multiple widgets by putting several of the above items in the same widget package. However, creating such packages is *not recommended*. 
 

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

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

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md

@@ -480,10 +480,12 @@ 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.
 
+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}
 
-`<actionVariables>` — 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.
+`<actionVariables>` — 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.
 
 `<actionVariable>` (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:
 

content/en/docs/control-center/marketplace/submitted-requests.md

@@ -16,7 +16,7 @@ The **Submitted Requests** page gives you the governance capabilities to approve
 * Company guidelines assurance: It enables you to meet regulatory requirements and internal policies by thoroughly reviewing components.
 * Efficient management: It offers a centralized approval process to save time and resources, preventing additional communication outside of the platform. 
 
-{{% alert color="info" %}}As a Mendix Admin or component owner, you can always unpublish content from the Marketplace of your organization. This can help your organization keep its private Marketplace neat, with only relevant company content. To do so, go to [Company Content](/appstore/home-page/#company-content) in the Marketplace home page, click the {{% icon name="three-dots-menu-horizontal" %}} icon on the component card, then select **Unpublish all versions**. {{% /alert %}}
+{{% alert color="info" %}}As a Mendix Admin or component owner, you can always unpublish content from the Marketplace of your organization. This can help your organization keep its private Marketplace neat, with only relevant company content. To do so, go to [Published](/appstore/home-page/#published) in the **Manage Components** section of the Marketplace home page, click **Manage Versions** in the contextual menu of the component, then select **Unpublish**. {{% /alert %}}
 
 The **Submitted Requests** page contains the following tabs: 
 

content/en/docs/control-center/security/private-connectivity/best-practices.md

@@ -15,13 +15,9 @@ Check the [Feature Release Calendar](/releasenotes/feature-release-calendar/) fo
 
 This page provides best practices for configuring and using Private Connectivity networks, agents, and resources. Following these guidelines helps ensure secure, efficient, and maintainable connections between your Mendix apps and internal infrastructure.
 
-{{% alert color="info" %}}
-Mendix uses Tailscale subnet routers to access routes in your network. In a Mendix context, these are called agents. 
-{{% /alert %}}
-
 ## Authentication Key Security 
 
-Creating an agent involves creating an authentication key. An agent registered with that authentication key can join the agent's network. If you have a production network, only use the generated authentication key for agents placed in your production network. Apply the same principle for development networks.
+Installing an agent involves creating an authentication key. An agent registered with that authentication key can join the agent's network. If you have a production network, only use the generated authentication key for agents placed in your production network. Apply the same principle for development networks.
 
 ## When to Create Networks 
 
@@ -94,12 +90,12 @@ For example, Azure Container Apps do not have privileged container access, so yo
 
 ## Advertised Routes
 
-Mendix uses Tailscale subnet routers to advertise routes to your network. This gives you full control over where the agent forwards traffic within your network.
+You need to advertise which IP addresses can be accessed by Mendix Cloud. This gives you full control over where the agent forwards traffic within your network.
 
 ### Routes to Advertise
 
 The routes you advertise depend on what your Mendix Cloud app needs to access and what you want to share:
 
 * Single resource – If your app only needs to reach one specific resource, advertise it as a `/32` route (for example, `192.168.1.10/32`).
-* App subnet – If you host all apps in one specific subnet, use the subnet router (for example, `192.168.1.0/24`).
-* Entire network – If you want to share the entire network to avoid repeatedly opening new routes, use the entire VPC or VNet subnet router (for example, `192.168.0.0/16`).
+* App subnet – If you host all apps in one specific subnet, advertise the entire subnet (for example, `192.168.1.0/24`).
+* Entire network – If you want to share the entire network to avoid repeatedly opening new routes, use the entire VPC or VNet subnet (for example, `192.168.0.0/16`).