update

.github/workflows/deploy.yml

@@ -18,8 +18,4 @@ jobs:
       # copy content to new app 
       - run: azcopy_v10 copy './docs' '${{ secrets.HELP_CONTENT_URL }}/content/${{ github.repository }}?${{ secrets.HELP_CONTENT_TOKEN }}' --recursive
       - run: azcopy_v10 copy './static' '${{ secrets.HELP_CONTENT_URL }}/content/${{ github.repository }}?${{ secrets.HELP_CONTENT_TOKEN }}' --recursive
-      - run: azcopy_v10 copy './sidebars.js' '${{ secrets.HELP_CONTENT_URL }}/content/${{ github.repository }}?${{ secrets.HELP_CONTENT_TOKEN }}'
-      # publish compiled output to existing app
-      - run: yarn install
-      - run: yarn build
-      - run: azcopy_v10 copy 'build/*' '${{ secrets.DOCS_STORAGE_URL }}/${{ secrets.DOCS_STORAGE_PATH }}?${{ secrets.DOCS_STORAGE_KEY }}' --recursive
+      - run: azcopy_v10 copy './sidebars.js' '${{ secrets.HELP_CONTENT_URL }}/content/${{ github.repository }}?${{ secrets.HELP_CONTENT_TOKEN }}'

docs/build-schedule-practice.md

@@ -0,0 +1,23 @@
+---
+sidebar_label: 'Practice: Build a Schedule'
+---
+
+# Practice: Build a Schedule
+
+
+### Objective
+
+Build the Schedule named **Practice Schedule 1** as Released for Today only. View to confirm that the Schedule and its Jobs run correctly.
+
+### Instructions
+
+1.	In Solution Manager, select the **Operations** tab.
+2.  In Operations Summary, click **Schedule Build** in the top right-hand corner.
+3.  In the **Schedule** List, select **Practice Schedule 1**.
+4.	In the **Scheduling Dates** section in the left-hand menu:
+  *	Select today's dates for **From** and **To**. 
+5.	In **Schedule Build** window:
+  * Select the **Released** option to automatically build the Schedule.
+6. Click the **Build** button.
+7.	In the next screen (Build Results), expand the dropdown menu and click down to select and click on **Practice Schedule 1** .
+8.	The **Processes** screen will allow review of the Job Run results and details.

docs/create-dependencies-practice.md

@@ -0,0 +1,36 @@
+---
+sidebar_label: 'Practice: Create Dependencies'
+---
+
+# Practice: Create Dependencies
+
+### Objective
+
+Create a **REQUIRES** Dependency Chain for the four Jobs in **Schedule 1**. 
+
+The Dependency Flow should be:
+
+**Windows Job 1** <- **Windows Job 2** <- **Windows Job 3** <- **Windows Job 4**
+
+where **Windows Job 4** Requires **Windows Job 3**, etc.
+
+### Instructions
+
+1.	In Solution Manger, select **Studio**. 
+2.	In the **Schedule** list, select **Practice Schedule 1e**.
+3. Click the **View** button.
+3.	Click **Windows Job 4**.
+4.	In the Job menu, click **Add Dependency**.
+5.	In the **Schedule** Schedule frame, check that **Schedule 1** is selected.
+6.  In the **Job** drop down list, select **Windows Job 3**.
+7.	In the **Dependency** frame, select **Requires** and **Finished OK**.
+8.	Click **Windows Job 3**.
+9.	In the Job menu, click **Add Dependency**.
+10.	In the **Schedule** Schedule frame, check that **Schedule 1** is selected.
+11.  In the **Job** drop down list, select **Windows Job 2**.
+12.	In the **Dependency** frame, select **Requires** and **Finished OK**.
+13.	Click **Windows Job 2**.
+14.	In the Job menu, click **Add Dependency**.
+15.	In the **Schedule** Schedule frame, check that **Schedule 1** is selected.
+16.  In the **Job** drop down list, select **Windows Job 1**.
+17.	In the **Dependency** frame, select **Requires** and **Finished OK**.

docs/create-frequency-practice.md

@@ -0,0 +1,7 @@
+---
+sidebar_label: 'Practice: Create a Frequency'
+---
+
+# Practice: Create a New Frequency
+
+{Test}

docs/create-job-practice.md

@@ -0,0 +1,46 @@
+---
+sidebar_label: 'Practice: Create a Job'
+---
+
+# Practice: Create a Job
+
+### Objective 
+
+Create a Job named **Windows Job 1** within the schedule named **Schedule 1**. The Job must run on the ```WINDOWS``` machine type. The Job must use the ```SMATRAINING``` machine and the ```SMATRAINING\SMAUSER``` User Id. The command line should run the following program:
+
+```timeout /t 10```
+
+Assign the Job an **Existing Frequency** of ```Example-Mon-Sun-O```. Repeat the preceding steps to create 3 more Jobs identical to **Windows Job 1** following the same naming pattern.
+
+### Instructions
+
+1.	In Solution Manager, select **Studio**. 
+2.	In the Schedule list, select **Schedule 1**.
+3.	In the Menu to the right, select **Add Job**.
+4.	In the Schedule drop-down list, select **Schedule 1**.
+5.  In the Name textbox, enter **Windows Job 1**
+6.  In the Job Type drop-down list, select **Windows**.
+7.  Click on **Task Details** to open the Details box.
+8.	In the Machines or Machine Group drop-down list, select the SMATraining machine. 
+9.	In the User ID drop-down list, select ```SMATRAINING\SMAUSER```
+10.	Under **Run**, in the **Command Line**, type: 
+
+```timeout /t 10```
+
+11.	Click the **Save** button.
+12. Click the **Lock** button in the right hand corner of the Master Job Details screen.
+13. Select the **Frequency** tab and select the **Add** button.
+14.	Create a Frequency named ```Mon-Sun-0```.
+- Select ```All Weeks``` from the **When to Schedule** dropdown.
+-  Select ```Monday``` through ```Friday``` in the **Days of the Week** menu.
+-  Select ```Before Date``` in the **A/O/B/N** menu.
+- Click **Save**.
+Create three jobs that are identical to Windows Job 1.
+15. Navigate to **Library** > **Master Jobs**.
+16. In the Master Jobs screen, select **Windows Job 1** 
+17. Click the **Copy** button.
+18. Enter the Job Name as **Windows Job 2**.
+19. Deselect the "Navigate to Maser Job Definition Page after copy" option.
+20. Click the **OK** button.
+21. Repeat the copy process to create **Windows Job 3** and **Windows Job 4**.
+22.	Close the **Job Master**.

docs/create-schedule-practice.md

@@ -0,0 +1,22 @@
+---
+sidebar_label: "Practice: Create a Schedule"
+---
+
+# Practice: Create a Schedule
+
+### Objective
+
+Create and save a Schedule named **Practice Schedule 1**. Provide documentation to detail that this is a training schedule. Set the Schedule to **Auto Build** ```7 days``` in Advance for ```1 day```. Set the schedule to **Auto Delete** for ```7 days ago```.
+
+### Instructions
+
+1.	In Solution Manager, from the **Home** tab, select **Studio**.   
+2.	Click the **Add** button on the toolbar.   
+3.	In the Schedule Name textbox, enter **Practice Schedule 1**.   
+4.	In the Documentation textbox, enter **This is a Training Schedule**.  
+5.	In the **Schedule Build and Maintenance** frame, mark the **Auto Build** checkbox.  
+6.	Set ```7``` for the number of days in advance for Auto Build.  
+7.	Set ```1``` for the number of days to Auto Build.  
+8.	Mark the **Auto Delete** checkbox.  
+9.	Set ```7``` for the number of days to Auto Delete.  
+10.	Click the Save button.   

docs/create-tags-practice.md

@@ -0,0 +1,31 @@
+---
+sidebar_label: 'Practice: Create Tags'
+---
+
+# Practice: Create Tags
+
+### Objective
+
+Tag the first three Jobs in **Schedule 1** with the following Tags:
+
+* ```Critical```
+* ```Generic```
+
+Once the Jobs are tagged, view the Tag assignments in **Tag Manager**.
+
+### Instructions
+
+#### Job Tags
+1.	In Solution Manager, select **Library**.
+2.  In Library, under Management, select **Tags**.
+3.  Click the **Add** button.
+4.  In the Tag Name box, type **Critical**.
+5.  Click the **Filter** tab.
+6.  Click the **>** button next to **Practice Schedule 1**.
+7.  Select **Windows Job 1**, **Windows Job 2**, and **Windows Job 3**.
+8.  Click **Save**.
+9. Repeat steps 3-8 to add a second Tag named  **Generic** to the same Jobs.
+
+#### Tag Management
+10.	In **Tags**, select **Critical**. 
+12.	View the Jobs that use this **Tag** category.

