Button payload is ending up as response

Rasa Open Source
4

@niveK - I was thinking that as well, I’m using this project for webchat, I just changed the look a bit. I just assumed it would have handled buttons (with slots) - GitHub - scalableminds/chatroom: React-based Chatroom Component for Rasa Stack and haven’t really looked into.

So lets forget about the web chat for a moment. I have the same issue when I use rasa shell

Here is the “button” prompt from the command line. You can see the button “values” in parenthesis:

rasa-shell-button-prompt
rasa-shell-button-prompt836×187 17.8 KB

Then when I choose (chose the Security Group option) it puts the entire payload into the response as it I typed it:

rasa-shell-chosen
rasa-shell-chosen1367×101 11.3 KB

I have my intents matching the payload

intents:
- Solution-10:
    use_entities: []
- s10_choice_shared_drive
- s10_choice_security_group
- s10_choice_neither

And the proper utterances for those intents:

  utter_s10_choice_shared_drive:
  - text: "In order to help you with your shared drive issue, I have to ask you some questions"
  utter_s10_choice_security_group:
  - text: "In order to help you with your security group issue, I have to ask you some questions"
  utter_s10_choice_neither:
  - text: "Is there another problem?"

I’m guessing since I am not seeing those utterances, the payloads are not grabbing the intents properly.

For fun I removed the slot filling portion for the buttons -

  utter_ask_s10_verify_problem:
  - text: "Are you trying to get access to a Shared Drive, Security Group or neither?"
    buttons:
    - title: "Shared Drive"
      payload: '/s10_choice_shared_drive'
    - title: "Security Group"
      payload: '/s10_choice_security_group'
    - title: "Neither"
      payload: '/s10_choice_neither'

And it did the same thing. :thinking: