Developer-Autodesk · sergioleon3d · Jul 22, 2020 · Jul 22, 2020 · Jul 22, 2020 · Jul 22, 2020
diff --git a/docs/_sidebar.md b/docs/_sidebar.md
@@ -17,7 +17,7 @@
 - [Modify your models](tutorials/modifymodels.md)
   - [Create a server](environment/setup/2legged_da.md)
   - [Basic app UI](designautomation/html/)
-  - [Prepare a plugin](designautomation/appbundle/)
+  - [Prepare an AppBundle (plugin)](designautomation/appbundle/)
   - [Define an activity](designautomation/activity/)
   - [Execute workitem](designautomation/workitem/)
 - [Run & Debug](environment/rundebug/readme.md)

diff --git a/docs/designautomation/activity/README.md b/docs/designautomation/activity/README.md
@@ -1,7 +1,9 @@
 # Define an Activity
 
-Activity is the specification of an action that can be executed using a specified engine. It specifies the number of input and output files, and the AppBundle and entry-point to use.
+Activity is the specification of an action that can be executed using a specified engine. It specifies: the number of input and output files, the AppBundle and an entry-point to use. 
 
 In this tutorial sample, the activity has 2 inputs (file & JSON data) and 1 output (file).
 
+> It's worth mentioning again the Design Automation documentation for [entities](https://forge.autodesk.com/en/docs/design-automation/v3/developers_guide/field-guide/), where you can see the relation between them in [Entity Relationships](https://forge.autodesk.com/en/docs/design-automation/v3/developers_guide/field-guide/#entity-relationships)
+
 Choose your language: [Node.js](designautomation/activity/nodejs) | [.NET Core](designautomation/activity/netcore)
