smatechnologies · rweesner · Mar 29, 2024 · Mar 29, 2024
diff --git a/docs/Audit Management.md b/docs/Audit Management.md
@@ -4,11 +4,23 @@ sidebar_label: 'Audit Management'
 
 
 * Used to view history of User updates to the OpCon database
-* Resides under Management in Enterprise Manager
+* Resides under **Management** > **Reporting**
 * The Audit Management (view) screen displays drop list for user, audit category selection, and options for date range to view preferred Audit information
 * Select **Master Job** in Audit Categories drop-down list
 * Click View Audit button or export data to .CSV file
 
+![AuditHistory](../static/imgbasic/AuditHistory.png)
+
+![AuditHistory2](../static/imgbasic/AuditHistory2.png)
+
+![Columns](../static/imgbasic/Columns.png)
+
+![Categories](../static/imgbasic/Categories.png)
+
+## Enterprise Manager
+
+<details>
+
 ![Picture295](../static/imgbasic/295.png)
 
 ![Picture296](../static/imgbasic/296.png)
@@ -27,4 +39,6 @@ sidebar_label: 'Audit Management'
 
 ### Audit Management Table
 
-![Picture300](../static/imgbasic/300.png)
+![Picture300](../static/imgbasic/300.png)
+
+</details>
diff --git a/docs/Embedded Scripts.md b/docs/Embedded Scripts.md
@@ -18,12 +18,13 @@ sidebar_label: 'Embedded Scripts'
 ### Script Types
 
 * Configure type of Scripts which can be stored by OpCon
-* There are 5 **predefined** Script types, but more can be added
+* There are 6 **predefined** Script types, but more can be added
   * Command Shell (.cmd)
   * Perl (.ps)
   * PowerShell (.ps1)
   * Python (.py)
   * VBScript (.vbs)
+  8 SQL (.sql)
 
 ![](../static/imgbasic/sm-script-types.png)
 

diff --git a/docs/Operation Views.md b/docs/Operation Views.md
@@ -79,7 +79,7 @@ When a Job is selected with a right-click several options are made available in
 * Job Configuration Tool
 * Job Executions History
 * Job Summary
-* Job Status Update
+* Status Update
 * Job Output
 * Diagram
 

diff --git a/docs/SM - Job Configuration.md b/docs/SM - Job Configuration.md
@@ -48,6 +48,6 @@ Right-Click Jobs and available actions appear
 
 ![](../static/imgbasic/Picture78.png)
 
-### Bulk Job Status Update
+### Bulk Status Update
 
 ![](../static/imgbasic/Picture79.png)
diff --git a/docs/SM - Job Status.md b/docs/SM - Job Status.md
@@ -23,7 +23,7 @@ When a Job is selected with a right-click several options are made available in
 * Job Configuration Tool
 * Job Executions History
 * Job Summary
-* Job Status Update
+* Status Update
 * Job Output
 * Diagram
 

diff --git a/docs/SM - Machine Status And User Accounts.md b/docs/SM - Machine Status And User Accounts.md
@@ -7,7 +7,7 @@ sidebar_label: 'SM - Machine Status And User Accounts'
 * Machine Status can be determined by the heart icon in the bottom right hand corner of the screen
 * Selecting the icon will display all Agents and their status
 * Machines can be bulk selected for status updates
-  * As with Schedule and Job status updates, only options available to a machine will be configurable
+  * As with Schedule and Status Updates, only options available to a machine will be configurable
 
 ![](../static/imgbasic/Picture83.png)
 

diff --git a/docs/SMA History.md b/docs/SMA History.md
@@ -6,8 +6,7 @@ sidebar_label: 'SMA History'
 
 * Founded in 1980
 * Headquarters in Houston, Texas
-* Over 800 Clients
-* Offices in USA and France
+* Service Over 800 Clients Worldwide
 * Proven Solution for all Operating Systems 
 * Customer Driven Technology
 * 24x7x365 Support 
diff --git a/docs/Schedule Status.md b/docs/Schedule Status.md
@@ -46,7 +46,7 @@ Right-Click Jobs and available actions appear
 
 ![Picture78](../static/imgbasic/Picture78.png)
 
-### Bulk Job Status Update
+### Bulk Status Update
 
 ![Picture79](../static/imgbasic/Picture79.png)
 

