Deployed 506ae25 with MkDocs version: 1.6.1

index.html

@@ -598,32 +598,38 @@ <h1 id="overview">Overview</h1>
 <h2 id="history">History</h2>
 <h3 id="version-20">Version 2.0</h3>
 <ul>
-<li>Added support to handle comments while uploading a process. The comments are mandatory when an user has <strong>"Require a Comment For Process Design Changes"</strong> enabled in the system settings of DevOps Deploy.</li>
-</ul>
-<p>Currently comments are added as the final argument in any of the upload command. These are also recommneded to be within double quotes.
-Syntax: <code>upload-generic/component/application-process &lt;username&gt; &lt;password&gt; &lt;server-url&gt; &lt;input-file&gt; "comments to add while updating process"</code></p>
-<ul>
-<li>Added Support to inject the value of a plugin property from a separate file if a user needs. The file path should be prefixed with <strong>scriptFile/</strong> in the respective Json or Yaml files as shown in below Examples:</li>
+<li>Added support to pass comments while uploading a process. The comments are mandatory when an user has <strong>"Require a Comment For Process Design Changes"</strong> enabled in the system settings of DevOps Deploy.Comments should be enclosed in double quotes. </li>
+<li>Syntax: <code>&lt;upload-command&gt; &lt;username&gt; &lt;password&gt; &lt;server-url&gt; &lt;input-file&gt; "comments to add while updating process"</code></li>
+<li>
+<p>Example <code>upload-generic-process admin admin http://localhost:8443 simple-shell-process.json "Changed the Regex in shell step to process only text files."</code></p>
+</li>
+<li>
+<p>Added Support to inject the value of a plugin property from a separate file if a user needs. The file path should be prefixed with <strong>scriptFile/</strong> in the respective Json or Yaml files as shown in below Examples:</p>
+<p><code>json5
+{ 
+  "properties": {
+        "prop1": "val1",
+        "prop2": "scriptFile/PropDetails.txt"
+  }
+}</code></p>
+<p><code>yaml
+properties:
+    prop1: "val1"
+    prop2: "scriptFile/PropDetails.txt"</code></p>
+</li>
 </ul>
-<pre><code class="language-json5">&quot;properties&quot;: {
-        &quot;prop1&quot;: &quot;val1&quot;,
-        &quot;prop2&quot;: &quot;scriptFile/PropDetails.txt&quot;
-}
-</code></pre>
-<pre><code>properties:
-    prop1: &quot;val1&quot;
-    prop2: &quot;scriptFile/PropDetails.txt&quot;
-</code></pre>
 <h3 id="version-12">Version 1.2</h3>
 <ul>
 <li>Added support to handle Post Processing script's body in separate files during upload and download process. The file path should be prefixed with <strong>scriptFile/</strong> in the respective Json or Yaml files as shown in below examples:</li>
 </ul>
-<pre><code class="language-json5">&quot;postProcessingScript&quot;: {
+<pre><code class="language-json5">  {
+      &quot;postProcessingScript&quot;: {
         &quot;name&quot;: &quot;MyScript&quot;,
         &quot;body&quot;: &quot;scriptFile/MyScript.txt&quot;
-}
+      }
+  }
 </code></pre>
-<pre><code>postProcessingScript:
+<pre><code class="language-yaml">postProcessingScript:
     name: &quot;MyScript&quot;
     body: &quot;scriptFile/MyScript.txt&quot;
 </code></pre>