diff --git a/docs/designautomation/activity/netcore.md b/docs/designautomation/activity/netcore.md
@@ -12,10 +12,30 @@ To define the activity we'll need the executable and the default file extension.
 /// </summary>
 private dynamic EngineAttributes(string engine)
 {
-    if (engine.Contains("3dsMax")) return new { commandLine = "$(engine.path)\\3dsmaxbatch.exe -sceneFile \"$(args[inputFile].path)\" $(settings[script].path)", extension = "max", script = "da = dotNetClass(\"Autodesk.Forge.Sample.DesignAutomation.Max.RuntimeExecute\")\nda.ModifyWindowWidthHeight()\n" };
-    if (engine.Contains("AutoCAD")) return new { commandLine = "$(engine.path)\\accoreconsole.exe /i \"$(args[inputFile].path)\" /al \"$(appbundles[{0}].path)\" /s $(settings[script].path)", extension = "dwg", script = "UpdateParam\n" };
-    if (engine.Contains("Inventor")) return new { commandLine = "$(engine.path)\\inventorcoreconsole.exe /i \"$(args[inputFile].path)\" /al \"$(appbundles[{0}].path)\"", extension = "ipt", script = string.Empty };
-    if (engine.Contains("Revit")) return new { commandLine = "$(engine.path)\\revitcoreconsole.exe /i \"$(args[inputFile].path)\" /al \"$(appbundles[{0}].path)\"", extension = "rvt", script = string.Empty };
+    if (engine.Contains("3dsMax")) 
+        return new { 
+            commandLine = "$(engine.path)\\3dsmaxbatch.exe -sceneFile \"$(args[inputFile].path)\" $(settings[script].path)", 
+            extension = "max", 
+            script = "da = dotNetClass(\"Autodesk.Forge.Sample.DesignAutomation.Max.RuntimeExecute\")\nda.ModifyWindowWidthHeight()\n" 
+        };
+    if (engine.Contains("AutoCAD")) 
+        return new { 
+            commandLine = "$(engine.path)\\accoreconsole.exe /i \"$(args[inputFile].path)\" /al \"$(appbundles[{0}].path)\" /s $(settings[script].path)", 
+            extension = "dwg", 
+            script = "UpdateParam\n" 
+        };
+    if (engine.Contains("Inventor")) 
+        return new { 
+            commandLine = "$(engine.path)\\inventorcoreconsole.exe /i \"$(args[inputFile].path)\" /al \"$(appbundles[{0}].path)\"", 
+            extension = "ipt", 
+            script = string.Empty 
+        };
+    if (engine.Contains("Revit")) 
+        return new { 
+            commandLine = "$(engine.path)\\revitcoreconsole.exe /i \"$(args[inputFile].path)\" /al \"$(appbundles[{0}].path)\"", 
+            extension = "rvt", 
+            script = string.Empty 
+        };
     throw new Exception("Invalid engine");
 }
 ```

diff --git a/docs/designautomation/appbundle/README.md b/docs/designautomation/appbundle/README.md
@@ -1,23 +1,22 @@
-# Prepare a plugin
+# Prepare an AppBundle (plugin)
 
-Design Automation uses .bundle just like the Autodesk App Store, meaning you need to create a `PackageContents.xml` and a ZIP with the `DLL` (and other required files). For detailed information on how to create them, please visit [Autodesk App Store Developer Center](https://www.autodesk.com/developer-network/app-store).
+At this section we will create a basic plugin or AppBundle that searches for the Windows in the scene model tree and updates the `width` and `height` parameters of it, saving the resulting file as a new file. 
 
-At this section we will create a basic plugin that update `width` and `height` parameter and save the resulting file. Also the supporting files (`PackageContents.xml`) and the folder structure to place them. Finally create a .ZIP file ready to upload to Design Automation.
+Design Automation uses .bundle just like the Autodesk App Store. For it, a `PackageContents.xml` descriptor file will be created and ZIP together with the `DLL` and other possible required files. For detailed information on how to create them, please visit [Autodesk App Store Developer Center](https://www.autodesk.com/developer-network/app-store). The created ZIP AppBundle file will be uploaded.
 
 ### Prerequisites
 
 - **7zip**: use to create the .ZIP with bundle files, please install [from here](https://www.7-zip.org/). This tutorial assumes **7zip** is installed on the default folder: _C:\Program Files\7-Zip\7z.exe_.
 
-### Additional prerequisites 
+#### Additional prerequisites 
 
 For the next session you can use the pre-build plugin. Or if you decide to build it, you will need:
 
 - **Visual Studio**: Visual Studio 2017 or newer is required, please visit [this link](https://visualstudio.microsoft.com/vs/).
 
-- **AutoCAD, Inventor, Revit or 3ds Max**: In order to develop, test and debug your Design Automation plugin: [AutoCAD](https://www.autodesk.com/products/autocad/overview) | [Inventor](https://www.autodesk.com/products/inventor/overview) | [Revit](https://www.autodesk.com/products/revit/overview) | [3ds Max](https://www.autodesk.com/products/3ds-max/overview).
+- **AutoCAD, Inventor, Revit or 3ds Max**: In order to develop, compile, test and debug your Design Automation plugin, you will need the respective application installed: [AutoCAD](https://www.autodesk.com/products/autocad/overview) | [Inventor](https://www.autodesk.com/products/inventor/overview) | [Revit](https://www.autodesk.com/products/revit/overview) | [3ds Max](https://www.autodesk.com/products/3ds-max/overview).
 
 ***
 
-For the next step, choose the **Engine**, which is the Autodesk application where you plugin will run. You'll need the respective application installed in order to compile, debug and test locally.
-
-Choose the engine: [AutoCAD](/designautomation/appbundle/engines/autocad) | [Inventor](/designautomation/appbundle/engines/inventor) | [Revit](/designautomation/appbundle/engines/revit) | [3ds Max](/designautomation/appbundle/engines/max)
+The **Engine** is the Autodesk application where your plugin or App will run. Choose the engine you will use: 
+[AutoCAD](/designautomation/appbundle/engines/autocad) | [Inventor](/designautomation/appbundle/engines/inventor) | [Revit](/designautomation/appbundle/engines/revit) | [3ds Max](/designautomation/appbundle/engines/max)
diff --git a/docs/designautomation/appbundle/common.md b/docs/designautomation/appbundle/common.md
@@ -1,5 +1,5 @@
-# Upload app bundle
+# Create and upload AppBundle
 
-Now the ZIP bundle is ready, let's upload to Design Automation.
+Now that the ZIP AppBundle is ready, let's upload it to Design Automation.
 
 Choose your language: [Node.js](designautomation/appbundle/nodejs) | [.NET Core](designautomation/appbundle/netcore)
diff --git a/docs/designautomation/appbundle/engines/autocad.md b/docs/designautomation/appbundle/engines/autocad.md
@@ -138,7 +138,7 @@ namespace UpdateDWGParam
 
 ## PackageContents.xml
 
-Create a folder named `UpdateDWGParam.bundle` and, inside, a file named `PackageContents.xml`, then copy the following content to it. Learn more at the [PackageContents.xml Format Reference](https://knowledge.autodesk.com/search-result/caas/CloudHelp/cloudhelp/2016/ENU/AutoCAD-Customization/files/GUID-BC76355D-682B-46ED-B9B7-66C95EEF2BD0-htm.html). This file defines the new AutoCAD custom command `UpdateParam` that will be called when Design Automation executes.
+Create a folder named `UpdateDWGParam.bundle` and, inside, a file named `PackageContents.xml`, then copy the following content to it. Learn more at the [PackageContents.xml Format Reference](https://help.autodesk.com/view/ACD/2021/ENU/?guid=GUID-BC76355D-682B-46ED-B9B7-66C95EEF2BD0). This file defines the new AutoCAD custom command `UpdateParam` that will be called when Design Automation executes.
 
 ```xml
 <?xml version="1.0" encoding="utf-8" ?>

