Updates

tutorials/spa-academy-run-salesorderprocess/spa-academy-run-salesorderprocess.md

@@ -35,35 +35,42 @@ Releasing a project creates a version or snapshot of the changes and deploying t
 
      If you are releasing for the first time, then the version will start with **1.0.0**. Next time you release, the version numbers will be automatically updated.
 
-    <!-- border -->![Release](1.png)
+    <!-- border -->
+    ![Release](1.png)
 
 2. Click **Release**.
 
-    <!-- border -->![Release](2.png)
+    <!-- border -->
+    ![Release](2.png)
 
 
 ### Deploy released project
 
+1. If you do not have an environment already, go to **Control Tower** **->** **Environments** and create one.
 
-1. Once the project is released successfully:
-
-    - Click on **Deploy** option on the top-right corner of the screen
-    - Choose the **Public** environment
-    - Deploy the project
+    <!-- border -->
+    ![Run](environments.png)
+
+2. Once the project is released successfully, change to the released version and choose **Deploy** in the top-right corner of the screen.
+
+3. Choose the environment and select **Deploy**.
 
-    <!-- border -->![Deploy](3.png)
+    <!-- border -->
+    ![Deploy](3.png)
 
     Since you have created an **API trigger** in your process, you can see **Sales Order Trigger** in the list of triggers.
 
 2. Click **Deploy**.
 
-    <!-- border -->![Deploy](3.3.png)
+    <!-- border -->
+    ![Deploy](3.3.png)
 
     > Deployment will take a couple of seconds/minutes depending upon how big your project is and how many different artifacts it has. Any errors during the deployment will be shown in the Design Console at the bottom of the screen.
 
     Once the deployment is successful, you will see a changed status. You can also see all your deployed and/or released project versions from the project status list next to the project name.
 
-    <!-- border -->![Deploy](3.4.png)
+    <!-- border -->
+    ![Deploy](3.4.png)
 
     > You cannot edit released or deployed projects. To continue working on your project, you need to select the Editable version of your project (at the top of the page).
 
@@ -75,17 +82,15 @@ Releasing a project creates a version or snapshot of the changes and deploying t
 
 Once you have successfully deployed the business process with an API trigger, you can view the API trigger. 
 
-In the **Lobby**, under **Control Tower**, choose **Environment**.
-
-<!-- border -->![Triggers](4a.png)
-
-1. Open the **Public** environment.
+1. Open the environment where you deployed.
 
-    <!-- border -->![Triggers](4b.png)
+    <!-- border -->
+    ![Triggers](4b.png)
 
-2. Under the **Triggers**, open the trigger View
+2. On the **Triggers** tab, open the trigger View.
 
-    <!-- border -->![Triggers](4c.png)
+    <!-- border -->
+    ![Triggers](4c.png)
 
 2. You can view the API URL and the payload that must be sent to start the process. Copy the payload, which will be used in later steps. If you go into the deployed view of the process, you can see the API details of how you can call the API Trigger:
 
@@ -106,22 +111,22 @@ In the **Lobby**, under **Control Tower**, choose **Environment**.
     |  `definitionId`       | ID of the process after it is deployed
     |  `context`     | The data to be sent to the process. In yours, you defined the `salesorderdetails` and all its fields.
 
-    <!-- border -->![Run](4.1.png)
 
 3. Copy-paste the payload to Notepad or some other editor for future use, by clicking the **Copy** button.
 
-    <!-- border -->![Run](4.11.png)
+    <!-- border -->
+    ![Run](4.11.png)
 
 4. Since you have created an API Trigger for the Business process, let's test the process with API Trigger in **Monitoring** section before you start the process from SAP Build Apps.
 
     `definitionId` of the process can be seen in Monitoring section or in the API trigger section as shown in the above step.
 
-    - From the Build lobby, navigate to **Monitoring** tab and within the tab, under **Manage** section, access **Processes and Workflows**.
+    - From your environment, choose the **Processes and Workflows** tab.
     - Search for the project `Sales Order Management_<your unique identifier>` that you have created in previous tutorial.
     - Click on **Start New Instance**.
 
-    <!-- border -->![Run](4.2a.png)
-    <!-- border -->![Run](4.2b.png)
+    <!-- border -->
+    ![Run](4.2b.png)
 
 5.  Remove the example payload in the dialog. You need to add the payload you saved earlier, but only part of the payload.
 