diff --git a/docs/Support Information.md b/docs/Support Information.md
@@ -36,12 +36,12 @@ sidebar_label: 'Support Information'
 * <a href="https://www.linkedin.com/groups/12274641" target="_blank">OpCon Wizards Group</a>
 * A Learning Community hosted as a LinkedIn Group that provides communication and feedback with OpCon experts within SMA and with other users
 
-##### OpCon Roundtables
+##### OpCon Connections
 
-* <a href="https://smatechnologies.com/roundtables" target="_blank">SMA Roundtables</a>
-* Roundtables are frequent OpCon-centered technical discussions and Q & A sessions hosted digitally the third Thursday of each month by Product Management and Technical Specialists.
+* <a href="https://smatechnologies.com/connections" target="_blank">SMA Connections</a>
+* A new series of sessions designed to develop meaningful connections with and among our valued customers. These sessions will provide a space where you can engage not only with our products but also with each other, fostering a collaborative information network..
 
-##### Webinars
+##### SMA Webinars
 
 * <a href="https://smatechnologies.com/webinars" target="_blank">SMA Webinars</a>
 * Webinars are educational presentations updating clients on releases and improvements as well as demonstrations of OpCon use cases.
diff --git a/docs/Unit 1 Exercise 8.md b/docs/Unit 1 Exercise 8.md
@@ -50,7 +50,7 @@ We can validate that this is the error by navigating to that location via a Wind
 14.	Click the **Save**. This should take you back to the Processes screen.
 
 #### On the Processes screen
-15.	The **Job Selection** menu should still be open, click **Job Status Update** and select **Restart**.
+15.	The **Job Selection** menu should still be open, click **Status Update** and select **Restart**.
 16. Close the **Job Selection** menu.
 17.	The job should have a **Finished OK** status because the invalid command in the **Command Line** has been corrected.
 18.	In the **Processes** screen, in the **Date** list, select tomorrow’s date. 

diff --git a/docs/Unit 1 Exercise 9-obsolete.md b/docs/Unit 1 Exercise 9-obsolete.md
@@ -56,11 +56,11 @@ https://SMATraining
   *	You should be able to see all 4 Jobs built for today in the Job List. 
 9.	From the **Job** list, select **Windows Job 1** and **Windows Job 2**.
 10.	Right-Click one of the Jobs.
-  *	The **Job Status Update** screen will appear on the right.
+  *	The **Status Update** screen will appear on the right.
   *	Notice that not all actions are available. Only the actions that can be performed for both Jobs.
 11.	Select **Restart on Hold**.
   *	Solution Manager will show a message in the top of the screen confirming the action was processed.
-12.	Close the **Job Status Update** screen, minimize Google Chrome and go back to **Enterprise Manager**.
+12.	Close the **Status Update** screen, minimize Google Chrome and go back to **Enterprise Manager**.
 13.	Open the **List** or **Matrix** view, go to today’s date and check the Jobs under **My First Schedule**.
   *	The status for **Windows Job 1** and **Windows Job 2** should be **On Hold**.
 14.	Still from **Enterprise Manager**, Right-Click the Jobs and select **Release**. You must perform this action for each Job.

diff --git a/docs/Unit 2 Exercise 10.md b/docs/Unit 2 Exercise 10.md
@@ -59,13 +59,13 @@ The **Forecast** screen should show the **15th and 30th days of each month** as
 19. In the **Frequency Manager Wizard**:
   * In the **Name** field, enter ```Annual```.
   * In the **When to Scheduled** dop-down menu, select **Annual Plan**.
-  * In the **Calendar** drop-down menu, select **Master Calendar**.
+  * In the **Calendar** drop-down menu, select **Master Holiday**.
   * In the **A/O/B/N** section, select **On Date**.
   * Click the **Save** button.
 20. In the **Active** column, select the frequency then select **Forecast**.
 
 :::tip
-The **Forecast** screen should show the **dates selected on the Master Calendar in Exercise 7** as green.
+The **Forecast** screen should show the **dates selected on the Master Holiday in Exercise 7** as green.
 :::
 
 21. Click the **Back** button to navigate back to the **Studio** workspace.

