Merge branch 'Mendix-11' into qt-privatevaluescommand

Author: quinntracy

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/studio-pro/extensibility-api/csharp/extensibility-api-howtos/_index.md

@@ -9,4 +9,4 @@ description_list: true
 
 ## Introduction
 
-The following how-tos teach you how to use the Extensibility API for C# Developers in different use cases.
+The following how-tos teach you how to use the Extensibility API for C# Developers in different use cases.

content/en/docs/apidocs-mxsdk/apidocs/studio-pro/extensibility-api/packaging-your-extension.md

@@ -26,4 +26,4 @@ Once the add-on module is available to a Studio Pro user, they are now able to a
 
 Once an add-on module containing an extension is imported in the app, Studio Pro will show a warning to the user, asking to trust the extension contained in it. If the user does not choose to trust, the module will still be imported but the extension inside it won't be loaded.
 
-![Trust Extension](/attachments/apidocs-mxsdk/apidocs/extensibility-api/trustExtension.png)
+![Trust Extension](/attachments/apidocs-mxsdk/apidocs/extensibility-api/trustExtension.png)

content/en/docs/apidocs-mxsdk/apidocs/studio-pro/extensibility-api/web/web-extensions-howtos/menu-api.md

@@ -83,7 +83,6 @@ The menu has the following properties:
 
 {{< figure src="/attachments/apidocs-mxsdk/apidocs/extensibility-api/web/menus/grouped_menus.png" >}}
 
-
 ## Creating a Menu with Submenus
 
 You can also have a number of submenus that branch out your menu.

content/en/docs/apidocs-mxsdk/apidocs/studio-pro/runtime-api.md

@@ -11,6 +11,7 @@ Extend your application model using Java. All functionality and information from
 
 ## Mendix Runtime API
 
+* [Mendix 11 Runtime API](https://apidocs.rnd.mendix.com/11/runtime/index.html)
 * [Mendix 10 Runtime API](https://apidocs.rnd.mendix.com/10/runtime/index.html)
 * [Mendix 9 Runtime API](https://apidocs.rnd.mendix.com/9/runtime/index.html)
 * [Mendix 8 Runtime API](https://apidocs.rnd.mendix.com/8/runtime/index.html)

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

@@ -6,7 +6,7 @@ description: "Presents documentation for Mendix SDKs, including Mendix Platform
 ---
 
 {{% alert color="warning" %}}
-Mendix Platform SDK versions below 5.0 are deprecated. They depend on the [Projects API](/apidocs-mxsdk/apidocs/projects-api/) which will be removed early in 2024. A firm date will be communicated once a decision has been made.
+Mendix Platform SDK versions below 5.0 are deprecated.
 {{% /alert %}}
 
 ## Introduction

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

@@ -48,7 +48,6 @@ For an explanation on this topic, see [How to Manipulate Existing Models](/apido
 Some more explanation on manipulating existing models can be found in these documents:
 
 * [How to Change Things in the Model](/apidocs-mxsdk/mxsdk/changing-things-in-the-model/)
-* [How to Close the Server Connection](/apidocs-mxsdk/mxsdk/closing-the-server-connection/)
 * [How to Find Things in the Model](/apidocs-mxsdk/mxsdk/finding-things-in-the-model/)
 * [How to Load Units and Elements](/apidocs-mxsdk/mxsdk/loading-units-and-elements/)
 

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/creating-the-domain-model.md

@@ -54,7 +54,7 @@ customer.location = { x: 100, y: 100 };
 With these ingredients, you can create the two entities. Replace the snippet that creates a single entity in the script that you created in the [previous how-to steps](/apidocs-mxsdk/mxsdk/creating-your-first-script/) with the following snippet to create the two new entities:
 
 ```ts
-const domainModel = await loadDomainModel(workingCopy); 
+const domainModel = await domainModelInterface.load();
 const customer = domainmodels.Entity.createIn(domainModel);
 customer.name = `Customer`;
 customer.location = { x: 100, y: 100 };
@@ -148,14 +148,16 @@ In the Model SDK, the [`Entity.generalization`](https://apidocs.rnd.mendix.com/m
 So, to set up entity `Customer` as a specialization of entity `Administration.Account`, you first need to look up the `Account` entity which [can be done in several ways](/apidocs-mxsdk/mxsdk/finding-things-in-the-model/). The following snippet looks up the `Account` entity in the `Administration` domain model, using the `findEntityByQualifiedName` function:
 
 ```ts
-const systemUser = workingCopy.model().findEntityByQualifiedName(`Administration.Account`);
+const systemUser = model.findEntityByQualifiedName(`Administration.Account`);
 ```
 
 The `domainmodels.Generalization` instance that will be used to configure the `Account` instance can now be created. The `generalization` property is set to the `System.User` entity instance that was looked up:
 
 ```ts
-const generalization = domainmodels.Generalization.createIn(customer);
-generalization.generalization = systemUser;
+if(systemUser){
+    const generalization = domainmodels.Generalization.createIn(customer);
+    generalization.generalization = systemUser;
+}
 ```
 
 Together, the creation of the `Customer` entity will look like the following code snippet. Replace the creation of the `customer` entity instance in the script with the following snippet:
@@ -166,8 +168,10 @@ customer.name = `Customer`;
 customer.location = { x: 100, y: 100 };
 
 const generalization = domainmodels.Generalization.createIn(customer);
-const systemUser = workingCopy.model().findEntityByQualifiedName(`Administration.Account`);
-generalization.generalization = systemUser;
+const systemUser = model.findEntityByQualifiedName(`Administration.Account`);
+if (systemUser) {
+    generalization.generalization = systemUser;
+}
 ```
 
 ### Resources

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/creating-your-first-script.md

@@ -47,6 +47,10 @@ After setting up all the prerequisites, you can start writing a first script tha
 
 Don't forget to [set up your personal access token](/apidocs-mxsdk/mxsdk/set-up-your-pat/) before executing the script.
 
+{{% alert color="warning" %}}
+Working copy creation is a resource-intensive process. Consider reusing previously-created ones by invoking `app.getOnlineWorkingCopy(workingCopyId)`. All working copies are automatically deleted after 24 hours.
+{{% /alert %}}
+
 ### Code Explanation
 
 Here are some explanations about the script:

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/manipulating-existing-models/changing-things-in-the-model.md

@@ -106,4 +106,4 @@ All the parts of a *deleted* element are also *deleted* and cannot be accessed.
 
 ## Next Step
 
-Continue with [How to Close the Server Connection](/apidocs-mxsdk/mxsdk/closing-the-server-connection/).
+Continue with [How to Find Things in the Model](/apidocs-mxsdk/mxsdk/finding-things-in-the-model/).