@@ -131,7 +136,7 @@ In the **Lobby**, under **Control Tower**, choose **Environment**.
 
     ```JSON
     {
-            "salesorderdetails": 
+            "salesOrderDetails": 
             {
                 "material": "HT-1000",
                 "orderAmount": 120000,
@@ -140,7 +145,7 @@ In the **Lobby**, under **Control Tower**, choose **Environment**.
                 "salesOrganisation": "01",
                 "distributionChannel": "01",
                 "shippingCountry": "India",
-                "expectedDeliveryDate": "2023-10-10",
+                "expectedDeliveryDate": "2025-10-10",
                 "division": "01"
             }
      }    
@@ -149,13 +154,14 @@ In the **Lobby**, under **Control Tower**, choose **Environment**.
     >Common issues when you are unable to start the instance:
 
     >1. SAP Build Process Automation supports the ISO 8601 format for date and time: YYYY-MM-DD (2023-03-16) and hh:mm:ss (15:33:16). Hence make sure to enter `expectedDeliveryDate` in the supported format as shown above.
-    >2. There is no mismatch in the field names.
+    >2. Mismatch in the field names.
     >3. Data type mismatch. For example, if you enter order amount as a string instead of a number ("orderAmount":"120000").
 
 
 6. Click **Start New Instance and Close**.
 
-    <!-- border -->![Run](5.png)
+    <!-- border -->
+    ![Run](5.png)
 
     >Don't modify the payload when you integrate with SAP Build Apps.
 
@@ -164,14 +170,14 @@ In the **Lobby**, under **Control Tower**, choose **Environment**.
 
 Monitoring business process is one of the key aspect of the automated processes. Technical monitoring is an administrator job where a process admin proactively and consistently monitors the process performance, identifies any issues in the process and takes necessary actions to ensure business process continuity.
 
-**SAP Build** provides different applications to monitor and manage different process artifacts. These applications are available under the **Monitoring** tab.
+**SAP Build** provides different applications to monitor and manage different process artifacts.
 
-1. Earlier, you accessed **Processes and Workflows** under the **Manage** section to see all the deployed processes.
-
-    To monitor all the running instances of the process, you must go to **Process and Workflow Instances** under the **Monitor** section.
+1. In the lobby, go to **Monitoring** **->** **Process and Workflow Instances**.
 
-    <!-- border -->![Run](6a.png)
-    <!-- border -->![Run](6b.png)
+    <!-- border -->
+    ![Run](6a.png)
+    <!-- border -->
+    ![Run](6b.png)
 
     In there, you will see all the running, erroneous and suspended process instances. Use the filter bar to get a more customized view of the process instances based on different statutes like running, completed, suspended, terminated and so forth.
 
@@ -183,15 +189,18 @@ Monitoring business process is one of the key aspect of the automated processes.
 
     Since the order amount is greater 100000, the process requires an approval.
 
-    <!-- border -->![Run](6.1.png)
+    <!-- border -->
+    ![Run](6.1.png)
 
 3. As you can see the process is waiting for the task to be completed. These tasks are generated from the forms that are added in the process and can be accessed via the **My Inbox** application.
 
-    <!-- border -->![Run](7.png)
+    <!-- border -->
+    ![Run](7.png)
 
     In the **Logs** section, expand the top activity. Notice the **Recipients** list. This is the same as configured in the **General** section of the **Approval Form**. The task will go into the inboxes of all the recipients.
 
-    <!-- border -->![Recipients](recipients.png)
+    <!-- border -->
+    ![Recipients](recipients.png)
 
     You will open the **My Inbox** in the next step.
 
@@ -202,23 +211,27 @@ Tasks are the request for the users to participate in an approval or review proc
 
 1. Access the **My Inbox** by going to the SAP Build lobby, and clicking the icon in the upper right. 
 
-    <!-- border -->![My Inbox](10.png)
+    <!-- border -->
+    ![My Inbox](10.png)
 
 2. Open the **My Inbox**, and find the task for the process you just triggered.
 
 3. Click **Approve**.
 
-    <!-- border -->![Inbox](8.png)
+    <!-- border -->
+    ![Inbox](8.png)
 
 4. Once you **approve/reject** the approval task, **refresh** the inbox again to get the final notification based on action taken.
 
 5. Click on **Submit** to complete the process.
 
-    <!-- border -->![Run](8.1.png)
+    <!-- border -->
+    ![Run](8.1.png)
 
     Once you acknowledge the notification sent via the approval process, the process will be completed.
 
-    <!-- border -->![Run](9.png)
+    <!-- border -->
+    ![Run](9.png)
 
     Repeat the testing above twice more:
 
@@ -234,16 +247,20 @@ In order to trigger a process from SAP Build Apps, you must first publish the pr
 
 1. Open the SAP Build lobby.
 
-2. Select the Process row,  click the 3 dots menu, go to the **Versions** tab, select Publish to Library.
+2. Select the project row, go to the **Versions** tab, choose **...** beside the deployed version and choose **Publish to Library**.
 
     A dialog lets you specify the version and other parameters. No need to change anything.
 
     Click **Publish**.
-    <!-- border -->![Publish to Library](publish-to-library.png)
 
-3. You should get a dialog that the process was published.
+    <!-- border -->
+    ![Publish to Library](publish-to-library.png)
+
+3. You should see that the version was published.
+
+    <!-- border -->
+    ![Publish to Library](published.png)
 
-
 
 ### Retrieve sample project from the store (Optional)
 
@@ -259,21 +276,26 @@ To retrieve this sample, please follow these steps:
 
 3. Choose **Create from Template** to retrieve the sample and save it as a new project in your lobby.
 
-    <!-- border -->![Store](store1.png)
+    <!-- border -->
+    ![Store](store1.png)
 
 4. Choose **Create**.
 
-    <!-- border -->![Create](create1.png)
+    <!-- border -->
+    ![Create](create1.png)
 
     Your project gets created in editable version. You may release and deploy it and run the project.
 
 5. Navigate back to the lobby by clicking on the SAP logo.
 
-    <!-- border -->![Project](project1.png)
+    <!-- border -->
+    ![Project](project1.png)
 
     You can see your project is available in the lobby.
 
-    <!-- border -->![Lobby](lobby1.png)
+    <!-- border -->
+    ![Lobby](lobby1.png)
+
 
 ---