Updated README doc

Author: Russ Williams

ACSAgentHub/APIs/Conversations/putConversation.cs

@@ -23,7 +23,7 @@ public putConversation(IConfiguration config)
             _config = config;
         }
 
-        [FunctionName("putConversation")]
+        [FunctionName("putConversations")]
         public async Task<IActionResult> Run(
             [HttpTrigger(AuthorizationLevel.Anonymous, "put", Route = "conversations")] HttpRequest req,
             ExecutionContext context,

ComposerExample/ComposerExample.dialog

@@ -78,7 +78,7 @@
           "$kind": "Microsoft.SendHandoffActivity",
           "$designer": {
             "id": "6RC9sf",
-            "comment": "Handoff to ACS"
+            "comment": ""
           },
           "context": {
             "Skill": "offshore accouts",

Deployment/Scripts/deploy_and_configure.ps1

@@ -2,7 +2,7 @@
 Run this script from the ACSAgentHub project folder (i.e., the one that has ACSAgentHub.csproj)
 #>
 
-#Requires PoserShell 7
+# Requires PowerShell 7
 
 # Usage:
 # The following command deploys and configures an agent hub named TestHubRHW21 to run locally
@@ -16,6 +16,7 @@ Run this script from the ACSAgentHub project folder (i.e., the one that has ACSA
 Param(
     [string] $hubName,
     [string] $resourceGroup,
+    [string] $ngrokFullPath,
     [string] $configurationOnly = "false", # Just configure things to run locally, but don't deploy (remaining params are not needed with -restart command)
     [string] $location,
     [string] $NuGetFullPath,
@@ -45,6 +46,10 @@ if (-not $resourceGroup) {
     $resourceGroup = $hubName
 }
 
+if (-not $ngrokFullPath) {
+    $ngrokFullPath = Read-Host "? Full path to ngrok.exe (e.g., c:\ngrok\ngrok.exe):"
+}
+
 if (-not $location -and $configurationOnly.ToLower() -eq "false") {
     $location = Read-Host "? Azure resource group region"
 }
@@ -116,7 +121,7 @@ if ($configurationOnly.ToLower() -eq "false") {
 
 # Step 5 - Create Tunnel to Agent Hub
 Write-Host "Creating Tunnel to Agent Hub"  -NoNewline -ForegroundColor Green
-start -FilePath "c:\ngrok\ngrok" -ArgumentList "http 7071 -host-header=localhost:7071" -WindowStyle Minimized 
+start -FilePath $ngrokFullPath -ArgumentList "http 7071 -host-header=localhost:7071" -WindowStyle Minimized 
 
 if ($?) {Write-Host " - Done." -ForegroundColor Green} else {Write-Host " - Failed" -ForegroundColor Green; $errCnt++} 
 

README.md

@@ -59,12 +59,13 @@ In PowerShell, change the current directory to the root solution folder (i.e., t
 that contains the ACSAgentHub.sln file). Then run the following script to deploy and
 configure all the services required by the ACS Agent Hub:
 ```
-.\Deployment\Scripts\deploy_and_configure.ps1 -hubName <hub name> -resourceGroup <resource group> -location <location name> -NuGetFullPath <nuget path>
+.\Deployment\Scripts\deploy_and_configure.ps1 -hubName <hub name> -resourceGroup <resource group> $ngrokFullPath <ngrok path> -location <location name> -NuGetFullPath <nuget path>
 ```
 where:
 - **\<hub name>** is the name of your agent hub which will also be used as part of the name of
 other services created by this script
 - **\<resource group>** is the name of the resource group that services will be deployed to
+- **\<ngrok path>** is the full path to the ngrok.exe (e.g., c:\nuget\ngrok.exe)
 - **\<location name>** is the Azure location name of the region that services will be deployed in
 - **\<nuget path>** is the full path to the nuget.exe (e.g., c:\nuget\nuget.exe)
 
@@ -103,15 +104,18 @@ sense for your bot<br>
 to ```=null```:<br>
 ```
 {
-  "Skill": "<skill 1> <skill 2> <skill N>",
-  "Name": "<bot user's name>",
-  "CustomerType": "<customer class (e.g., vip, premium, etc.>",
-  "WhyTheyNeedHelp": "<reason for help request>"
+  "Skill": "offshore accounts",
+  "Name": "Test Name",
+  "CustomerType": "vip",
+  "WhyTheyNeedHelp": "lost order"
 }
 ```
 The properties and values above are defined by the agent hub you're escalating to.  So, for example, the payload
 is unique to LivePerson or Omnichannel and you'd check their documentation to find out what the payload should
-look like for those agent hub solutions but, for the ACS Agent Hub you'll use the above payload.  Currently, 
+look like for those agent hub solutions but, for the ACS Agent Hub you'll use the above payload and replace the
+hardcoded sample values with the appropriate values (use the values above if you are just experimenting).  
+
+Currently, 
 the **Skill** and **CustomerType** properties are not being used by the ACS Agent Hub and can be set to whatever
 you like or left empty.  The **Name** and **WhyTheyNeedHelp** properties are used in the agent-portal and the 
 ComposerExample shows a nice way to gather and set those properties.  When you're finished, it should look like