diff --git a/docs/Unit 2 Exercise 4 And 5.md b/docs/Unit 2 Exercise 4 And 5.md
@@ -26,7 +26,8 @@ Start Communication for the ```SUSEVM``` Machine.
 2.  Select **Enable Full Comm. (Job start Enabled)**.
 3.  Click **Back**.
 4.  You should receive a **Not Responding** in the **Status** column.
-5.  Continue on to **Exercise 5**.
+5. Close **Operations**
+6.  Continue on to **Exercise 5**.
 
 :::info Note
 Do not panic! This is an expected behavior based on the port number we entered when defining the **Socket Number** in Exercise 3. Please continue on to Exercise 5 to correct this issue.
@@ -42,19 +43,20 @@ View the **Netcom Log** to determine the reason why you are unable to establish
 
 #### Viewing the Log
 
-1. Open a **File Explorer** window
-2. Navigate to where the logs are stored. In this environment they are stored in the following path:  **C:\ProgramData\OpConxps\SAM\Log**
-3. Double click on the **SMANetcom.log** file.
-4. Scroll to the bottom of the **SMANetcom.log** file and look for this entry in the Log file: 
+1. In **Library** > **Administration** > **Logs**
+2. Click on the **SMANetcom.log** file.
+3. Scroll to the bottom of the **SMANetcom.log** file and look for this entry in the Log file: 
   * ```ConnectToMachine() -- Exception happens at machine [SUSEVM]: No connection could be made because the target machine actively refused it. [[<IP ADDRESS>:3111]]```
+4. Click **Back** until you get to the main **Library** page.
 
 #### Correcting the Communication Error
 
-5.	Back in Solution Manager, right click the **SUSEVM** machine
-6.	Select the **Wrench** icon to edit Machine details.
-7.  Click the **Change Communication Status** button at the bottom of the screen, select **Disable Communication**.
-8.	In the **General Settings** tab, change the **Socket Number** to ```3100```.
-9.	Click the **Save**.
+5.	In **Library** > **Administration** > **Agents**.
+6.  Right-click on the **SUSEVM** Unix Agent.
+7.	Click the **Wrench** icon in the Agent Selection panel to edit the Machine details.
+8.  Click the **Change Communication Status** button at the bottom of the screen, select **Disable Communication**.
+9.	In the **General Settings** tab, change the **Socket Number** to ```3100```.
+10.	Click the **Save**.
 11.	Click the **Change Communication Status** button, select **Enable Full Comm. (Job Start Enabled)**.
 12. Click the **Back** button in the top right-hand corner to return to the **Agents** main screen to verify that the **SUSEVM** machine is now communicating.
 13. Close **Operations**.

diff --git a/docs/Unit 3 Exercise 1.md b/docs/Unit 3 Exercise 1.md
@@ -36,7 +36,7 @@ You will create a new **Role** and **User Account**, then assign this new user t
   * In the **Description** field, enter some documentation.
     * Example: Role to be used during the security exercises.
   * Click **Save**
-8.  Click on the **User** section within the **Role Definition** section
+8.  Click on the **Users** section within the **Role Definition** section
 9.  Select the check-box for **Student Number1**
 10. Click **Save**.
 11. Close **Library**
@@ -58,7 +58,7 @@ You will create a new **Role** and **User Account**, then assign this new user t
 
 :::note
 * License & Support should show you the version information and links for various SMA and OpCon websites.
-* Tags is accessible but if you try to create a new tag you won't be able to do to a lack pf permissions.
+* Tags is accessible but if you try to create a new tag you won't be able to do to a lack of permissions.
 :::
 
 16. **Logout** of **Student1** and back in as the **SMAUSER**

diff --git a/docs/Unit 3 Exercise 11.md b/docs/Unit 3 Exercise 11.md
@@ -76,9 +76,10 @@ Validate that all the jobs in **My First Schedule** are in a completed state and
 24. In the **From** field, select today's date.
 25. In the **To** field, select today's date.
 26. Select the **Released** radio button.
-27. In the **Schedule List**, select **My First Schedule**.
-28. Click the **Build** button.
-29. Expand and click on the schedule link for **My First Schedule** to return to the **Processes** screen.
+27. Toggle on the **Overwrite Exsisting** switch
+28. In the **Schedule List**, select **My First Schedule**.
+29. Click the **Build** button.
+30. Expand and click on the schedule link for **My First Schedule** to return to the **Processes** screen.
 
 ## Enterprise Manager