Merge pull request #9312 from platrofa/ms/MS-3808-review-sdk-docs

MS-3808 review sdk docs

Author: MarkvanMents

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/).

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/manipulating-existing-models/closing-the-server-connection.md

@@ -5,7 +5,7 @@ url: /apidocs-mxsdk/mxsdk/finding-things-in-the-model/
 
 ## Introduction
 
-The `model` object you get back from `workingCopy.model()` can be used to find and even manipulate units and elements. It provides three different means with which you can find units and elements.
+The `model` object you get back from `workingCopy.openModel()` can be used to find and even manipulate units and elements. It provides three different means with which you can find units and elements.
 
 ## The model.root Property
 
@@ -14,7 +14,8 @@ The `root` object refers to the `root` app node in the **App Explorer** in Studi
 For example, this snippet finds the name of the first attribute of the `Customer` entity in the first module of your app:
 
 ```js
-const model = workingCopy.model();
+const model = await workingCopy.openModel();
+
 const domainModel = model.root.modules[0].domainModel;
 const customerEntity = domainModel.entities.filter(entity => entity.name === "Customer")[0]
 
@@ -40,7 +41,9 @@ For all the referable concepts in a model (both units, such as a page, as well a
 
 ```js
 const customerEntity = model.findEntityByQualifiedName("Customers.Customer");
-const attributeName = customerEntity.attributes[0].name;
+if (customerEntity) {
+    const attributeName = customerEntity.attributes[0].name;
+}
 ```
 
 For more information, see [How to Load Units and Elements](/apidocs-mxsdk/mxsdk/loading-units-and-elements/).
@@ -50,7 +53,7 @@ For more information, see [How to Load Units and Elements](/apidocs-mxsdk/mxsdk/
 Implement this snippet to fetch information on all the Marketplace modules used in your app:
 
 ```js
-const model = workingCopy.model();
+const model = await workingCopy.openModel();
 model.allModules()
 	.filter(module => module.fromAppStore === true)
 	.forEach(module =>

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

@@ -14,9 +14,7 @@ Since a unit might already have been loaded before, you are also allowed to use
 The following (slightly) contrived example demonstrates the behavior of `load`. The type information is made explicit in this example for demonstration purposes, but you can just omit this code since the TypeScript compiler will infer it. Note that this example is contrived: a normal flow would be to call `load` on the `domainModel` and work with the fully-loaded domain model inside its callback.
 
 ```ts
-import {domainmodels} from "mendixmodelsdk";
-
-const model = workingCopy.model();
+const model = await workingCopy.openModel();
 
 // at first, only interfaces are available:
 const domainModel = model.allDomainModels()[0];

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/manipulating-existing-models/loading-units-and-elements.md

@@ -6,7 +6,7 @@ deprecated: true
 ---
 
 {{% 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 %}}
 
 The following how-tos present details for Mendix Platform SDK versions below 5.0:

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

@@ -34,15 +34,15 @@ To set up your development tools, follow these steps:
 
     ```bash
     $ node --version
-    v14.15.0
+    v18.20.8
     ```
 
     For Debian-based Linux distributions such as Ubuntu, please refer to [NodeSource Node.js Binary Distributions](https://github.com/nodesource/distributions#user-content-installation-instructions) to properly set up your apt-get sources.
 
     In the rest of the how-tos, in blocks such as the above, lines starting with a `$` represent commands to type into a terminal. Sometimes a line follows without a $, represents output of the command.
 
 3. Install [Visual Studio Code](https://code.visualstudio.com/) (not to be confused with Visual Studio), a text editor/IDE with good support for [TypeScript](https://www.typescriptlang.org/). Make sure you have a recent version (v1.11.0+); check the version you are using through Help > About when you have Code opened.
-4. Install TypeScript 4.4.3 or higher with [`npm`](https://www.npmjs.com/) (or [`yarn`](https://yarnpkg.com/)), Node.js's package manager:
+4. Install TypeScript 4.6.2 or higher with [`npm`](https://www.npmjs.com/) (or [`yarn`](https://yarnpkg.com/)), Node.js's package manager:
 
     ```bash
     $ npm install -g typescript
@@ -52,7 +52,7 @@ To set up your development tools, follow these steps:
 
     ```bash
     $ tsc --version
-    Version 4.4.3 (or higher)
+    Version 4.6.2 (or higher)
     ```
 
     If the version number is much lower, it could be that you also have an outdated TypeScript SDK on your system, left over from a previous installation. You can either uninstall the old TypeScript SDK, or bypass it by removing the old TypeScript SDK from your system's PATH environment variable.