diff --git a/docs/designautomation/appbundle/engines/max.md b/docs/designautomation/appbundle/engines/max.md
@@ -11,7 +11,11 @@ Remember that for Design Automation, there should be no UI or prompts that canno
 
 ## Create a new .NET project
 
-Right-click on the solution, the **Add** >> **New Project**. Select **Windows Desktop**, then **Class Library** and, finally, name it `UpdateMAXParam`. You will then need to reference the Autodesk.Max.Dll managed assembly (3ds Max .NET API core module). This module is found in the 3dsmax.exe folder and when referencing, make sure to turn off the "Copy Local" flag. There are a few other modules used for .NET API support (see [The 3ds Max .NET SDK](http://help.autodesk.com/view/3DSMAX/2019/ENU/?guid=__developer_3ds_max__net_sdk_html)), but for this tutorial we will use only Autodesk.Max.dll. Then search and install `Newtonsoft.Json` (which is used to parse input data in JSON format).
+Right-click on the solution, and then **Add** >> **New Project**. Select **Windows Desktop**, then **Class Library** and, finally, name it `UpdateMAXParam`. 
+
+You will then need to reference the Autodesk.Max.dll managed assembly (3ds Max .NET API core module). This module is found in the 3dsmax.exe folder and when referencing, make sure to turn off the "Copy Local" flag. There are a few other modules used for .NET API support (see [The 3ds Max .NET SDK](http://help.autodesk.com/view/3DSMAX/2019/ENU/?guid=__developer_3ds_max__net_sdk_html)), but for this tutorial we will use only Autodesk.Max.dll. 
+
+Then search and install `Newtonsoft.Json` (which is used to parse input data in JSON format).
 
 > Please select .NET Framework 4.7. If not listed, [please install the Dev Pack](https://dotnet.microsoft.com/download/dotnet-framework/net47).
 
@@ -28,9 +32,61 @@ As a result, the **package.config** should look like the following for the Newto
 
 The project should contain a `Class1.cs` class, let's rename the file to `Command.cs` (for consistency). 
 
+## PackageContents.xml
+
+Create a folder named `UpdateMAXParam.bundle` and inside this folder add a file named `PackageContents.xml` that will be the AppBundle descriptor. Copy the content listed below in the XML section into the PackageContents.xml file. 
+
+This file will tell 3ds Max the modules to load. In this case points to the .NET API plugin assembly we will compile, but it can also include MAXScripts, Python, and/or C++ plugins. Because the dll plugin is being loaded through this feature, you only need to worry later about the instructions to trigger your automation job. Please note that a unique ID for both ProductCode and UpgradeCode are required for 3ds Max to correctly load your code. 
+
+> You can learn about the [PackageContents.xml Format Reference](http://help.autodesk.com/view/3DSMAX/2019/ENU/?guid=__developer_writing_plug_ins_packaging_plugins_packagexml_format_html). 
+> For more 3ds Max specific information for packaging your 3ds Max plugins, please see here [Packaging Plugins](http://help.autodesk.com/view/3DSMAX/2019/ENU/?guid=__developer_writing_plug_ins_packaging_plugins_html)
+
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<ApplicationPackage 
+	SchemaVersion="1.0" 
+	AutodeskProduct="3ds Max" 
+    Name="Sample Design Automation Plugin for 3ds Max"
+    Description="A sample package to update parameters of a 3ds Max scene file containing a casement window"
+	AppVersion="2019.0.0" 
+	FriendlyVersion="2019.0.0" 
+	ProductType="Application" 
+	SupportedLocales="Enu" 
+	AppNameSpace="apps.autodesk.com" 
+	Author="Autodesk Forge" 
+    ProductCode="{6A8D06F4-C3DD-42DD-A69E-9B9617A7ABC0}"
+	UpgradeCode="{CE88CEA5-47F6-423E-B9EC-E9FA683B5228}"
+    >
+
+	<CompanyDetails Name="Autodesk"
+		Phone=" "
+		Url="http://forge.autodesk.com"
+		Email="noreply@autodesk.com" />
+
+	<RuntimeRequirements OS="Win64" Platform="3ds Max" SeriesMin="2019" SeriesMax="2021" />
+
+	<Components Description="assemblies parts">
+		<RuntimeRequirements OS="Win64" Platform="3ds Max" SeriesMin="2019" SeriesMax="2021" />
+		<ComponentEntry AppName="UpdateMAXParam" Version="2019.0.0" ModuleName="./Contents/UpdateMAXParam.dll" AppDescription="The Sample Design Automation Plugin managed assembly module" />
+	</Components>
+
+</ApplicationPackage>
+```
+
+Create a subfolder named `Contents` and leave it empty. At this point, the project should look like:
+
+![](_media/designautomation/max/bundle_folders.png)
+
 ## Commands.cs
 
-This is the main code that will run with 3ds Max. Copy the following content into `Command.cs`. There are three classes to handle the Design Automation porcessing. First is the `InputParams` that will be used to interface with the JSON input data. Next is `ParameterChanger` class that is used to iterate the scene, and find all Casement Windows (but could be any object types as identified by the class ids). Finally the `RuntimeExecute` is used to take the input and drive the automation. Also note there is a specialized logging that will output information to the Design Automation console. See the LogTrace function. Note that the `ILogSys` 3ds Max managed class is used for this, and the flags used with the `LogEntry` API indicated are necessary for the output to show in the Design Automation console. 
+This is the main code that will run within 3ds Max. Copy the following content into `Command.cs`. There are three classes to handle the Design Automation processing. 
+
+1. `InputParams` will interface with the JSON input data. 
+2. `ParameterChanger` iterates through the scene, and find all Casement Windows models in our sample. It could also be any object types as identified by the class ids. 
+3. `RuntimeExecute` takes the input and drives the automation. 
+
+Note there is a specialized logging that will output information to the Design Automation console. See the `LogTrace` function. Note that the `ILogSys` 3ds Max managed class is used for this, and the flags used with the `LogEntry` API indicated are necessary for the output to be shown in the Design Automation console. 
 
 ```csharp
 using System;
@@ -182,48 +238,6 @@ namespace Autodesk.Forge.Sample.DesignAutomation.Max
 }
 ```
 
-## PackageContents.xml
-
-Create a folder named `UpdateMAXParam.bundle` and inside this folder add a file named `PackageContents.xml`. Copy the content listed below in the XML section into the PackageContents.xml file. Learn more at the [PackageContents.xml Format Reference](https://knowledge.autodesk.com/search-result/caas/CloudHelp/cloudhelp/2016/ENU/AutoCAD-Customization/files/GUID-BC76355D-682B-46ED-B9B7-66C95EEF2BD0-htm.html). For more 3ds Max specific information for packaging your 3ds Max plugins see here [Packaging Plugins](http://help.autodesk.com/view/3DSMAX/2019/ENU/?guid=__developer_writing_plug_ins_packaging_plugins_html)
-
-This file will tell 3ds Max the modules to load (in this case the .NET API plugin assembly we are creating, but can also include MAXScripts, Python, and/or C++ plugins.) Because the plugin is being loaded through this feature, you only need to worry about the instructions to trigger your automation job. Please note that a unique ID for both ProductCode and UpgradeCode are required for 3ds Max to correctly load your code. See above mentioned documentation for details.
-
-```xml
-<?xml version="1.0" encoding="utf-8"?>
-<ApplicationPackage 
-	SchemaVersion="1.0" 
-	AutodeskProduct="3ds Max" 
-    Name="Sample Design Automation Plugin for 3ds Max"
-    Description="A sample package to update parameters of a 3ds Max scene file containing a casement window"
-	AppVersion="2019.0.0" 
-	FriendlyVersion="2019.0.0" 
-	ProductType="Application" 
-	SupportedLocales="Enu" 
-	AppNameSpace="apps.autodesk.com" 
-	Author="Autodesk Forge" 
-    ProductCode="{6A8D06F4-C3DD-42DD-A69E-9B9617A7ABC0}"
-	UpgradeCode="{CE88CEA5-47F6-423E-B9EC-E9FA683B5228}"
-    >
-
-	<CompanyDetails Name="Autodesk"
-		Phone=" "
-		Url="http://forge.autodesk.com"
-		Email="noreply@autodesk.com" />
-
-	<RuntimeRequirements OS="Win64" Platform="3ds Max" SeriesMin="2019" SeriesMax="2021" />
-
-	<Components Description="assemblies parts">
-		<RuntimeRequirements OS="Win64" Platform="3ds Max" SeriesMin="2019" SeriesMax="2021" />
-		<ComponentEntry AppName="UpdateMAXParam" Version="2019.0.0" ModuleName="./Contents/UpdateMAXParam.dll" AppDescription="The Sample Design Automation Plugin managed assembly module" />
-	</Components>
-
-</ApplicationPackage>
-```
-
-Finally, create a subfolder named `Contents` and leave it empty. At this point, the project should look like:
-
-![](_media/designautomation/max/bundle_folders.png)
-
 ## Post-build event
 
 > For Node.js it is required to adjust the AppBundle ZIP output folder.
@@ -236,7 +250,7 @@ del /F "$(ProjectDir)..\forgesample\wwwroot\bundles\UpdateMAXParam.zip"
 "C:\Program Files\7-Zip\7z.exe" a -tzip "$(ProjectDir)../forgesample/wwwroot/bundles/UpdateMAXParam.zip" "$(ProjectDir)UpdateMAXParam.bundle\" -xr0!*.pdb
 ```
 
-This will copy the DLL from /bin/debug/ into .bundle/Contents folder, then use [7zip](https://www.7-zip.org/) to create a zip, then finally copy the ZIP into /bundles folders of the webapp.
+This will copy the compiled DLL from /bin/debug/ into .bundle/Contents folder. It will then use [7zip](https://www.7-zip.org/) to create a zip. And finally it will copy the ZIP into /bundles folders of the webapp.
 
 ![](_media/designautomation/max/post_build.png)
 > Note how the **Post-build event** uses the project and folder names, so make sure you're using these names.
@@ -245,6 +259,8 @@ If you build the `UpdateMAXParam` project now you should see something like belo
 
 ![](_media/designautomation/max/build_output.png)
 
+## Testing locally
+
 At this point, you could test the functionality using the 3ds Max batch tool. It works similarly to the 3ds Max Design Automation engine and is a good way to test all your automation locally before sending the job to the Forge DA cloud services. For .NET Classes to be instantiated in MAXScript environment, we can use the `dotNetClass` MAXScript function. For this sample project, the MAXScript code would look like this:
 
 ```MAXScript
@@ -257,7 +273,7 @@ fn UpdateParam =
 UpdateParam()
 ```
 
-To execute this locally, we could do test a a command-line prompt with something like this:
+To execute this locally, we could do test a command-line prompt with something like this:
 ```CommandLine
 "%ADSK_3DSMAX_x64_2019%\3dsmaxbatch.exe" -sceneFile <myTestScene>.max da_script.ms
 ```

diff --git a/docs/designautomation/appbundle/engines/revit.md b/docs/designautomation/appbundle/engines/revit.md
@@ -129,7 +129,7 @@ namespace Autodesk.Forge.Sample.DesignAutomation.Revit
 
 ## PackageContents.xml
 
-Create a folder named `UpdateRVTParam.bundle` and, inside, a file named `PackageContents.xml`, then copy the following content to it. Learn more at the [PackageContents.xml Format Reference](https://knowledge.autodesk.com/search-result/caas/CloudHelp/cloudhelp/2016/ENU/AutoCAD-Customization/files/GUID-BC76355D-682B-46ED-B9B7-66C95EEF2BD0-htm.html). This file tells Revit to load our `.addin` plugin.
+Create a folder named `UpdateRVTParam.bundle` and, inside, a file named `PackageContents.xml`, then copy the following content to it. Learn more at the [PackageContents.xml Format Reference](https://help.autodesk.com/view/ACD/2021/ENU/?guid=GUID-BC76355D-682B-46ED-B9B7-66C95EEF2BD0). This file tells Revit to load our `.addin` plugin.
 
 ```xml
 <?xml version="1.0" encoding="utf-8" ?>