syncing walkthrough

docs/infrastructure/deploy_application.md

@@ -1,7 +1,14 @@
 # Demo: Deploy Application
 
+[Click here to return to master demo list](../../README.md#demo-repository)
+
 ## Table of Contents
-TBD
+
+* [Objective](#objective)
+* [What business problem is solved?](#what-business-problem-is-solved)
+* [Features show cased](#features-show-cased)
+* [Video](#video)
+* [Guide](#guide)
 
 # Objective
 
@@ -35,16 +42,50 @@ For description of these and other features of the Red Hat Ansible Automation Pl
 
 2. Navigate to **Templates**
 
-  ![job templates](../../images/templates.png)
+     ![job templates](../../images/templates.png)
 
 3. Click the rocket next to **INFRASTRUCTURE / Deploy Application** to launch the Job
 
-  ![rocket launch](../../images/rocket.png)
+     ![rocket launch](../../images/rocket.png)
 
 4.  The survey will prompt you to install an application.
 
-  ![survey choice](../../images/deploy_application_survey.png)
+     ![survey choice](../../images/deploy_application_survey.png)
+
+5. Choose an application and press **NEXT**      
+
+     ![survey preview](../../images/survey_preview.png)
+
+     Explain to audience what is happening here depending on audience persona
+
+    **Persona A**: Technical audience that has written Ansible Playbooks before:
+    Surveys create variables that the Job can use within Ansible Playbooks. In this example a pre-defined list of applications that are tested and allowed on IT infrastructure.  The variable is named **application** and the value is **httpd** in this screenshot.
+
+    **Persona B**: Decision maker audience, IT manager or above:
+    reiterate business values above.  This allows a non subject matter expert the ability to automate routine tasks.  They can't install applications that are not vetted and put within the survey.  In the event that your IT process does not allow the Red Hat Ansible Automation Platform to be the front end, it has a rich and powerful API that can work with existing workflows such as ServiceNow.
+
+6. Execute the job by pressing the green **LAUNCH** button
+
+7. Explain what is happening:
+
+     - Job has started executed in the background.  The user can navigate off this page and the job will continue to execute.
+     - On the left is the **Job Details Pane** labeled simply with **DETAILS**.  This information is logged and tells you who, what, when and how.
+       - **who** - who launched the job, in this example is the admin user
+       - **what** - the project and Ansible Playbook used, and which credential to login to the infrastructure
+       - **when** - time stamps for start, end and duration of the job run.
+       - **how** - the job status (pass, fail), enviornment and execution node
+     - The larger window on the right is the **Standard Out Pane**.  This provides the same console output the user would be used to on the command-line for troubleshooting purposes.  Some important takeways to showcase are:
+       - aggregate info is at the top including the amount of Plays, tasks, hosts and time duration.
+       - this pane can be expanded to take up entire browser window
+       - Ansible Playbook can be downloaded for troubleshooting purposes
+       - **click on task output** to show them task-by-task JSON output that can be used for troubleshooting or just getting additional information
+       ![task breakdown](../../images/platform_task_breakdown.png)
+
+8. Circle back and summarize
+
+     You need to circle back what has been showcased to the [business reasons listed above](#what-business-problem-is-solved).  You are welcome to verify on the RHEL web nodes that the application was actually installed but unless you have a very technical audience you are going to start losing folks.  The real business solution here is automating away the boring and routine.  
+
 
 
 ---
-You have finished this demo.  [Click here to return to master demo list](../../README.md)
+You have finished this demo.  [Click here to return to master demo list](../../README.md#demo-repository)