Merge branch 'development' into PLCM_Beta_Release

Author: katarzyna-koltun-mx

.github/workflows/remunusedattachments.yml

@@ -30,8 +30,8 @@ jobs:
           body: |
             "We're trying to delete some unnecessary attachments."
           branch: rem-unused-attachments
-          assignees: JohannaHemminger
-          reviewers: JohannaHemminger
+          assignees: MarkvanMents
+          reviewers: MarkvanMents
           labels: Internal WIP
           add-paths: |
             static/attachments/**

content/en/docs/apidocs-mxsdk/apidocs/deploy-api-3.md

@@ -26,7 +26,7 @@ Authentication for the Deploy API v3 uses a personal access token (PAT).
 
 ### 2.1 Generating a PAT
 
-To generate a PAT, see the [Personal Access Tokens](/developerportal/community-tools/mendix-profile/#pat) section of *Mendix Profile*.
+To generate a PAT, see the [Personal Access Tokens](/developerportal/community-tools/mendix-profile/#pat) section in *Mendix Profile*.
 
 Select the following as **Deployment Mendix Cloud** scopes:
 
@@ -58,6 +58,10 @@ The {appId} in version 3 is retrieved as the {ProjectId} from the version 1 API.
 
 The following steps will change the Technical Contact of the app identified by the UUID {appId}.
 
+{{% alert color="info" %}}
+Only Mendix Admins of the company and the current Technical Contact can give the Technical Contact role to another team member. It is currently not possible to have more than one Technical Contact for an app.
+{{% /alert %}}
+
 1. Set up your authentication PAT. You must have permission to change the Technical Contact of the app.
 1. Create a request body containing the userId of the new Technical Contact. For example, to make jane.doe@domain.tld the new Technical Contact, provide a body as shown below:
 
@@ -77,9 +81,12 @@ The following steps will change the Technical Contact of the app identified by t
 
 ### 3.2 Using the API to Change App Team Members' Access Permissions to an Environment
 
-The following steps will change the permissions of a team member to an environment of the app identified by the UUID {appId}.
+The following steps will change the permissions of a team member to an environment of the app identified by the UUID {appId}:
+
+{{% alert color="info" %}}Only the following people can change the access permissions of team members: Mendix Admins of the company, the Technical Contact of the app, and the app team members who can manage permissions.{{% /alert %}}
+
+1.  Set up your authentication PAT. You must have permission to **Manage Permissions** for the app.
 
-1. Set up your authentication PAT. You must have permission to **Manage Permissions** for the app.
 1. Call `GET /apps/{appId}/environments/{environmentId}/permissions` to get the existing Team Members' permissions for this {environmentId} of this {appId}. For example:
 
     ```http {linenos=false}

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

@@ -110,14 +110,14 @@ The following steps will create a cluster, register and install a namespace, add
 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.
 
 1. Set up your authentication PAT.
-2. Call `GET /apps/{appId}/environments/{environmentId}` to get the environment manifest for your app environment.
+2. Call `GET /apps/{appId}/namespaces/{namespaceId}/environments/{environmentId}` to get the environment manifest for your app environment.
 3. Change the `container.instances` to `0` in the manifest.
-4. Call `PUT /apps/{appId}/environments/{environmentId}` using the updated manifest.
+4. Call `PUT /apps/{appId}/namespaces/{namespaceId}/environments/{environmentId}` using the updated manifest.
 5. Verify that the job is successful using the process described in [Managing Asynchronous Jobs](#async-jobs).
 
     At this point, your app is stopped and you will not be able to access it using the `appURL`.
 6. Change the `container.instances` in the manifest to the number of instances you want to run.
-7. Call `PUT /apps/{appId}/environments/{environmentId}` using the updated manifest.
+7. Call `PUT /apps/{appId}/environments/namespaces/{namespaceId}/{environmentId}` using the updated manifest.
 8. Verify that the job is successful, as before.
 
     Your app is available once more.
@@ -140,10 +140,10 @@ The following steps will create a cluster, create a namespace, and create an env
 11. Create a `DeploymentPackage` in the Private Cloud Portal.
     You can create a deployment package by using the [Mendix for Private Cloud Build API](/apidocs-mxsdk/apidocs/private-cloud-build-api/). Once you create a deployment package, you can retrieve the `packageId` using the `GET /apps/{appId}/packages` response.
 12. Prepare a manifest for your new environment. 
-    Either use the model in the OpenAPI spec file or get the manifest of an existing environment (by calling `GET /apps/{appId}/environments/{environmentId}`, for example) and change where required. Remember to use the `{clusterID}` and `{namespace}` values for the `provider` using the cluster and namespace you have just created, and use the ID of the deployment package you have just created as the `packageId`.
+    Either use the model in the OpenAPI spec file or get the manifest of an existing environment (by calling `GET /apps/{appId}/namespaces/{namespaceId}/environments/{environmentId}`, for example) and change where required. Remember to use the `{clusterID}` and `{namespace}` values for the `provider` using the cluster and namespace you have just created, and use the ID of the deployment package you have just created as the `packageId`.
 13. Make the API call `POST /apps/{appId}/environments` using the environment manifest to create a new environment. 
 14. Verify that the job is successful using the process described in [Managing Asynchronous Jobs](#async-jobs).
-15. Now you can access the application at the `appURL` which is returned from `GET /apps/{appId}/environments/{environmentId}` of the environment.
+15. Now you can access the application at the `appURL` which is returned from `GET /apps/{appId}/namespaces/{namespaceId}/environments/{environmentId}` of the environment.
 
 ## 4 API Reference
 

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

@@ -40,7 +40,7 @@ To learn how to navigate to the main documentation sources, refer to the [How to
 
 ### 3.1 Development Workflow
 
-The script you used in the Creating your first script step was doing a full round-trip. It created an app, made it available as a working copy and committed it back to the TeamServer after making changes. Depending on what exactly you're using the SDK for (see [Use Case Examples](/apidocs-mxsdk/mxsdk/sdk-use-cases/)), this may or may not be a good idea. If you're interested in, for instance, analyzing your model, you want to start from an existing project instead of a newly created app and you won't have any changes to your model to commit.
+The script you used in the Creating your first script step was doing a full round-trip. It created an app, made it available as a working copy and committed it back to the TeamServer after making changes. Depending on what exactly you're using the SDK for (see [Use Case Examples](/apidocs-mxsdk/mxsdk/sdk-use-cases/)), this may or may not be a good idea. If you are interested in, for instance, analyzing your model, you want to start from an existing app instead of a newly created app and you will not have any changes to your model to commit.
 
 ### 3.2 How to Manipulate Existing Models
 

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/generating-code-from-the-model.md

@@ -170,7 +170,7 @@ function generate(domainModel1: domainmodels.DomainModel, model: IModel) {
 }
 ```
 
-For the next step, you will create a script that make use of the function. The script is written in TypeScript, so it will be able to run a JavaScript code just fine. This script will create a blank project and modify the domain model in the 'MyFirstModule' module.
+For the next step, you will create a script that make use of the function. The script is written in TypeScript, so it will be able to run a JavaScript code just fine. This script will create a blank app and modify the domain model in the `MyFirstModule` module.
 
 ```ts
 import { domainmodels, IModel } from "mendixmodelsdk";
@@ -210,6 +210,6 @@ Execute the script. You should have a new app with the generated entities.
 
 {{% alert color="info" %}}
 
-Instead of creating a new app, you can also reuse an existing project or even an existing online working copy.
+Instead of creating a new app, you can also reuse an existing app or even an existing online working copy.
 
 {{% /alert %}}

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

@@ -10,7 +10,7 @@ The `model` object you get back from `workingCopy.model()` can be used to find a
 
 ## 2 The model.root Property
 
-The `root` object refers to the `root` project node in the **App Explorer** in Studio Pro. From there, you can walk through the app tree and into specific documents.
+The `root` object refers to the `root` app node in the **App Explorer** in Studio Pro. From there, you can walk through the app tree and into specific documents.
 
 For example, this snippet finds the name of the first attribute of the `Customer` entity in the first module of your app:
 

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

@@ -137,7 +137,7 @@ For more information, see [Async Await](https://basarat.gitbook.io/typescript/fu
     ```
 
 {{% alert color="info" %}}
-The steps for app (project) creation (line 3) and committing to the Team Server (line 10) can take some time, so please be patient. Be aware that 'revision -1' refers to the latest revision, and that 'branch null' is equal to the main line.
+The steps for app creation (line 3) and committing to the Team Server (line 10) can take some time, so please be patient. Be aware that 'revision -1' refers to the latest revision, and that 'branch null' is equal to the main line.
 {{% /alert %}}
 
 ## 5 Opening the App in Studio Pro

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/setting-up-your-development-environment.md

@@ -10,7 +10,7 @@ This document will lead you through the process of setting up everything you nee
 
 ## 2 Quick Installation
 
-If you know what you are doing, the quick installation instructions below are for you. Otherwise, please skip this paragraph and continue with the [Setting Up Your Development Tools](#setting) section.
+If you know what you are doing, the quick installation instructions below are for you. Otherwise, skip this paragraph and continue with the [Setting Up Your Development Tools](#setting) section.
 
 For the quick installation, we assume that you have `node` already installed. 
 Set up a new `node` project and install the dependencies using the following steps:

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/using-platform-sdk.md

@@ -43,7 +43,7 @@ You can pass the following options to `createNewApp`:
 | `templateDownloadURL` | The URL of the download location of the app template package file (*.mpk*). If the template package is private, this URL must be authenticated with a signature. |
 | `templateId` | The UUID of the app template on which the app should be based. |
 
-If both `templateDownloadURL` and `templateId` are left blank, the app project will be created using the standard blank app template in the latest Mendix version.
+If both `templateDownloadURL` and `templateId` are left blank, the app will be created using the standard blank app template in the latest Mendix version.
 
 Here is an example for creating a Mendix app based on the [Asset Management](https://marketplace.mendix.com/link/component/107652) template:
 

content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/javascript-typescript-resources.md

@@ -26,7 +26,7 @@ If you have any additional useful resources, feel free to mention them in the co
 * [Official TypeScript website](http://www.typescriptlang.org/Handbook) - Tutorial, handbook, samples
 * [Definitive Guide to TypeScript](https://www.sitepen.com/blog/2013/12/31/definitive-guide-to-typescript/) - covers TypeScript 1.5,slightly older than the current release, but still useful
 * [Editing TypeScript](https://code.visualstudio.com/docs/languages/typescript) with Visual Studio Code
-* Debugging your project with [Node Inspector](https://www.npmjs.com/package/node-inspector)
+* Debugging your app with [Node Inspector](https://www.npmjs.com/package/node-inspector)
 
 ## 4 Videos