docs/dependencies.md

@@ -0,0 +1,27 @@
+---
+sidebar_label: 'Dependencies'
+---
+
+# Dependencies
+
+<!--
+![](../static/imgbasic/Picture21.png)
+-->
+
+### Job Dependencies in Job Definition
+
+<!--
+![](../static/imgbasic/sm-daily-job-dependency.png)
+-->
+
+### Set Job Dependency Details
+
+<!--
+![](../static/imgbasic/sm-job-dependency-details-set.png)
+-->
+
+### Job Dependency Status
+
+<!--
+![](../static/imgbasic/sm-job-dependency-status.png)
+-->

docs/frequency-definition.md

@@ -0,0 +1,27 @@
+---
+sidebar_label: 'Frequency Definition'
+---
+
+# Frequency Definition
+
+<!--
+![Picture17](../static/imgbasic/Picture17.png)
+-->
+
+* In Solution Manager, a **Frequencies List** is found in **Library > Management > Frequencies**
+
+<!--
+![](../static/imgbasic/sm-frequencies-list.png)
+-->
+
+* Frequencies can be edited by selecting a Frequency from the **Frequencies List** and clicking the **Edit** button
+
+<!--
+![](../static/imgbasic/sm-frequency-manager-wizard-edit.png)
+-->
+
+* Frequency details for a Job can be viewed in the DEaily Job Definition
+
+<!--
+![](../static/imgbasic/sm-frequency-in-daily-job.png)
+-->

docs/index.md

@@ -1,36 +1,10 @@
 ---
 slug: '/'
-sidebar_label: 'Product Name'
+sidebar_label: 'Training'
 ---
 
-# Tutorial Intro
+# Training
 
-Let's discover **Docusaurus in less than 5 minutes**.
+[Create A Schedule](../static/video/create_a_schedule.mp4)
 
-## Getting Started
-
-Get started by **creating a new site**.
-
-Or **try Docusaurus immediately** with **[new.docusaurus.io](https://new.docusaurus.io)**.
-
-## Generate a new site
-
-Generate a new Docusaurus site using the **classic template**:
-
-```shell
-npx @docusaurus/init@latest init my-website classic
-```
-
-## Start your site
-
-Run the development server:
-
-```shell
-cd my-website
-
-npx docusaurus start
-```
-
-Your site starts at `http://localhost:3000`.
-
-Open `docs/intro.md` and edit some lines: the site **reloads automatically** and display your changes.
+<video src="../static/video/create_a_schedule.mp4" width="320" height="240" controls></video>

docs/inventory-report-checkpoint.md

@@ -0,0 +1,32 @@
+---
+sidebar_label: 'Checkpoint: Inventory Report Schedule'
+---
+
+# Checkpoint: Build an Inventory Report Schedule
+
+### Objective
+
+Congo Online Retail Inc. needs to run a Schedule named **CONGO INVENTORY REPORTS** that will create separate Inventory reports for six products every working day. These reports must run **sequentially** and be **Tagged** within the following categories:
+
+**Toys**
+
+* Legos
+* Nerf
+
+**Electronics**
+
+* Smartphones
+* Xbox
+
+**Clothing**
+
+* Levis
+* Nike
+
+All six ```WINDOWS``` Jobs must run **Monday-Friday** and may not start until ```8:00 AM```.
+
+The program that must be run in the Command Line for Job execution is:
+
+```
+timeout /t 15
+```

docs/jobs.md

@@ -0,0 +1,34 @@
+---
+sidebar_label: 'About Jobs'
+---
+
+# About Jobs
+
+OpCon needs some basic information to run a process:
+
+* Job type (Windows, UNIX, etc.)
+* Where it will run (Machine)
+* User associated with execution
+* What program/script (Command Line) will OpCon run
+
+
+### Job Type
+
+* **Job Type** defines the type of process to run
+* Usually associated with a specific Operating System
+* Only Job Types configured within your OpCon Environment are shown
+* Once a Job Type is selected, parameters specific to the chosen technical environment are displayed
+
+### Windows Job Type Definition Details
+
+Windows Job Type parameters must be set:
+
+* Primary Machine
+* User Id
+* Command Line
+
+### Job Details - Solution Manager
+
+<!--
+![](../static/imgbasic/sm-job-type-details.png)
+-->