Merge branch 'development' into olu-proofreading-about-mendix-cloud

Author: OlufunkeMoronfolu

.travis.yml

@@ -15,8 +15,9 @@ env:
   global:
 # Global variables can go here, for example HUGO_VERSION if we were using Netlify to publish.
 
-#add group: previous to see if this fixes the stalled npm build - 2025-04-14
-group: previous
+# add group: previous to see if this fixes the stalled npm build - 2025-04-14
+# remove again 2025-05-08 as builds started breaking again.
+# group: previous
 
 branches:
 # build only development and production

assets/scss/_badge.scss

@@ -40,3 +40,10 @@
     background-color: $info-1;
     color: $info-7;
 }
+
+.badge-company-approved {
+    border: solid 1px $success-9;
+    background-color: $company-approved;
+    color: $success-9;
+    padding: 2px 2px
+}

assets/scss/_variables_project.scss

@@ -20,6 +20,7 @@ $white: #fff; // YL - Override the default color defined in _variables_forward.s
 $light: #99D0FF; // DB - Blue-3 from PDS
 $dark: #0A1325; // Gray-10 from PDS (MxDock color)
 $blue: #146FF4; // YL - Mendix Blue in SP 10; Override the default color defined in _variables_forward.scss
+$company-approved: #E0FAE1; // NC - Company approved Marketplace label
 $gray-100: #f7f7f7;
 $gray-200: #f2f2f3;
 $gray-light: $gray-200;

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

@@ -9,6 +9,7 @@ aliases:
     - /apidocs/
     - /apidocs-mxsdk/apidocs/authentication/
     - /apidocs/index.html
+    - /apidocs-mxsdk/apidocs/runtime-api/
 #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
 ---
 

content/en/docs/apidocs-mxsdk/apidocs/apps/epics-api.md

@@ -43,4 +43,8 @@ To authenticate calls when using the Open API specification below, click **Autho
 
 ## API Reference
 
-{{< swaggerui src="/openapi-spec/epics.yaml"  >}}
+{{% alert color="warning" %}}
+You cannot call endpoints from the Epics API Swagger UI.
+{{% /alert %}}
+
+{{< swaggerui-disable-try-it-out src="/openapi-spec/epics.yaml"  >}}

content/en/docs/apidocs-mxsdk/apidocs/deployment/private-cloud-deploy-api.md

@@ -102,7 +102,7 @@ The API does not generate unique UUIDs for the resources. You must generate your
 
 The following sections of this document contain sample usage scenarios for the API.
 
-### Using the API to Update the Cluster and Namespace
+### Using the API to Update the Cluster and Namespace {#update-cluster}
 
 The following steps will create a cluster, register and install a namespace, add or update a cluster member, and enable development mode for the namespace.
 
@@ -125,6 +125,21 @@ The following steps will create a cluster, register and install a namespace, add
 If required, the invitation for the cluster/namespace member can be auto-accepted by setting `autoAcceptInvite` to true in the update cluster/namespace API request.
 {{% /alert %}}
 
+### Using the API to Assign a Custom Role to the Namespace Member {#assign-custom-role}
+
+Perform the following steps to create a cluster, register and install a namespace, add a custom role in the Cluster Overview page in the portal, and assign the role to the namespace member:
+
+1. Set up your authentication PAT.
+2. Prepare the manifest for both your new cluster and namespace.
+3. Configure the namespace by following steps 8-11 of [Using the API to Update the Cluster and Namespace](#update-cluster).
+4. Create a custom role in the Cluster Overview page in the portal. This role must be created only on the Portal side.
+5. Make a POST `/clusters/{namespaceId}` API call to assign the role that you created in step 4 to the namespace member.
+    You can obtain the manifest for this update request through GET `/clusters/{namespaceId}`. When updating the namespace, only the role needs to be specified for the namespace member, as the fine-grained permissions are already included in the role created in step 4.
+
+{{% alert color="info" %}}
+If required, the invitation for the cluster or namespace member can be auto-accepted by setting `autoAcceptInvite` to true in the update cluster or namespace API request.
+{{% /alert %}}
+
 ### Using the API to Restart an App {#restart}
 
 The following steps will restart an app by setting the number of instances to zero and then setting it back to the number of instances required.

content/en/docs/apidocs-mxsdk/apidocs/frontend/client-api.md

@@ -15,11 +15,15 @@ The Client API is compatible with both the React and the Dojo client.
 
 * [Mendix 10 Client API](https://apidocs.rnd.mendix.com/10/client-mx-api/index.html)
 
+{{% alert color="info" %}}
+The Mendix 10 Client API is available in Studio Pro 10.20.0 and above. For earlier versions of Studio Pro, please use the APIs listed in [Legacy Client APIs](#legacy).
+{{% /alert %}}
+
 {{% alert color="warning" %}}
 The Client API is not supported in widgets. For widget development, please use our [Pluggable Widgets API](/apidocs-mxsdk/apidocs/pluggable-widgets/)
 {{% /alert %}}
 
-## Legacy Client APIs
+## Legacy Client APIs {#legacy}
 
 * [Mendix 10 React Client API](https://apidocs.rnd.mendix.com/10/client-react/index.html)
 * [Mendix 10 Dojo Client API](https://apidocs.rnd.mendix.com/10/client/index.html)