aws-samples / amazon-ai-building-better-bots Goto Github PK

Hi,

Is there any way that we can send multiple response cards in bot response using fulfillment by lambda ?

Regards,
Kanwal

It looks like the last change to the lambda function source code (bd47237) only works with Node 6.10, not 4.3. If this is true, please update the README.md file (https://github.com/awslabs/amz-ai-building-better-bots/blob/master/README.md#lambda-function) to prevent confusion. Thanks!

I followed the tutorial and made a bot using Amazon Lex. I created an alias and attached the lambda function to it and enabled the code hook option so that it uses that lambda function in the alias. When I test the bot though, it just says that the intent coffeOrderBeverageIntent is fulfilled.

Hi,

Has anything changed with the response format that is expected by Lex,

I am getting the error message,

An error has occurred: Invalid Lambda Response: Received error response from Lambda: Handled

when i try from Lex. However, the cafeOrderCoffee_test.json is giving the response as

{
"sessionAttributes": {},
"dialogAction": {
"type": "ElicitSlot",
"intentName": "cafeOrderBeverageIntent",
"slots": {
"BeverageType": "mocha",
"BeverageStrength": null,
"Creamer": null,
"BeverageSize": null,
"BeverageTemp": null,
"BeverageExtras": null
},
"slotToElicit": "BeverageSize"
}
}

Thanks,

Hello!

While this is a very helpful resource, the documentation is only accurate for users using the Lex V1 console. For new users hoping to follow with Lex V2, some instructions are slightly inaccurate or incorrect altogether (Error Handling specifically). I would like to propose a rewriting of the README to better support users hoping to implement the CoffeeBot with Lex V2.

Some areas I noticed that would need a change are:

• Step 1: Create the bot:
  • "Output Voice" and "Sentiment Analysis" are no longer necessary parts of the table
  • "IAM Role" value listed in table is no longer correct
• Step 3: Create slot types:
  • Slot types are now created under the "Language" submenu, and are not accessible from the sidebar while creating an intent.
• Step 6: Define fulfillment:
  • Return parameters to client is no longer an option under the "Fulfillment" menu
• Step 7: Define responses:
  • "Responses" are now shown as "Closing response" in Lex V2
  • You can no longer declare a second message after selecting "Wait for user reply" in the "Closing response" menu
• Step 8: Review the error handling settings:
  • This section is fully outdated as there is no longer an "Error handling" page in the menu for Lex V2
    • From my understanding, the error handling is now managed through the "FallbackIntent." Documentation for this was seemingly sparse in AWS docs, so I think this CoffeeBot would be a great way to show new users how to configure the FallbackIntent. This is the section of the project that I personally had the hardest time following when trying to implement within Lex V2.

Hopefully restructuring this CoffeeBot tutorial to utilize Lex V2 will be taken into consideration, this would be nice to have for new Lex users like myself.

Thanks!